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

nerdtree does not support file or directory has comma in it. #314

Closed
Yggdroot opened this issue Feb 17, 2014 · 4 comments · Fixed by #873
Closed

nerdtree does not support file or directory has comma in it. #314

Yggdroot opened this issue Feb 17, 2014 · 4 comments · Fixed by #873
Assignees

Comments

@Yggdroot
Copy link

This is a bug.

@mb720
Copy link

mb720 commented Apr 3, 2016

Hi,

I just stumbled over this bug and would like to give more details and instructions how to reproduce it:

  1. Create a file at ~/Desktop/dir , with , commas/testFile.txt
  2. Open it in Vim
  3. Execute :NERDTreeFind

This results in the following error message:

Error detected while processing function 45_findAndRevealPath:
line 44:
E716: Key not present in Dictionary: putCursorHere

I'm on Windows 10, 64 bits and have the latest version of NERDTree (git pull tells me that there's nothing to update).

Thanks a lot in advance.

@PhilRunninger
Copy link
Member

PhilRunninger commented Dec 20, 2017

@Yggdroot @mb720 My Windows VM is acting up on my machine, so I can't test it there. The bug doesn't exist, or was fixed, in MacOS. Can you try the newest commit to see if the issue still exists?

@lifecrisis
Copy link
Contributor

lifecrisis commented Dec 20, 2017

@PhilRunninger, I'm using Windows right now. Here's what I can confirm...

  1. I can create dir , with , commas\test.txt, but opening the directory with o fails to show the child node.
  2. It looks like the problem with :NERDTreeFind reported by @mb720 was the same as A newly written file cannot be found with NERDTreeFind #779. It may also be related to the commas, but we can't know until we fix the other problem.

As I recall, spaces in the file name can be an issue, but I remember that only being a problem at the beginning of the file name.

@PhilRunninger
Copy link
Member

PhilRunninger commented May 2, 2018

@lifecrisis, Not a bug in Mac. It looks like something may have done around Jan 5 to fix this.

@PhilRunninger PhilRunninger self-assigned this Aug 14, 2018
@PhilRunninger PhilRunninger added the PR Under Review Coding is finished, and a pull request has been created and is being reviewed. label Aug 14, 2018
@PhilRunninger PhilRunninger removed the PR Under Review Coding is finished, and a pull request has been created and is being reviewed. label Aug 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants