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

<C-i> doesn't do jump_forward #6184

Closed
gyreas opened this issue Mar 4, 2023 · 7 comments
Closed

<C-i> doesn't do jump_forward #6184

gyreas opened this issue Mar 4, 2023 · 7 comments

Comments

@gyreas
Copy link

gyreas commented Mar 4, 2023

C-i doesn't behave as intended. When "tab" is mapped to "command_mode", C-i then does "command_mode". It doesn't do anything when "tab" is not mapped as such.
I tried changing keymaps/defaults.rs as such:
- "C-i" | "tab" => "command_mode",
+ "C-i" => "command_mode",

And recompiling helix-term. Got the same result: it behaves the same way.

Is this an isolated event?

Terminal:
Kitty
Platform:
Fedora 37
hx -v:
22.12

@the-mikedavis
Copy link
Member

Are you running helix from master or a pre-built release from a package manager?

By default, when you hit C-i, the terminal sends the same escape sequences as if you had hit tab to Helix. With #4939 being merged, it's now possible to tell C-i and tab apart if you're using a terminal that supports the enhanced keyboard protocol like Kitty.

@gyreas
Copy link
Author

gyreas commented Mar 4, 2023

Are you running helix from master or a pre-built release from a package manager?

By default, when you hit C-i, the terminal sends the same escape sequences as if you had hit tab to Helix. With #4939 being merged, it's now possible to tell C-i and tab apart if you're using a terminal that supports the enhanced keyboard protocol like Kitty.

I'm using the master branch, and that's because I couldn't get Ada lsp to work with it. I'm using Kitty too

@the-mikedavis
Copy link
Member

What does the log say when opening the editor when running in verbose mode (hx -vv)? https://github.com/helix-editor/helix/wiki/FAQ#access-the-log-file

There should be a line that says "The enhanced keyboard protocol is supported on this terminal" if we're enabling the enhanced keyboard protocol.

@gyreas
Copy link
Author

gyreas commented Mar 4, 2023

What does the log say when opening the editor when running in verbose mode (hx -vv)? https://github.com/helix-editor/helix/wiki/FAQ#access-the-log-file

Running tail -f ~/.cache/helix/helix.log | grep enhanced showed nothing even tho hx -vv was used

There should be a line that says "The enhanced keyboard protocol is supported on this terminal" if we're enabling the enhanced keyboard protocol.

Do I enable it myself or it's core to helix?

@the-mikedavis
Copy link
Member

Ah ok, I think you are using a build that is older than the merge commit for #4939 then. Can you try pulling master and re-installing from source? cargo install --path helix-term --locked

@gyreas
Copy link
Author

gyreas commented Mar 4, 2023

Oh, okay. I try that now. Thanks

@gyreas
Copy link
Author

gyreas commented Mar 4, 2023

Yup, works like magic OTTB. We can close now. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants