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
No response
I use Neovim as code editor. I noticed that neovim couldn't fill the entire terminal, but I tested it fine on terminal.app.
To reproduce it: 1- open neovim in warp
MacOS
macos14
zsh 5.9
v0.2023.10.03.08.03.stable_01
No, this bug or issue has existed throughout my experience using Warp
No
No, this same issue happens in Warp and other terminals.
None
The text was updated successfully, but these errors were encountered:
Thanks for submitting this @Raopend
We already have a request tracking this over at #2373
If you could please give it a 👍 and subscribe to that request, it would help us gauge interest. We'll post any updates there, so stay tuned!
We'll be closing this as a duplicate.
Sorry, something went wrong.
No branches or pull requests
Discord username (optional)
No response
Describe the bug
I use Neovim as code editor. I noticed that neovim couldn't fill the entire terminal, but I tested it fine on terminal.app.
To reproduce
To reproduce it:
1- open neovim in warp
Expected behavior
No response
Screenshots
Operating system
MacOS
Operating system and version
macos14
Shell Version
zsh 5.9
Current Warp version
v0.2023.10.03.08.03.stable_01
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
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.)
No, this same issue happens in Warp and other terminals.
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
None
The text was updated successfully, but these errors were encountered: