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

On Wed, Apr 14, 2021 at 12:20 AM rwmit...@gmail.com
<rwmitchell@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 NONE and it worked as expected.
>
> I have nearly 50 plugins, so my motivation on figuring out which one is pretty low.
>
> On Tuesday, April 13, 2021 at 4:45:48 PM UTC-4 antoine.m...@gmail.com wrote:
>>
>> 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.

First, in your full session (with vimrc etc) go until the screen wakes
up blank. Then type (you may or may not have to blind-type)

:redir > ~/plugins.txt
:scriptnames
:redir END

This will write the list of all Vim scrpts sourced in this session
until that point, to a file named plugins.txt in your home directory,
but only if it doesn't exist yet (you may use any other name if you
already have a file by that name that you want to keep, or use :redir!
instead of :redir if you want to overwrite it). Then you may want to
open that text file in something other than Vim, or even to print it
so you can write on it the result of the following experiments:

If some of these scripts look like they might be causing the problem,
temporarily move them away to some place where Vim won't find them. If
none of them looks particularly suspicious, then move away about half
of them (not counting those which are distributed with Vim). Then
restart. If the problem reoccurs, it's one or more of those you kept
which is (are) the culprit. If it doesn't, then at least one of those
you moved away is all or part of the problem.

This way you ought to be able to cut the number of possible culprits
in half at each successive restart. Since 5 < log2(50) < 6, six tries
(or less if you're lucky or clever) ought to be enough to isolate the
culprit, at least if it's a single script. Maybe a few more tries if
it's two or more scripts throwing wrenches into each other's cogs.

Best regards,
Tony.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXvyvyfSObVFiw4T8yKM2rV789-phsF1F%3DsVFVV%2BQ%3DMwfw%40mail.gmail.com.