warpdotdev
Editing in Nano screen discombulated
Discord username (optional)
No response
Describe the bug
On my Mac (11.7.10) when I open a file for editing via Nano, and use the commands to jump to a specific line (^W,^T + line number 222) , the screen display is wonky. If I instead use the navigation keys to scroll down to the proper location (^V) the display is fine. In the first case, if I scroll up some of the screen display is corrected, but not entirely.
To reproduce
1 - Open nano with an existing file (in my case a PHP code file appx 10K) 2 - Ctrl+W to open search menu 3 - Ctrl+T to goto line 4 - Enter ### (in my case 222) 5 - Observe the mess
Expected behavior
I expect the text in the file to display properly. Using the same steps in Terminal the behaviour is as expected.
Screenshots
No response
Operating system
MacOS
Operating system and version
11.7.10
Shell Version
zsh 5.8 (x86_64-apple-darwin20.0)
Current Warp version
v0.2024.01.02.08.02.stable_02
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
I'm new to Warp
Additional context
No response
Does this block you from using Warp daily?
No
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
I’ll have to set something up to capture - gimme a few days...
-- Larry Nussbaum Purgamentum init, exit purgamentum @.*** +61 431 770 008 m 1 917/921-6547 US On 9 Jan 2024, 6:02 AM +1100, elvis kahoro @.***>, wrote:
@larryn thanks for opening. can u send over a video too! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
here's video with what I believe is the same problem.
I don't think btop is the real culprit, but something at some point messes up the terminal. I also start to get history items quoted with the ~xxx ... xxx~ symbols. Have same issue on iTerm, but it detects it and asks to mitigate.
overall warp is not ready to be my ssh client yet, but otherwise good work.
https://github.com/warpdotdev/Warp/assets/957113/f4d6765d-5f58-42b3-aebc-d6f2d639afe6
Hello,
It seems related to https://github.com/warpdotdev/Warp/issues/3990 I opened.
