-
-
Notifications
You must be signed in to change notification settings - Fork 506
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
macOS + iterm ctrl-n binding issues #1577
Comments
In my macOS, iTerm2 3.4.23.
|
Do you have any bindings setup? iTerm often has a bunch of shortcuts defined in its keys settings. Also - what keyboard layout are you using? |
I'm also having issues. I have a lot of terminals on my Mac, so I tested in all of them:
I don't actually use most of these terminals, so I doubt that it's my config that's the issue. |
Having the same problem here on linux/us layout with multiple terminals/shells (including tty!), so it's not just macs -- upon further digging it looks like it's a feature; for example xterm's code:
So ctrl-3 is escape, that'd close the search interface alright... Looking at Since I cannot use alt for this (taken up by my window manager), I'd be tempted to suggest other alternatives (shift-number, F keys, first row...) -- but that'll depend heavily on the keyboard layout, perhaps it'd be simpler to just let users bind each key individually? The code in atuin/src/command/client/search/interactive.rs is currently a big match switch that's a tad unwieldy to customize but I guess it'll be an investment that pays off for everyone who isn't on us layout as well. Until then, we can just ignore the pretty numbers on the left! :p |
This issue has been mentioned on Atuin Community. There might be relevant details there: https://forum.atuin.sh/t/help-with-macos-ctrl-n-key-shortcuts/271/2 |
It works for me, thanks. |
it doesn't work in macOS Donoma 14.1.2 that use
ctrl_n_shortcuts = true
in config file. when i use this config, press ctrl+n shortcut and don't work!The text was updated successfully, but these errors were encountered: