kassio / neoterm

Wrapper of some vim/neovim's :terminal functions.
Other
1.32k stars 117 forks source link

Neoterm clashes with inccommand=split #159

Closed joereynolds closed 7 years ago

joereynolds commented 7 years ago

Ubuntu 16.04

To Reproduce

Now try and do a live substitution

:%s/test/test/g

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.

justinmk commented 7 years ago

Isn't this a nvim bug? What's neoterm to do with it?

joereynolds commented 7 years ago

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?

kassio commented 7 years ago

I tried locally and wasn't able to replicate it in my macos with iterm2.

  1. Can you try with a minimal init.vim, like this:
    set runtimepath-=~/.config/nvim
    set runtimepath-=~/.config/nvim/after
    set runtimepath+=~/.config/nvim/pack/minpac/start/neoterm " use your path here.
    set inccommand=split
  2. Can you give more information about the env, like neoterm version and neovim version please?

My test: inccomand

joereynolds commented 7 years ago

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!

justinmk commented 7 years ago

@joereynolds Flicker can sometimes be related to $TERM. Make sure $TERM matches your real terminal, see :h $TERM.

joereynolds commented 7 years ago

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

inccommand

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.

justinmk commented 7 years ago

Please read :h $TERM