-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
request: option for literal searching #190
Comments
Indeed it does. It uses the same flag as grep does:
Note that |
Oh geeze. When I saw -Q didn't work, I looked at the list of flags, but apparently I only looked at the "Less common options" section and ignored the top, thinking that the top was a summary and the longer descriptions beneath had all the flags. But now that I've actually read the section header it's obvious that it's not describing the most common options. |
Yeah, if you have any suggestions on how to make the docs clearer, I would be happy to hear them. I don't think --help is that great today, and I mostly intended the top section to be options that i thought were either more common or somehow more important, but the categorization is something i came up with willy nilly. Maybe it should have more sections? Or one big one? |
Honestly, I think the best solution would be to have a manpage. The problem with |
There is a man page. :-) In #189, it was suggested to show less on |
There is? Does cargo just not know how to install it? |
Correct. |
Yes it does. It uses the standard Note that this should never be used for performance reasons. Its only use On Oct 21, 2016 14:23, "Kevin Ballard" notifications@github.com wrote:
|
You should probably stop advertising any compatibility with ag/ack if you don't make an effort to match their arguments.... Why copy from grep when you advertise copying from ag/ack? It makes no sense, and ripgrep is harder to use because of it. It's also very difficult to find in the man because you don't use 'literal', 'quote', 'exact', or any other terminology people are likely to use. "Fixed strings" is a terrible phrase that can mean anything. What is a non fixed string? |
@duane Can you please point me to the place where ripgrep advertises "compatibility with ag/ack" so that I can fix it? No such promise is intended. No such promise for grep is intended either. ripgrep does take inspiration from those tools though. Documentation can always be improved. I'm not perfect.
"literal" is there: https://github.com/BurntSushi/ripgrep/blob/master/doc/rg.1#L61 --- It's also in the FWIW, the |
The help is pretty large. I spent a minute reading through it and then just searched the internet and came here. |
The "literal" reference in --help refers to a regular expression, not a literal. Edited to remove snark. The documentation does not seem accurate to me. Re: ack and ag, it's not clear why this is undesirable—they have a much more approachable interface, and I would be happy to explain why if you indicate interest. |
What is inaccurate about it...?
|
I use
ag -Q
(orag --literal
) fairly often to do a literal search across files, since it's so fast and colorizes the output. I'd love to be able to userg
this way, exceptrg
doesn't seem to have any support for literal searching.The text was updated successfully, but these errors were encountered: