-
Notifications
You must be signed in to change notification settings - Fork 1.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
Cannot open files with square brackets in the name #391
Comments
Actually, it seems that other things break too with them (e.g., 'x' to close the parent). Seems related to the fact that Vim is escaping |
Seeing the same thing. Could this be new/recent behavior? I swear this used to work in an older version |
Could be a Vim bug as well. |
Not sure how I would test that, but vim opens the files fine via e, tabe, and drag/drop... |
Possibly related to #420 ? |
Possibly. ISTR it being escaped brackets as well. Ill have to check my install logs to see if Vim got bumped around this time. Did you update Vim lately? |
I don't know what ISTR is... but yes, this may be a newer version of Vim than I had before, though I'm not sure offhand. It is a new machine, and I switched to vundle and updated my plugins. It says it's |
"I seem to remember"
There should be a patch level with this (e.g., 7.4.475). |
|
I'm seeing this on 8.0, as well.
|
From my testing, the problem seems to occur when a file or directory name contains a [, any number of characters, and ]. The following filenames are problematic for me:
The following filenames open just fine:
|
Confirmed on |
I'm using Slackware 14.2 at the moment with the default package of gvim and i'm having the same issue. This concern directory opening as well. In case you wonder if it's a vim bug, it doesn't happen with the default file explorer. and it only affect files and directories with matching brackets. i.e. : |
I think the filename is probably treated as a regex somewhere and not escaped properly. Other regex-special characters probably also cause issues in nerdtree. |
Directly related to #680. This is a confirmed bug. |
+1, I suspect that this issue originetates from the fact that those names aren't escaped at some point, and they are interpreted as bash wildcards. |
@mathstuf @briandonahue @justfalter @przepompownia @Nausx @MrMino , would you be willing to test the pull request #868 I've put together for this issue? Details are in the PR. Thanks. |
With #868 I can open |
I am on holiday until 8/27, but will be happy to check it out after that if it still needs testing. |
Fixed in #868. |
$subject.
The text was updated successfully, but these errors were encountered: