-
-
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
machine interface #462
Comments
How about existing |
#244 is related. May be worthwhile to see if what is outlined there differs from your requirements. |
I use mostly search with context:
Those contexts lines are really useful, so I really work on AgGroup (not the commands related with quicklist). Parsing results with context slows the interaction and is error prone @tiehuis That would help to highlight without reprocess regex (with the escape characters hell) Deterministic results like:
etc etc woud be great as there's lot of info rg knows but do not expose (reflected in highlights for example) |
Just to add, here (#359) was a similar issue regarding structured output (which looks very much the same as what you are suggesting) and a response from BurntSushi. |
@tiehuis Thanks that's exactly what I need. I was afraid to ask for a library, but seems there's a work in progress. That's perfect for another idea I have for rg (use on gnome builder as a global search albfan/gnome-builder#14) Then we need to contribute on rg library. That makes sense, thanks! |
Hi, I'm the maintainer of https://github.com/albfan/ag.vim
Someone ask me to integrate with rg, and after trying it is sensibly faster than ag so want to ask if it's possible to add an option to expose results in a parseable way ready for machines.
By now I'm parsing filename, column, line and contents from
--group
option so this is not a stopper, but would be great to offer results that way to ease maintenance and complex features like hightlight codeMaybe
--porceain
could be a great name for option. Anything will workThe text was updated successfully, but these errors were encountered: