More often than not, one would use an external grep (ack, ag or perhaps ripgrep) to search in the project blazing fast.
Blazing fast doesn't really align with having to look at the output in a very-plan text format, then pressing enter before ViM will parse it beautifully into the QuickFix or Location list.
There are many hacky ways to get this sorted: defining :Grep and :Make as user-defined commands (not really playing nice with everything else that might expect to call `:grep), using the internal grep (which is slow and exactly the opposite of the initial idea here).
Trying to fiddle around with the shellpipe variable doesn't help either - even if I remove the tee part, I still see the output "twice" (once in the terminal, and once in the QuickFix list).
From a UNIX perspective, it's an obvious solution to change the behaviour of shellpipe to capture everything, unless tee is used; not sure, how we could achieve the same on Windows and the like.
Alternatively, I'd propose to introduce a new boo variable that would control this, perhaps shellquiet and noshellquiet or similar.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Instead of a new option, I think you could temporarily increase 'cmdheight' option, no?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Not sure, that would help with a whole page (or more) worth of grep` output...
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
In my vimrc I have set
&grepformat = '%f:%l:%c:%m'
&grepprg = 'rg --vimgrep -uu'
There is no prompt, if I put 'silent' before 'grep': :silent grep ...
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I know that this is not the requested feature, but just in case you can also remove the extra terminal noise by setting:
set shellpipe=>%s\ 2>&1
This redirects both stdout and stderr into the file Vim uses for the quickfix list, so you don’t see the output twice.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
This is also useful to automate sos report collection from multiple OCP nodes without interaction
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
This is also useful to automate sos report collection from multiple OCP nodes without interaction
I cannot parse that sentence. Did you try the :silent solution?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()