Skip to content
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

Home and End keys do not work in helix while using zellij #1182

Closed
dannasessha opened this issue Mar 6, 2022 · 4 comments · Fixed by #1190
Closed

Home and End keys do not work in helix while using zellij #1182

dannasessha opened this issue Mar 6, 2022 · 4 comments · Fixed by #1190
Labels
compatibility Issues with VT/terminal compatibility suspected bug

Comments

@dannasessha
Copy link

zellij --version: zellij 0.25.0
tput lines: 45
tput cols: unknown terminfo capability 'col'
OS: arch linux 5.16.11-arch1-2

List of programs interacted with:
HELIX helix --version
helix v0.6.0
ALACRITTY alacritty --version
alacritty 0.10.1 (2844606d)

log displays all INFO events, nothing stands out as wrong.

Running helix in alacritty without zellij I am able to use Home and End keys while in helix's insert mode to navigate the cursor to the beginning and end of the line I am editing. Running zellij and then helix, using those keys in the same way appear to do nothing. I also tried locking zellij, but this does not change the behavior.

@a-kenji a-kenji added the compatibility Issues with VT/terminal compatibility label Mar 6, 2022
@colemickens
Copy link

I had opened one on the helix side a while back too, just to link them: helix-editor/helix#1694

@colemickens
Copy link

I use zsh, and it seems like I have manually set these bindkeys... at some point in forgotten history (in case its related):

bindkey "^[[H"    beginning-of-line
bindkey "^[[F"    end-of-line
bindkey "^[[3~"   delete-char
bindkey "^[[1;5C" forward-word
bindkey "^[[1;5D" backward-word

@a-kenji
Copy link
Contributor

a-kenji commented Mar 7, 2022

Some more information:

  • alacritty:

HOME:

^[[H 	 27 0033 0x1b
 	 91 0133 0x5b
 	 72 0110 0x48

END:

^[[F 	 27 0033 0x1b
 	 91 0133 0x5b
 	 70 0106 0x46
  • alacritty & tmux:

HOME:

^[[1~    27 0033 0x1b
         91 0133 0x5b
         49 0061 0x31
        126 0176 0x7e

END :

^[[4~    27 0033 0x1b
         91 0133 0x5b
         52 0064 0x34
        126 0176 0x7e
  • alacritty & zellij:

HOME:

^[OH     27 0033 0x1b
         79 0117 0x4f
         72 0110 0x48

END:

^[OF     27 0033 0x1b
         79 0117 0x4f
         70 0106 0x46

@tlinford
Copy link
Contributor

tlinford commented Mar 8, 2022

Interesting, referring again to the xterm docs it looks like since #815 we are sending the SS3 H and SS3 F versions instead of the CSI H and CSI F that we are getting from alacritty (https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-PC-Style-Function-Keys).
On the other hand tmux is sending the vt220 variants CSI 1 ~ and CSI 4 ~ (https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-VT220-Style-Function-Keys).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compatibility Issues with VT/terminal compatibility suspected bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants