You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Three keyboard shortcuts I've come to expect in the terminal (rightly so or otherwise) are ctrl+L to clear the terminal, ctrl+U to clear the line to the left of the cursor, and ctrl+K to clear the line to the right of the cursor. However in theia it seems the default behavior is different. (And it is not so clear to me how to set it to this behavior.)
There is a similar situation with ctrl+a and ctrl+e, which I've come to expect for moving the terminal cursor to the beginning of the line and end of the line, respectively. ctrl+e works as expected, but ctrl+a does select all instead, which I argue is not expected default behavior in the terminal (it is in the editor).
Steps to Reproduce:
Access theia in the browser via theia-ide (can even try this via the Theia Cloud demo at theia-ide.org)
Pressing ctrl+U at the terminal works as expected; pressing ctrl+L at the terminal works as expected. Pressing ctrl+K at the terminal does not work as expected.
Pressing ctrl+k at the terminal does not clear to the end/right of the line (instead it clears up, see next).
Pressing ctrl+k at the terminal, when there are multiple lines displayed, clears it to the top (like expected from ctrl+L, which also does this — but I think ctrl+k should not do this).
Pressing ctrl+e at the terminal works as expected; pressing ctrl+a at the terminal does not, it does select all instead of moving the cursor to the start of the line.
Additional info
Part of the issue is that it is not clear to me how I would set these keyboard shortcuts myself to override the default behavior. This is because I don't have an example of the keyboard shortcut setting to use based on the ctrl+u and ctrl+e combinations that work as expected. Is this because of how the keyboard even is handled by the browser itself, before it is even registered in theia? This situation makes it all the more so relevant to have these shortcuts as the default, if possible, so users will not get stuck about how to set these as custom shortcuts.
Note that the Home and End keys at least seem to work as expected in the terminal, via the browser, which is good. But the ctrl+a/ctrl+e shortcuts are more effective alternatives in my opinion (and apparently in broader opinion, since I did not make these shortcuts up).
System Information
Operating System: Theia running on Ubuntu 24.04 aarch64 minimal via Theia-IDE; accessed from Windows 11 in the browser.
Theia Version: 1.54 (accessed via Firefox 131.0 on Windows)
The text was updated successfully, but these errors were encountered:
Bug Description:
Three keyboard shortcuts I've come to expect in the terminal (rightly so or otherwise) are
ctrl+L
to clear the terminal,ctrl+U
to clear the line to the left of the cursor, andctrl+K
to clear the line to the right of the cursor. However in theia it seems the default behavior is different. (And it is not so clear to me how to set it to this behavior.)There is a similar situation with
ctrl+a
andctrl+e
, which I've come to expect for moving the terminal cursor to the beginning of the line and end of the line, respectively.ctrl+e
works as expected, butctrl+a
does select all instead, which I argue is not expected default behavior in the terminal (it is in the editor).Steps to Reproduce:
ctrl+U
at the terminal works as expected; pressingctrl+L
at the terminal works as expected. Pressingctrl+K
at the terminal does not work as expected.ctrl+k
at the terminal does not clear to the end/right of the line (instead it clears up, see next).ctrl+k
at the terminal, when there are multiple lines displayed, clears it to the top (like expected fromctrl+L
, which also does this — but I thinkctrl+k
should not do this).ctrl+e
at the terminal works as expected; pressingctrl+a
at the terminal does not, it does select all instead of moving the cursor to the start of the line.Additional info
Part of the issue is that it is not clear to me how I would set these keyboard shortcuts myself to override the default behavior. This is because I don't have an example of the keyboard shortcut setting to use based on the
ctrl+u
andctrl+e
combinations that work as expected. Is this because of how the keyboard even is handled by the browser itself, before it is even registered in theia? This situation makes it all the more so relevant to have these shortcuts as the default, if possible, so users will not get stuck about how to set these as custom shortcuts.Note that the
Home
andEnd
keys at least seem to work as expected in the terminal, via the browser, which is good. But thectrl+a
/ctrl+e
shortcuts are more effective alternatives in my opinion (and apparently in broader opinion, since I did not make these shortcuts up).System Information
The text was updated successfully, but these errors were encountered: