-
-
Notifications
You must be signed in to change notification settings - Fork 815
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
Show symlink target? #482
Comments
I think you could do that with |
Thanks. I didn't know about I still think it might be nice to support it internally and not via |
Thank you for the feedback. I kind of like the idea, but it should be discussed first. It would certainly only be enabled in "interactive" mode (when not piping the output elsewhere). I see one obvious disadvantage of this behavior. If someone wants to "copy & paste" a list of found files from |
I would like to vote for this feature. I use |
see also: #491 |
Add a new `-l`/`--list` option to show more details about the search results. This is basically an alias for `--exec-batch ls -l` with some additional `ls` options. This can be used in order to: * see metadata like permissions, owner, file size, modification times (#491) * see symlink targets (#482) * achieve a determinstic output order (#324, #196, #159) * avoid duplicate search results when multiple search paths are given (#405)
Add a new `-l`/`--list` option to show more details about the search results. This is basically an alias for `--exec-batch ls -l` with some additional `ls` options. This can be used in order to: * see metadata like permissions, owner, file size, modification times (#491) * see symlink targets (#482) * achieve a deterministic output order (#324, #196, #159) * avoid duplicate search results when multiple search paths are given (#405)
Add a new `-l`/`--list` option to show more details about the search results. This is basically an alias for `--exec-batch ls -l` with some additional `ls` options. This can be used in order to: * see metadata like permissions, owner, file size, modification times (#491) * see symlink targets (#482) * achieve a deterministic output order (#324, #196, #159) * avoid duplicate search results when multiple search paths are given (#405)
In #556, I have implemented a new @wpcarro @danielecook I hope that's fine for your use case. |
This fits my use-case exactly. Thank you, @sharkdp |
This has now been released in fd v8.0. |
so my .gitignore ignores a few build temporary dirs, but I need find files there once a file, fd will quietly ignore them, and I have to return to 'find'. is there a way to set a local file that has higher priority than .gitignore, say .gitfd, that once it's there, fd will prefer it to .gitignore. .gitignore is for git to manage code(commit or not), but fd should do more, and could we have a way to do that like described above? |
@laoshaw you tell If you just want exceptions to .gitignore, you can add a negated rule to your .fdignore file. So, say if you have But also, what does this have to do with showing symlink targets? |
That works. Nothing to do with symlink, it's when I could not find the symlinks in a directory I first thought it's because fd can not do symlinks, then realized it's because of .gitignore has that directory. Thanks. |
Thanks for making
fd
. I love it and I've been using it heavily for about a year.I was wondering if it was possible to display the targets of symlinks for commands like:
I couldn't find anything in the documentation about this, but it would be a nice addition.
The text was updated successfully, but these errors were encountered: