We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When capturing with stdin.setRawMode(true) it doesn't return anything for those keys on Mac.
If you want to see for your self, configure rebase-editor -s to get a status bar on top that show exactly what keys are pressed..
rebase-editor -s
Any help or suggestions on this issue are very welcome.
In the mean time we have to settle with using Left and Right..
The text was updated successfully, but these errors were encountered:
I figured it out! You can configure the terminal to send the keys..
Terminal --> Preferences... --> Profiles --> Keyboard
Seletct + to add a key: Key: Cursor Up Modifier: Shift Action: Send text: \033[1;2A
Here are the relevant keys to configure: ⇧↑ \033[1;2A ⌃↑ \033[1;5A
⇧↓ \033[1;2B ⌃↓ \033[1;5B
For a complete list of available keys: /~https://github.com/google/terminal-app-function-keys/blob/master/README.md
If you want to use custom keys, use the -k parameter. It is also smart to enable the status bar with -s while testing. See command line arguments.
Sorry, something went wrong.
Update note on keybindings with solution from #8
f47bf83
To use HOME and END: ↖ \033[H ⇧↖ \033[1;2H
↘ \033[F ⇧↘ \033[1;2F
For PAGE_UP and PAGE_DOWN ⇞ \033[5~ ⇧⇞ \033[5;2~
⇟ \033[6~ ⇧⇟ \033[6;2~
For selection to work with PAGE_UP/DOWN you also need to disable Scroll alternate screen
Scroll alternate screen
No branches or pull requests
When capturing with stdin.setRawMode(true) it doesn't return anything for those keys on Mac.
If you want to see for your self, configure
rebase-editor -s
to get a status bar on top that show exactly what keys are pressed..Any help or suggestions on this issue are very welcome.
In the mean time we have to settle with using Left and Right..
The text was updated successfully, but these errors were encountered: