We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v0.8.0
no, vim 9.0.0655
Gentoo Linux
Alacritty
xterm-256color
emerge vim
NVim:
$ nvim -u NONE -es --cmd 'au VimEnter * verbose echo expand("%") expand("<afile>") "\n" | q' foo/ foo/ foo
Vim:
$ vim -u NONE -es --cmd 'au VimEnter * verbose echo expand("%") expand("<afile>") "\n" | q' foo/ foo/ foo/
Both expand('%') and expand('<afile>') should return 'foo/'. Vim (not Nvim) works as expected.
expand('%')
expand('<afile>')
'foo/'
expand('<afile>') returns 'foo' without a trailing slash.
'foo'
Related: #2833
The text was updated successfully, but these errors were encountered:
Seems a regression between v0.5.0 and v0.6.0.
Sorry, something went wrong.
zeertzjq
Successfully merging a pull request may close this issue.
Neovim version (nvim -v)
v0.8.0
Vim (not Nvim) behaves the same?
no, vim 9.0.0655
Operating system/version
Gentoo Linux
Terminal name/version
Alacritty
$TERM environment variable
xterm-256color
Installation
emerge vim
How to reproduce the issue
NVim:
Vim:
Expected behavior
Both
expand('%')
andexpand('<afile>')
should return'foo/'
. Vim (not Nvim) works as expected.Actual behavior
expand('<afile>')
returns'foo'
without a trailing slash.Related: #2833
The text was updated successfully, but these errors were encountered: