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
mrmonday opened this issue
Dec 11, 2017
· 2 comments
Labels
duplicateAn issue that is duplicative of another.questionAn issue that is lacking clarity on one or more points.wontfixA feature or bug that is unlikely to be implemented or fixed.
I thought it might be good to normalise by default, so I did a little investigation:
grep in git bash (find does similarly):
$ grep -r aa 'a\'
a\/c/b:aaaa
$ grep -r aa 'a/'
a/c/b:aaaa
findstr in cmd: I couldn't find a way to make it recurse, but it prints exactly as passed
dir in cmd: This always normalises to \
Get-ChildItem a/ -Recurse in powershell normalises to \
I'm no expert in Window's command line utilities, but my minor investigation reveals quite a mixed bag of results - there's no definitive "ripgrep should do this because it's what everything else does".
I'll close this, since --path-separator is a sufficient workaround. Thanks.
duplicateAn issue that is duplicative of another.questionAn issue that is lacking clarity on one or more points.wontfixA feature or bug that is unlikely to be implemented or fixed.
Using either cmd or git bash on windows:
Here the output mixed
/
and\
as directory separators - they should be normalised for consistency.The text was updated successfully, but these errors were encountered: