Vi / Vim / Neovim support

[elviskahoro]

Vim support

[elviskahoro]

Describe the solution you'd like?

Vim Speed + Performance similar to alacritty.

Is your feature request related to a problem? Please describe.

My full Vimrc with various plugins installed, performs noticeably slower in Warp compared to Alacritty. I removed the plugins but kept sensible vim settings from the vimrc to test scrolling time with a base vimrc. Without plugins the difference is not as pronounced and not to the detriment of usability, but with plugins it was very noticeable and led to me using alacritty for text editing related tasks.

Additional context

Results

Alacritty - 59 seconds
08:05:20
08:06:19

Warp - 77 seconds total
08:06:23
08:07:40

~1.3 X - length
Video Here: https://elvis.ai/assets/warp_test_01.m4v
Warp - Test
09/23/2021

Vim's Scrolling Speed via Shift + ]
is considerably slower in warp compared to alacritty.
Scroll through a large file (pandas-core/generic.py)

Note: Tried to get the display to be as similar as possible (via alacritty.yml) but the warp window displays 49 vim lines and alacritty displays 48 vim lines.
Have a window running TOP under alacritty and warp for the clock.

Alacritty Settings:

	window
		padding: x = 8
		padding: y = 0

	font:
		size: 14.0
		offset: y = 2

Warp Settings:

	font size: 14

[CalgaryMichael]

x-post from Discord message:

Small visual bug that I had noticed when using vim (v 8.2) on Warp. You can see the cursor is bouncing around at random when scrolling on a file. Does not seem to have any affect besides visual -- when you stop scrolling, the cursor is in the correct location.

Screen.Recording.2021-10-05.at.2.18.57.PM.mov

Let me know if you need another further information (vim plugins, etc.)

[S15]

Ran into similar performance issues using with vim + warp. I see slow scrolling, slow cursor movement, and slow input. I was directed to this ticket to add information. What I am seeing appears to be related to having a (drawing a?) background color.

I set termguicolors, and use a custom color scheme. I link (most of) the rest of the highlight groups against the Normal group, and I set the Normal highlight group to:

hi Normal guifg=#bbbbbb guibg=#333333 gui=NONE

Changing Normal to:

hi Normal guifg=#bbbbbb guibg=NONE gui=NONE

seems to resolve the performance problems. (Similarly I tried editing with vim -u NONE and that seemed to work fine)

[Caprowni]

Just wanted to chime in on this after experiencing the same issues with lag using Vim, using the fix @S15 mentioned above worked for me also, speed increased to what I would expect!

[lrvdijk]

For me one of the last updates has fixed performance issues.

[lessp]

Got prompted with an update today which seems to have solved the performance issue for me as well! 🙌

[gagata]

oddly enough i most often hit the issues (gettiing a rainbow circle and all) when pressing backspace or switching between modes.

[elviskahoro]

From discord #vim-users 11.13.2021

I can't use ctrl-6 to go back to my latest buffer in nvim. This works in all other terminals I've used so far.
map <C-^> even adding this to my init.vim doesn't change anything...
<C-^> works but doesn't

[lrvdijk]

Hi, a few other things that are not entirely correct:

1. I use Fira Code Nerd Font, together with Vim-airline. The line height seems off, however, and the special glyphs are rendered a bit weirdly.
2. The different color of the window border compared to the vim background color bothers me a bit. Maybe I should configure my vim differently?

[lessp]

Also seeing some discrepancies in regards to themes (e.g. notice the line numbers as well as the indentation lines):

Warp

Kitty

[jmaitoza]

Here is my neovim output from the Warp terminal:

same exact prompt from iTerm:

I will note that I've been trying out neovim using this setup which does run with a lot of plugins

[elviskahoro]

Neovim:
"Specifically, Warp seems to struggle with mouse support for neovim. Clicking to move the cursor and scrolling using the touchpad are both pretty unreliable and jittery."

[elviskahoro]

Likning:

• nvim / neovim - Split plane w/ nvim wont resize #342

[elviskahoro]

Linking:

• Moved to #451: CTRL-/ does not comment out anymore in my neovim #376

[elviskahoro]

Linking:

• vi / vim / Nvim Double-cursor in warp when using fzf nvim plugin #429

[elviskahoro]

This specific theme makes the cursor disappear. Ported from #368

For some reason I don't see any cursor when using vim. While it's a nice throwback to only navigate using the line:col output in the status bar it's a bit too much these days.

The issue disappears when I disable the use of my vim theme - vividchalk.

Screenshot from both iterm2 and warp attached.

Iterm2

Warp

[elviskahoro]

@madisp

[elviskahoro]

From Andrew
One thing that’s a bit funny in neovim, is that warp adds tilde’s under the file in lieu of line numbers

Compared with alacritty

Also it seems that relative line numbers aren’t working in warp. The above screws are the same file, same vimrc config

[jamesgecko]

Some of my keybindings that use option don't seem to work in Neovim under Warp. I use A-h (and jkl) to switch between splits, and the keybinding works when my option keys are configured in iTerm 2 and Terminal, but I don't have such an option in Warp.

The neovim default <C-w>h keybinding works, but not my A-h mapping. In my ~/config/nvim/config.lua:

local map = vim.api.nvim_set_keymap
map('n', '<A-j>', '<C-w>j', { noremap = true })
map('n', '<A-k>', '<C-w>k', { noremap = true })
map('n', '<A-h>', '<C-w>h', { noremap = true })
map('n', '<A-l>', '<C-w>l', { noremap = true })

iTerm2 preference	Terminal preference

[jamesgecko]

Oops, I didn't even see this option is in the File menu.

[elviskahoro]

CTRL-/ does not comment out anymore in my neovim

From @corroded via #376

Describe the solution you'd like?

I would hope that all the keybindings I have in my vimrc would have been ported over. It looks like there are some keys that have not ported over properly. I think it should be able to port as the neovim window is technically not the terminal window anymore?

Is your feature request related to a problem? Please describe.

No response

Additional context

I am using this plugin: https://github.com/tomtom/tcomment_vim

Let me know if additional info is needed or there's already an existing issue (I tried to search but couldn't find any)

[elviskahoro]

ctrl shortcuts: "ctrl " usually comments things out in neovim but it doesn't work in warp.

[oriming]

I had the same problem and it was bothering me

[matsdahlin]

I recently got access to Warp, and NeoVim is pretty much unusable in it, it is noticeably laggy entering text compared to my current terminal (Kitty).

Glad that some of you have seen speed improvements, hoping there will be more improvements coming up!

[elviskahoro]

From email:

need padding/margin from top when terminal app (neovim) launched, there is no space atm, looks a bit strange.

[stevepond]

I run NVChad, which is neovim and packer and a bunch LSP and plugins. Seems like none of the plugin paths can be found...

[sullimander]

I'm using neovim with the navarasu/onedark.nvim theme, and it is rendering very different than it is in iTerm2. Any advice on how to fix the issue?

iTerm2

Warp

[robertwijas]

same here, the lack of underline is especially annoying :) any workarounds?

[minaeakhalil]

Does not appear to be fixed yet! I'm having this issue with various themes.

[elviskahoro]

@minaeakhalil What's your current configuration for Settings > Appearance > Text > Enforce Minimum Contrast?

If the underline is still missing after changing the setting to Never could you share a couple themes it works for and a couple themes it doesn't? Will help us drill down what's breaking it.

[minaeakhalil]

@elviskahoro - Thanks for following up and thanks for all your effort in making Warp such an amazing product 😄

The issue persist even when the Settings > Appearance > Text > Enforce Minimum Contrast is set to Never.

Here are some additional details, hope it would help troubleshooting this issue:

1. Using currently Neovim 0.9 with LazyVim pre-configuration
2. Tested this issue with different themes:
   • Catpuccin (the one in the attached screenshot),
   • Gruvbox
   • Gruvbox-material
   • TokyoNight (default for LazyVim)

In the screenshot, Warp is Top section, Wezterm is Bottom.

[minaeakhalil]

@elviskahoro - FYI, this is no longer an issue with the latest stable version of Warp (v0.2023.06.27.19.34.stable_01).

Thanks for the help and the support with Warp 😄

[nfwyst]

ligatures font support please

[colepeters]

Definitely some massive differences in colour rendering for me. Here's my Neovim in iTerm:

…and in Warp:

[bfulop]

This should be fixed in the coming weeks:
#1110 (comment)

[nyngwang]

off-topic: What's the name of your colorscheme?

[ddbrierton]

This thread is very old now, I have no idea if anyone from Warp is still monitoring it. Anyway, first things first, I’ve been using Warp every day since November 2022 and I absolutely love it. It’s easily the most innovative terminal application I’ve ever used. But I now find myself in the absurd situation of having to have Alacritty open alongside Warp solely so that I can use Neovim.

Whilst many of the earlier issues seem to have been addressed, two of the most fundamental things haven’t:

1. Warp does not relinquish styling of the cursor to Neovim, with the result that in Neovim’s normal mode the character the cursor is on is unreadable.
2. The option key on my Mac keyboard does not function properly — this is with Settings > Features > Keys > Left/Right Option key is Meta enabled. Some keys seem to work, but keys which in macOS normally function as dead keys, such as option + i do not. This seems to be a regression, which I reported in [macOS] option-i not working even with Left/Right Option key is Meta enabled #3018. I use a British keyboard and the # character is option + 3 which does nothing in Neovim running in Warp (but does work in the Warp command line). I write a lot of CSS - the # character is pretty essential.

Furthermore, some character decorations such as underlining and wavy underlining are not working in Warp but are in Alacritty, although I don’t consider that an essential feature, but it would be nice to have.

Screenshot of Warp:

Screenshot of Alacritty:

On the plus side, in my subjective opinion I think that fonts and colours are rendered better in Warp than in Alacritty.

I have to say though that I find it truly disheartening that you appear to be using time and resources adding things like AI when such fundamental things as a usable cursor and keyboard appear to be overlooked. Warp sure is clever, but if I want to get some work done I have to use Alacritty.

Finally, is there a vision for how Warp should handle apps which takeover the full terminal screen? After all, once something like nvim is running everything special about Warp is no longer available. It strike me that there is room to innovate here just as you did with blocks. Perhaps full terminal screen apps should detach into a s separate frame? I hope there is a vision, but please please fix the cursor and the keyboard before working on that!

[karambaq]

With line-height more that 1.3 symbols looks like this:

While in kitty or iTerm2 it looks fine:

[Manubi]

Are there also any plans to just add vim for the normal warp terminal? not the neovim support?
Because I am used to use vim navigation with iTerm. Would be nice to navigate with vim as well.

[ratbekn]

Hi! Font ligatures works in command line, but don't work in Neovim. Am I doing something wrong?

[chadoh]

Vim within an ssh session is not supported properly. The command header is still shown, which covers the first three lines of the file or so. Here you can see that the "do, re, mi" lines are covered by the command header.

[NeuSandeZ]

Is it only for me that the NeoVim doesn't take the full width and hight of warp?

[ddbrierton]

No, but I think that it is normal. Warp's window can be any number of pixels tall and wide, but Neovim I think sets its size in characters not pixels.

[elviskahoro]

@NeuSandeZ it has to do with Warp's grid. The Warp team explored expanding it way back but it led to some messiness. The most elegant workaround is to have Warp match the color of your neovim :(

[2nthony]

@NeuSandeZ it has to do with Warp's grid. The Warp team explored expanding it way back but it led to some messiness. The most elegant workaround is to have Warp match the color of your neovim :(

There are couple issues about the gap(padding) I've seen, so it should be add option to tweak the gap(padding). iTerm has supported, wezterm also supported(window_padding)

IMO: terminal should flex to user, but not user forced to flex terminal, because it is a Terminal

this is day theme for warp, but neovim is using night theme.