You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #1523: "--No lines in buffer--" appears in status line when match listing is first shown

Kind bug
Product Command-T
When
Status open
Reporter Greg Hurrell
Tags no tags

Description

Haven't yet identified the pattern for this, but I am noticing that the very first time I bring up Command-T in a window the prompt tends to display correctly, but often after opening other files and re-displaying the prompt it shows "--No lines in buffer--" rather than the desired ">> ". Causing the prompt to refresh in any way (by typing letters or tabbing in and out, for example) is enough to cause the prompt to display correctly.

Comments

  1. Greg Hurrell

    Most reliable recipe I've come up with so far to reproduce:

    • <Leader>t: bring up match listing
    • <CR>: open something
    • <Leader>t: bring up match listing
    • <CR>: open something else (merely reopening the same file won't work)
    • <Leader>t: bring up match listing; now visible "--No lines in buffer--"

    Note that it doesn't matter whether you open with <CR> or <C-CR> etc.

  2. Greg Hurrell

    After a lot of experimentation with silent, and forced redraws, and changing the order of things, I am unable to get rid of the "--No lines in buffer--" message.

    The only way I've been able to suppress the display of the message is to not destroy the match window (with :bwipeout!). This obviously breaks the plug-in, so I can't simply eliminate that line, but it does at least suppress the message. I'm going to try some other experiments around that point of the code in order to see what I can do.

Add a comment

Comments are now closed for this issue.

Menu