-
Notifications
You must be signed in to change notification settings - Fork 376
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
OPTION/CMD + ARROW LEFT/RIGHT or BACKSPACE not working as intended when Warp is in long-running command mode #807
Comments
I also see this behavior when starting the Julia REPL; pushing |
In fact, here's the exact unicode point that gets inserted: julia> x = ""
"\uf703" |
These shortcuts work when the Warp input area is showing. When you're in a REPL or a subshell, you're interacting directly with the shell which doesn't have Warp's editor functionality. Please upvote #64! |
I am closing this because this is not a bug, and it's actually what the terminal experience is outside of Warp. In order to get the desired behavior, we want to allow support for subshells to also be bootstrapped with Warp's input editor. Please subscribe to #64. |
I am not sure why this is intended. Both the built-in Terminal app and iTerm2 do not behave like this and I could for sure find other terminal apps which do the same. |
@jonashojer sorry about that - I was mistaken about the shell behavior without the warp input editor. reopening this! |
What's the status of this? Any workarounds? Until we get the subshell I would like to at least be able to use the basic keyboard shortcuts the same way I do in other terminals |
Any status on this? |
I am connecting "gcloud compute ssh" normally mac os terminal and connected gcloud bash allow me to go next word by "option+right arrow" |
Has this issue not been resolved yet? |
Describe the bug
To Reproduce
Steps to reproduce:
sudo su -
to elevate to rootExpected behaviour
Screenshots
No response
Operating System
MacOS
OS Version
12.2.1
Additional context
No response
The text was updated successfully, but these errors were encountered: