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

Nvim opens a [No Name] buffer when started on a directory #79

Open
saccarosium opened this issue Jan 18, 2025 · 0 comments
Open

Nvim opens a [No Name] buffer when started on a directory #79

saccarosium opened this issue Jan 18, 2025 · 0 comments
Labels
bug issues reporting wrong behavior nvim neovim specific issues

Comments

@saccarosium
Copy link
Owner

Neovim version (nvim -v)

NVIM v0.6.1

Vim (not Nvim) behaves the same?

no, Works fine on Vim 8.2

Operating system/version

macOS 12.1 Monterey

Terminal name/version

Terminal.app 2.12

$TERM environment variable

xterm-256color

Installation

Homebrew

How to reproduce the issue

nvim -u NORC .

Expected behavior

This should start nvim with a single netrw buffer.
The status line should indicate the path followed by "[netrw]".

Actual behavior

It opens 2 buffers, the netrw one and a "[No Name]" one.
The status line mixes both names and says "[No Name] [netrw]"

Essentially it seems like you see the right netrw buffer and can interact with it, except nvim kind of believe it is on the "[No Name]" buffer.

The main issue for me is that it also places the "[No Name]" buffer as the current buffer. So if I open a file in the directory listing and then press CTRL-^, I expect to be back on the netrw buffer. But I end up on the real "[No Name]" buffer that is empty. I say "real" because when landing, it thinks I am on "[No Name]" but what I see and interact with is really the netrw buffer.

original issue: neovim/neovim#17841

@saccarosium saccarosium added bug issues reporting wrong behavior nvim neovim specific issues labels Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug issues reporting wrong behavior nvim neovim specific issues
Projects
None yet
Development

No branches or pull requests

1 participant