-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: winbar shows in terminal buffers in some cases #94
Comments
I've done some more digging, here's what I concluded: By default, an update to the winbar is only performed on the events Given that, I would think that there should be an additional event that should perform a winbar update, and this event should be triggered when launching a terminal. More in general, there should be an event that's triggered whenever Based on this assumption, I tried adding Does this make sense? |
Requirements
Expected Behavior
If I just start a terminal by for instance running
:call termopen(['ls'], {})
, there is no winbar in the current window (the current window is occupied by the terminal buffer). This is the behavior that I expect from barbecue.Now, I would also expect this behavior to be the same when doing the following set of actions
This is expressed by this function:
Actual Behavior
When calling the function defined above as
:call TestBarbecue()
, what I get is that there is a winbar in the window occupied by the terminal buffer. This is not expected (nor wanted, in my use case).Removing the line
call win_gotoid(l:orig_winid)
restores the expected behavior, i.e. no winbar in the terminal window. Interestingly, keeping the linecall win_gotoid(l:orig_winid)
but adding asleep 1m
just before the call totermopen()
also restores the expected behavior.Neovim Version
Minimal Configuration
Simple
init.vim
to reproduce the issue:Reproduction
TestBarbecue()
as specified in Expected Behavior:call TestBarbecue()
The text was updated successfully, but these errors were encountered: