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

Optionally ignore symlinks #66

Closed
blueyed opened this issue Mar 16, 2014 · 3 comments
Closed

Optionally ignore symlinks #66

blueyed opened this issue Mar 16, 2014 · 3 comments
Labels

Comments

@blueyed
Copy link
Contributor

blueyed commented Mar 16, 2014

I would like to ignore symlinks with Command-T (except for the one given, i.e. :CommandT /path/to/symlink would resolve the link, but links therein would be ignored).

I have found that there is a new file scanner (:let g:CommandTFileScanner='find'), where instead of the -L option -H would be used.

The ruby scanner would need to skip them here: https://github.com/wincent/Command-T/blob/master/ruby/command-t/scanner/file_scanner/ruby_file_scanner.rb#L66

@wincent wincent added the feature label Nov 7, 2014
@ghost
Copy link

ghost commented Aug 14, 2015

I've got a project which has as many as 12000 files, but when add new files to the project, i couldn't search the new files(foo) anyway in the root directory, but i could search files in it's own directory. I've also tried let g:CommandTMaxFiles=40000, which count is much lager then 12000, but it was still not work. And then i deleted folder one by one, tried to find out which folder interrupt the search. happenly when I delete the symlink to linux kernel source, everything goes well. I found there are 70325 files in linux-source directory. and my new added files are behind the the source code, so that's why i couldn't find it.

any new added files behind linux-26, would not be found, when g:CommandTMaxFiles is not large enough.

I also need to ignore the symlinks. thks.

# find
......
./Makefile
./config.h
./.gitignore
./.vim-bookmarks
./Bookmark.vim
./mygen
./mygen/mygen.sh
./linux-26
./foo
./foo/0
./foo/1
./foo/2

@wincent
Copy link
Owner

wincent commented Aug 14, 2015

Yeah, we can/should probably do this.

@wincent
Copy link
Owner

wincent commented Aug 26, 2022

Given the big rewrite for v6.0.x, I'm closing all older issues as there is unlikely to be anything significant happening on the 5-x-devel branch from here on1. Feedback issue for 6.0.x is here:

Footnotes

  1. Patches and PRs would be welcome, but my personal efforts are going to be directed towards main.

@wincent wincent closed this as not planned Won't fix, can't repro, duplicate, stale Aug 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants