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
How to reproduce:
touch 'fails*' 'works*fine'
works*fine
fails*
*
Known workaround:
chmod +x 'fails*'
The text was updated successfully, but these errors were encountered:
Confirmed.
Sorry, something went wrong.
@denilsonsa , would you be willing to test the pull request #868 I've put together for this issue? Details are in the PR. Thanks.
Fixed in #868.
PhilRunninger
No branches or pull requests
How to reproduce:
touch 'fails*' 'works*fine'
(Yeah, I know this is a weird filename.)works*fine
file opens correctly, as expected.fails*
file silently fails to open. It is also shown in a different color because NERDTree understands*
as a suffix for executable files.Known workaround:
chmod +x 'fails*'
The text was updated successfully, but these errors were encountered: