You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I have noticed that --exclude flag does not accept an absolute path as argument. Indeed
both commmands
$ pwd
/home/user
fd --hidden --exclude /home/user/beta kate
fd --hidden --exclude=/home/user/beta kate
were still searching /home/user/beta. I have noticed that because such path is a SSHFS remote mount and I could notice activity on such path.
To make sure fd was not searching inside such path I had to use the relative name
fd --hidden --exclude beta kate
fd --hidden --exclude=beta kate
I think it would be nice to be able to use absolute path too.
Thank your for your work on fd and have a nice day
The text was updated successfully, but these errors were encountered:
So the patrern passed to --exclude is interpreted similar to a gitignore pattern. That means that if it starts with a "/", then it is relative to the root search path.
So to support this, we would probably need a new option.
Hello, I have noticed that
--exclude
flag does not accept an absolute path as argument. Indeedboth commmands
were still searching
/home/user/beta
. I have noticed that because such path is a SSHFS remote mount and I could notice activity on such path.To make sure
fd
was not searching inside such path I had to use the relative nameI think it would be nice to be able to use absolute path too.
Thank your for your work on fd and have a nice day
The text was updated successfully, but these errors were encountered: