Add an option similar to -o, --only-matching about ripgrep

[gavinfoley]

To counterbalance the above comment, I wanted to say that I use and enjoy this excellent tool you've created every day, and I appreciate whatever improvements are made whenever they are made. Thanks for using some of your limited free time to make my life and others' easier.

[BurntSushi]

@sergeevabc This issue tracker isn't place to give me advice on how to schedule my free time or to shame anyone into doing work on their free time. Future comments in that vain won't be tolerated.

[22a]

Wonderful, thank you for the great work @kpp + @BurntSushi 🎉

[BurntSushi]

@sergeevabc I don't know. It happens when it happens. I do this in my free time and I don't typically schedule my free time in advance. Sorry.

[BurntSushi]

--replace already exists (and I agree it's kind of verbose for this case).

-o/--only-matching is an option on grep, so I'm OK adding this.

[BurntSushi]

@sergeevabc Yes, it would solve your problem. But there is a work-around for now:

$ host -t A wikipedia.org | openssl dgst -sha256 | rg -N '^.*([A-Fa-f0-9]{64}).*$' --replace '$1'

[cwillu]

Note that surrounding the search regex with .( ). and then using --replace $1 will do this; pretty verbose though, especially when using it in a pipeline.

[sergeevabc]

Input

host -t A wikipedia.org | openssl dgst -sha256 | rg --no-line-number [A-Fa-f0-9]{64}

Output

(stdin)= 0d00409623da8ae039de83200af7f6fa9211bb13e1b3e10ea45142cd08b3e50b

Hash is coloured red, but I need hash (that red part) only.
Would the considered option --only-matching be of help?

[sergeevabc]

@BurntSushi, thanks, but when --only-matching will be implemented?