-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[textinput] right or left arrow introduce stray characters while history search #10209
Comments
jalopezg-git
added a commit
to jalopezg-git/root
that referenced
this issue
Mar 29, 2022
UNIX terminals, e.g. vt100, send escape sequences for many special key combinations. Entering the history search mode assigned a specific meaning to the ESC character and disabled the processing of escape sequences, thus accidentally printing some characters that are part of a CSI. As a workaround, avoid changing the meaning of ESC; users can still use the well-known `ESC ESC` sequence (or any other editor command, e.g. move left/right) to exit the history search mode. Closes issue root-project#10209.
jalopezg-git
added a commit
to jalopezg-git/root
that referenced
this issue
Mar 29, 2022
UNIX terminals, e.g. vt100, send escape sequences for many special key combinations. Entering the history search mode assigned a specific meaning to the ESC character and disabled the processing of escape sequences, thus accidentally printing some characters that are part of a CSI. As a workaround, avoid changing the meaning of ESC; users can still use the well-known `ESC ESC` sequence (or any other editor command, e.g. move left/right) to exit the history search mode. This change only affects UNIX terminals. Closes issue root-project#10209.
2 tasks
jalopezg-git
added a commit
to jalopezg-git/root
that referenced
this issue
Mar 31, 2022
UNIX terminals, e.g. vt100, send escape sequences for many special key combinations. Entering the history search mode assigned a specific meaning to the ESC character and disabled the processing of escape sequences, thus accidentally printing some characters that are part of a CSI. As a workaround, avoid changing the meaning of ESC; users can still use the well-known `ESC ESC` sequence (or any other editor command, e.g. move left/right) to exit the history search mode. This change only affects UNIX terminals. Closes issue root-project#10209.
1 task
jalopezg-git
added a commit
that referenced
this issue
Mar 31, 2022
UNIX terminals, e.g. vt100, send escape sequences for many special key combinations. Entering the history search mode assigned a specific meaning to the ESC character and disabled the processing of escape sequences, thus accidentally printing some characters that are part of a CSI. As a workaround, avoid changing the meaning of ESC; users can still use the well-known `ESC ESC` sequence (or any other editor command, e.g. move left/right) to exit the history search mode. This change only affects UNIX terminals. Closes issue #10209.
Neel-Shah-29
pushed a commit
to Neel-Shah-29/root-1
that referenced
this issue
Apr 6, 2022
UNIX terminals, e.g. vt100, send escape sequences for many special key combinations. Entering the history search mode assigned a specific meaning to the ESC character and disabled the processing of escape sequences, thus accidentally printing some characters that are part of a CSI. As a workaround, avoid changing the meaning of ESC; users can still use the well-known `ESC ESC` sequence (or any other editor command, e.g. move left/right) to exit the history search mode. This change only affects UNIX terminals. Closes issue root-project#10209.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When you are within a search in the ROOT prompt (CTRL+R), pressing right arrow or left arrow selects the current match, but also introduces stray characters
[D
,[C
or similar. Which have then to be erased by hand.Something similar is found if you press Ctrl+Right_arrow or Ctrl+Left_Arrow
Expected behavior
The same, but without the stray characters being added.
To Reproduce
Setup
Additional context
#10121
The text was updated successfully, but these errors were encountered: