-
-
Notifications
You must be signed in to change notification settings - Fork 816
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
Support ripgrep's --path-separator option #428
Comments
What happened to this in #429? I see that PR got closed without comment. |
I did not see a great interest for it. I would be happy to see this merged, but I don't want to keep pinging. When I need the feature, I use my fork. |
I think there is some interest for it (see also the discussion in #153). If you closed the PR because there was no response from my side, let me assure you that it was only a lack of time, not lack of interest 😄 |
Great! When can we expect to see a windows release which includes this? https://github.com/sharkdp/fd/releases |
Released in v7.4.0. |
On windows (both cygwin and cmd.exe shells) the output is with backslashes as path separator. However, one sometimes would want to interop with windows port of unix tools and get slash-separated paths.
When using ripgrep, one can override the path separator with the
--path-separator
option. I think it would be great to support it in fd as well.This should also allow working around issues like #153.
reference: the ripgrep discussion BurntSushi/ripgrep#275
The text was updated successfully, but these errors were encountered: