-
Notifications
You must be signed in to change notification settings - Fork 394
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
Support Alt Click and OPT-CLICK to Navigate Through Current Command #775
Comments
bump |
Updated to specify that control clicking works when outside an encapsulating program in warp. |
Thanks for submitting! Will circle back when this is a work in progress. |
Please. |
+1 This is pretty much the only thing I've missed since moving to Warp. A co-worker mentioned this is the one thing preventing him from switching. |
This is the only reason i dont use warp |
Can someone post a video of the desired behavior from iTerm? AFAIK clicking in the Input Editor moves the cursor to where you clicked, is this request for moving the cursor within a Block (Command Output)? |
I loved Warp so much. But this is the reason I switched back to iterm2 |
Can you please add this feature in the next version? |
like this: Maybe not many people know Opinion+Click, but for those who know it, they are experts among terminal users, and Optional+Click is a killer feature for them. They will use or reject a terminal because of this feature. Please add this feature |
Yes, Please add this feature in the next release if possible |
Describe the solution you'd like?
In iTerm2, I'm able to alt click anywhere in my current line to move the cursor to that part of the line. This applies regardless of whether of I'm in a program or not (such as sql or an interpreter).
I would really love to see this feature in Warp - it's probably the greatest issue keeping me from recommending it over iTerm atm.
Is your feature request related to a problem? Please describe.
There are many applications for alt clicking on the terminal.
These include but not at all limited to:
Additional context
No response
The text was updated successfully, but these errors were encountered: