Closed joereynolds closed 7 years ago
Isn't this a nvim bug? What's neoterm to do with it?
Well this bug only happens if a neoterm split is open (a normal :term
is fine) so I assumed it was a neoterm bug. Happy to have it closed if that's the case though?
I tried locally and wasn't able to replicate it in my macos with iterm2.
set runtimepath-=~/.config/nvim
set runtimepath-=~/.config/nvim/after
set runtimepath+=~/.config/nvim/pack/minpac/start/neoterm " use your path here.
set inccommand=split
My test:
Interesting, it doesn't do it on my laptop at home either (Xubuntu) with the same init.vim. I'll try with a minimal setup tomorrow, thanks for the patience!
@joereynolds Flicker can sometimes be related to $TERM
. Make sure $TERM
matches your real terminal, see :h $TERM
.
Hmmm, $TERM
is set to xterm-256color
(I'm using GNOME terminal).
If I use another terminal (xterm for example) it all works fine.
There is nothing in my .bashrc
, .profile
, or init.vim
that manipulates $TERM
Here's a gif of the issue
I've tried with a minimal init.vim
consisting of
set runtimepath-=~/.config/nvim
set runtimepath-=~/.config/nvim/after
set runtimepath+=~/.config/nvim/plugged/neoterm/
set inccommand=split
It could be a conflict with another plugin, I'll try and narrow it down.
Please read :h $TERM
Ubuntu 16.04
To Reproduce
Make sure you have the following line in your
init.vim
Create a test file
Open it up (
nvim neoterm.bug
) and start Neoterm:T ls
Now try and do a live substitution
You will see that substitutions flicker and fight against Neoterm's terminal.
If you close Neoterm's terminal and try the substitution again, it will not flicker.