search

romgrk / barbar.nvim

The neovim tabline plugin.
2.16k stars 81 forks source link

nvim 0.10: bufferline doesn't update when process ends #522

Closed JosefLitos closed 10 months ago

JosefLitos commented 10 months ago

Open up a term (:term) and press \ or write exit. The term buffer title will stay hanging in the bufferline.

Iron-E commented 10 months ago

I can't reproduce. Does it happen with a minimal configuration?

vim.opt.rtp:append {
  '~/.local/share/nvim/lazy/barbar.nvim', -- or your install path
}

require'barbar'.setup {
  icons = {filetype = {enabled = false}},
}

vim.cmd.edit 'a' -- dummy file to fall back on after term closes
vim.cmd.term() -- open the terminal
  1. nvim --clean -u minimal.lua (a file with the contents from above)
  2. Enter exit into the terminal
JosefLitos commented 10 months ago

To me the same happens with minimal config: obrazek

My nvim -V1 -v:

NVIM v0.10.0-dev-924+g3e80b39a8
Build type: RelWithDebInfo
LuaJIT 2.1.1692716794
Compilation: /usr/bin/gcc-10 -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wvla -Wdouble-promotion -Wmissing-noreturn -Wmissing-format-attribute -Wmissing-prototypes -fno-common -Wno-unused-result -Wimplicit-fallthrough -fdiagnostics-color=always -fstack-protector-strong -DUNIT_TESTING -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_TS_HAS_SET_MAX_START_DEPTH -I/__w/neovim/neovim/.deps/usr/include/luajit-2.1 -I/usr/include -I/__w/neovim/neovim/.deps/usr/include -I/__w/neovim/neovim/build/src/nvim/auto -I/__w/neovim/neovim/build/include -I/__w/neovim/neovim/build/cmake.config -I/__w/neovim/neovim/src -I/usr/include -I/__w/neovim/neovim/.deps/usr/include -I/__w/neovim/neovim/.deps/usr/include -I/__w/neovim/neovim/.deps/usr/include -I/__w/neovim/neovim/.deps/usr/include -I/__w/neovim/neovim/.deps/usr/include -I/__w/neovim/neovim/.deps/usr/include
Iron-E commented 10 months ago

I updated my nightly version (v0.10.0-dev-950+gecd99e7dd now) since I was behind yours, and it seems that I can reproduce now.

Edit: :h news shows this message

Terminal buffers started with no arguments (and use 'shell') close automatically if the job exited without error, eliminating the (often unwanted) "[Process exited 0]" message.

That is probably the change that caused this.