These binds might also fix programs running within URxvt e.g. Where KP_Home and KP_End are the numpad Home and End keys.
#Alacritty wsl code#
You can add key binds using the same quoted-insert characters as used for Readline, but use \033 to represent an escape character:Īdd escape code binds to your X resources using the same escape sequence format as for Lynx:
#Alacritty wsl how to#
You may have to consult the documentation for the given program on how to fix it. If the above steps do not resolve the issue, it is probably a program-specific problem rather than a system-wide one. Then compile the new terminfo (which saves it to your ~/.terminfo directory)Īnd lastly specify the new terminfo in your shell's environment variables: Warning: Ensure that no other key use the same character sequence.
ncurses), you can try editing your terminfo to change which escape codes are sent to the terminal for certain actions.įirst save your existing terminfo to a file Note that Readline uses \e to indicate an escape character.įor programs that do not use Readline (e.g. Since these escape codes are not listed in the default Readline configuration, you will need to add them: The ^[ indicates an escape character in your shell, so this means that your Home key has an escape code of [1~ and you End key has an escape code of [4~.
#Alacritty wsl series#
The default binding for quoted-insert is Ctrl+v.įor example, you could give the following series of inputs in your terminal: To see them, you can use a Readline command called "quoted-insert" or run the command showkey -scancodes which outputs the value of a key verbatim. First you need to find out what escape codes are being sent. If your keys are not working, it could be because your particular terminal sends escape codes not in this list. In the default /etc/inputrc, there are several lines that attempt to handle common Home/End escape codes: Readline maintains mappings for more obscure keys in /etc/inputrc and ~/.inputrc for global and per-user mappings, respectively. So properly configuring Readline can fix Home and End in many cases. Many command line applications use the Readline library to read input. PS1="\\u \\w \\$ \"įor more info, please refer to Bash/Prompt customization. To avoid that, you should enclose your non-printable stuff in PS1 with \ so that shell can understand that it is actually non-printable. (Discuss in Talk:Home and End keys not working) Reason: The following instructions are Bash-specific. This will obviously result in text rendering mistakes. for colored text), shell may assume that they are actual printable characters with non-zero length. The shell tries to calculate actual length of the prompt contained in PS1 environment variable, but if PS1 contains some escape sequences (e.g. ~/.nf set -g default-terminal screen-256colorĪnother possible reason for misbehaving Home and End keys is malformed custom shell prompt. ~/.Xresources XTerm*termName: xterm-256colorįor GNU Screen, it can be set in ~/.screenrc:įor Tmux, it can be set in ~/.nf (see tmux#Configuration): 'xterm' when you want 'xterm-256color'), there is typically a way to configure your terminal to properly override it without changing the TERM variable.įor xterm and urxvt, it can be set in the X resources:
If you do not like the TERM value chosen by your terminal (e.g. Again, do not set TERM manually - let the terminal do it. All modern terminals are smart enough to set their own TERM variable, so before you go delving into program configurations ensure that you are not incorrectly overriding it (for example, in your ~/.bashrc). The number one cause of broken keys is overriding the TERM environment variable to something that conflicts with your shell. Thus the solution varies from program to program.įirst you should check the common culprits that can affect the behavior of many programs.
Usually this problem can be fixed by configuring the offending program to perform the correct action when receiving certain escape codes. This is usually because the terminal emulator sends multi-character escape codes when such keys are pressed, which the running program (such as your shell) does not know how to interpret correctly. A frequent problem in command line programs is that keys like Home and End do not work as expected.
0 kommentar(er)
