-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
bufadd does not sanitize windows drive letter capitalization #16331
Comments
Does this bug also apply to Vim and Nvim's |
yes, the behavior depends on bufadd, not buf_get_name/bufname |
I don't think this is a neovim (or vim) bug. If |
I guess the question is should it then. Currently when we want to compare on the lua side we have to sanitize the drive letter capitalization (which, to be fair, is trivial to do), because buf_get_name returns different values depending on the call to buff_add. I'm just not sure this behavior is intuitive see: |
I am having the same issue. Different results for different files. |
Was there any headway into fixing this? Does it even need fixing? As I see it, this shouldn't cause any problem. Sure, Funny aside: command prompt doesn't sanitize drive letters either. If you do |
Neovim version (nvim -v)
NVIM v0.6.0-dev+463-g68b2a9e56
Vim (not Nvim) behaves the same?
N/A (pretty sure the pathing code diverged a long time ago)
Operating system/version
Widnows 10
Terminal name/version
Windows Termianal
$TERM environment variable
N/A
Installation
source build
How to reproduce the issue
Expected behavior
vim.api.nvim_buf_get_name should show consistent capitalization for drive letters on windows regardless of the input to buf_add (which based on the code seems like it depends more on bufadd behavior than buf_get_name)
Actual behavior
The text was updated successfully, but these errors were encountered: