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

Bug: netrw buffer for directory appears in tabline buffer list #5

Closed
salcode opened this issue Oct 30, 2022 · 0 comments · Fixed by #6
Closed

Bug: netrw buffer for directory appears in tabline buffer list #5

salcode opened this issue Oct 30, 2022 · 0 comments · Fixed by #6

Comments

@salcode
Copy link
Owner

salcode commented Oct 30, 2022

How to Recreate

  • Open a file in Neovim
  • Hit - to trigger netrw
  • Navigate to another filename and click Return

Expected Behavior

There should be two buffers in the tabline at the top of the editor, one for each file

Actual Behavior

There are three buffers in the tabline at the top of the editor, one for each file plus one for the directory.

See tpope/vim-vinegar#13

Possible Solution

The vim-vinegar thread includes the suggestion of adding

vim.g.netrw_fastbrowse = 0

If we add this we should:

  • create a file at lua/config/vinegar.lua
  • add the above setting line to this new file
  • load this new file as the config for the vim-vinegar plugin in
    use({ "tpope/vim-vinegar" })
salcode added a commit that referenced this issue Oct 30, 2022
This is to resolve a bug where the directory buffer that is opened in
netrw when using vim-vinegar would appear in the tabline list alongside
the file buffers.

To prevent this we are setting g:netrw_fastbrowse to 0

Resolves #5
salcode added a commit that referenced this issue Oct 30, 2022
This is to resolve a bug where the directory buffer that is opened in
netrw when using vim-vinegar would appear in the tabline list alongside
the file buffers.

To prevent this we are setting g:netrw_fastbrowse to 0

Resolves #5
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

Successfully merging a pull request may close this issue.

1 participant