-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Add support for --passthr{u,ough}
flag
#740
Comments
I was thinking about that myself. I personally think it's easier to do it the way i mentioned in that thread, but it seems like some people are quite passionate about it, and it would be very trivial to add a flag that wraps the pattern in |
I'm kind of meh on it, but I don't feel strongly enough to reject it outright.
I like @okdana's suggested implementation. |
If it were me i think i'd make it |
It does 😉 (You can also make it visible so it's findable in the help output) |
The --passthru flag causes ripgrep to print every line, even if the line does not contain a match. This is a response to the common pattern of `^|foo` to match every line, while still highlighting things like `foo`. Fixes #740
@jzinn both are supported. Ripgrep has no specific goal to be "formal." Please drop this. It's a waste of time. |
After reading this comment on HN, I thought it'd be neat to add support for the
--passthrough
/--passthru
flag in ripgrep as well.Thoughts?
The text was updated successfully, but these errors were encountered: