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

--changed-within/--changed-before not working with directories #470

Closed
mrzool opened this issue Aug 17, 2019 · 4 comments · Fixed by #480
Closed

--changed-within/--changed-before not working with directories #470

mrzool opened this issue Aug 17, 2019 · 4 comments · Fixed by #480
Labels

Comments

@mrzool
Copy link

mrzool commented Aug 17, 2019

Took me a while to figure out… these options work fine when searching files, they don’t currently work when searching directories (thus when -t d is given).

Grateful for pointers.

Thanks for this amazing little tool.

@sharkdp
Copy link
Owner

sharkdp commented Sep 13, 2019

Thank you for reporting this!

I hope this could be fixed really easily by removing this condition:

fd/src/walk.rs

Line 358 in a0505bd

if entry_path.is_file() {

I'm not sure why it is there. It could be a copy&paste error from the size-constraints block above (where is_file is actually needed).

@sharkdp
Copy link
Owner

sharkdp commented Sep 15, 2019

Fixed in v7.4.0.

@chiefjester
Copy link

Hi, @sharkdp. Thank you for the fix. 🤝🏻 I've also got bitten by this, 😅, Like @mrzool, it took me a while to figure out that it wasn't working in directories. Ubuntu's still at v7.2. When I've updated it to v7.4.0 seems the problem went away.

I'm not sure if we should add in the README to use the latest version for the latest bugfixes. I wouldn't want people to get the same experience as me, especially if their time is really precious.

@sharkdp
Copy link
Owner

sharkdp commented Jan 9, 2020

@thisguychris Thank you for the feedback.

Ubuntu's still at v7.2. When I've updated it to v7.4.0 seems the problem went away.

I'm not sure if we should add in the README to use the latest version for the latest bugfixes

To be honest, I don't think so. That's a very general problem that appears with any kind of software. If you are using outdated versions, you might not have the latest bugfixes. This is not a critical bug, so I don't think any further action is required.

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