Re: Why vimdiff <() <() reset when terminal is switched?

2021-04-17 Thread Peng Yu
Here is what I have. I have tried to remove ~/.vim/ftdetect ~/.vim/bundle-available ~/.vim/after ~/.vim/plugin. The problem is not gone. When I try to remove ~/.vim, the problem is gone. It is very hard to debug this problem. Could this problem be due to some interaction between two plugins?

Re: Why vimdiff <() <() reset when terminal is switched?

2021-04-14 Thread Tony Mechelynck
On Wed, Apr 14, 2021 at 12:20 AM rwmit...@gmail.com wrote: > > I think there (or at least in my case) is some plugin causing the issue. > I didn't even have to change terminals, just 'j' to the bottom of the first > diff file and the screen went blank. > reran again using: vimdiff -u NONE -U

Re: Why vimdiff <() <() reset when terminal is switched?

2021-04-13 Thread Peng Yu
Indeed. Some plugins are causing the problem. But I also have any files in ~/.vim. How to easily figure out which one causes the problem? On Tuesday, April 13, 2021 at 5:20:10 PM UTC-5 rwmit...@gmail.com wrote: > I think there (or at least in my case) is some plugin causing the issue. > I

Re: Why vimdiff <() <() reset when terminal is switched?

2021-04-13 Thread rwmit...@gmail.com
I think there (or at least in my case) is some plugin causing the issue. I didn't even have to change terminals, just 'j' to the bottom of the first diff file and the screen went blank. reran again using: vimdiff -u NONE -U NONE and it worked as expected. I have nearly 50 plugins, so my

Re: Why vimdiff <() <() reset when terminal is switched?

2021-04-13 Thread Tony Mechelynck
Does the vimdiff content reappear if you hit Ctrl-L (on a Mac it might or might not be Cmd-L, I'm not sure) in Vim? If it does, then there is a screen refresh missing somewhere. Best regards, Tony. -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply

Re: Why vimdiff <() <() reset when terminal is switched?

2021-04-13 Thread Gary Johnson
On 2021-04-13, Peng Yu wrote: > > I don't understand what you mean by "switch to another terminal". > > > On macOS, I use iTerm2 to run vimdiff <(seq 3) <(seq 4). Then open a new tab > in > iTerm2. Then go back to the original tab. Then the content in vimdiff > disappears. Thanks for the

Re: Why vimdiff <() <() reset when terminal is switched?

2021-04-13 Thread Bram Moolenaar
Gary Johnson wrote: > On 2021-04-13, Peng Yu wrote: > > When I call `vimdiff <(seq 3) <(seq 4)`, then switch to another terminal > > then > > switch back, the content in vim disappear. How to make the content > > persistent? > > I run vimdiff with process substitution like that all the time

Re: Why vimdiff <() <() reset when terminal is switched?

2021-04-13 Thread Peng Yu
> I don't understand what you mean by "switch to another terminal". > On macOS, I use iTerm2 to run vimdiff <(seq 3) <(seq 4). Then open a new tab in iTerm2. Then go back to the original tab. Then the content in vimdiff disappears. -- -- You received this message from the "vim_use"

Re: Why vimdiff <() <() reset when terminal is switched?

2021-04-13 Thread Gary Johnson
On 2021-04-13, Peng Yu wrote: > When I call `vimdiff <(seq 3) <(seq 4)`, then switch to another terminal then > switch back, the content in vim disappear. How to make the content persistent? I run vimdiff with process substitution like that all the time without losing anything. The outputs of

Re: Why vimdiff <() <() reset when terminal is switched?

2021-04-13 Thread C. Meissa
Hi Peng Yu, those pipes are not seek-able files and may not be read again — maybe this is. Also, this problem sounds very very similar the your previous one. Best Regards, CM Peng Yu schrieb am 13.04.2021 16:39:56: > When I call `vimdiff <(seq 3) <(seq 4)`, then switch to another terminal >