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

NERDTreeFind does not mark hidden file #189

Closed
stabilobox opened this issue Aug 22, 2012 · 3 comments · Fixed by #202
Closed

NERDTreeFind does not mark hidden file #189

stabilobox opened this issue Aug 22, 2012 · 3 comments · Fixed by #202
Labels

Comments

@stabilobox
Copy link

For a hidden file the :NERDTreeFind will find the CWD but doesn't place the cursor on the file. Rather it marks the first directory entry.

E.g. open ~/.vimrc and do :NERDTreeFind

A :NERDTreeFind I also does not do the trick.

@mboughaba
Copy link
Contributor

mboughaba commented Nov 10, 2017

  • When the hidden file is in the root of cwd
    I get this issue too on GViM (Windows). It works fine on Linux.
    I suspect that wrong os slash is used in the code (partially fix applied by Make NERDTreeFind work on hidden files #202)

  • When the hidden file is in a subdirectory
    hidden files is not revealed in both vim and gvim (unix and windows)

@lifecrisis
Copy link
Contributor

Thanks for the report, guys. Just confirmed this bug. It will take some investigation to fix this properly.

@lifecrisis lifecrisis added the bug label Nov 10, 2017
lifecrisis added a commit that referenced this issue Jan 5, 2018
Here, a more accurate method of determining whether or not to show
hidden files is used.  A new method, "isHiddenUnder()" is defined
for "Path" objects.  This method is then used to set the flag for
hidden files in the ":NERDTreeFind" command.  Note that this
function is likely to be useful elsewhere.

Fixes #189.
@lifecrisis
Copy link
Contributor

@mboughaba and @stabilobox, you should both be able to update the NERDTree and have your problem fixed. Let me know if the issue is not corrected...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants