Skip to content
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

Change tab filename when switching between splits in the same tab #2332

Open
ByteDrummer opened this issue Feb 5, 2021 · 4 comments
Open

Comments

@ByteDrummer
Copy link

ByteDrummer commented Feb 5, 2021

environment

  • vim: nvim 0.4.4
  • vim-airline: latest
  • OS: Pop!_OS
  • Have you reproduced with a minimal vimrc: N/A
  • What is your airline configuration:
let g:airline#extensions#tabline#enabled = 1
let g:airline#extensions#tabline#show_buffers = 0
let g:airline#extensions#tabline#show_splits = 0
let g:airline#extensions#tabline#show_tabs = 1
let g:airline#extensions#tabline#show_tab_nr = 0
let g:airline#extensions#tabline#show_tab_type = 0
let g:airline#extensions#tabline#show_close_button = 0

if you are using terminal:

  • terminal: GNOME Terminal
  • $TERM variable: xterm-256color
  • color configuration (:set t_Co?): gruvbox
    if you are using Neovim:
  • does it happen in Vim: N/A

actual behavior

In a specific tab, when switching to a different split, the filename on the tab doesn't change to the filename of that split.

expected behavior

Although, I could use let g:airline#extensions#tabline#show_splits = 0 I'd like to keep the tabline minimal and instead have the filename on the tab change. This is similar to how lightline behaves if you've ever used it. Could there be a way to do this?

@bartels
Copy link

bartels commented Jun 3, 2021

This one may be the same as #2294

Fixing this would make things match the default tab behavior in vim, which changes the name in the tab to match the active/focused window.

@get-me-power
Copy link
Member

get-me-power commented Jun 3, 2021

Is this a problem that is also reproduced in vim8?

@bartels
Copy link

bartels commented Jun 3, 2021

Yes, I'm seeing this issue in both vim 8.1 and in neovim 0.5

@ByteDrummer
Copy link
Author

Is this a bug? I opened this issue as more of a feature request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants