You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like an option to tell ripgrep, that despite being connected to a pipe, it should not search standard input, so that it will do a normal recursive search.
Don't know about the name. --no-pipe, perhaps?
Motivation
ripgrep does not work from within Emacs when used as the grep-command on Windows. It exits immediately with error code 1, or hangs.
I suspect this is related to issue #951, something to do with stdin being a "fifo"? I'm not sure what that's supposed to mean, from what I can see Emacs is just running a bog standard inferior process - and indeed trying to run ripgrep as a Python subprocess exhibits the same problem, this hangs:
The key insight is that by omitting the path argument you are basically saying, "ripgrep, please guess whether to search the current working directory or stdin." Due to idiosyncracies in how processes are created in various contexts, it is impossible for ripgrep to guess correctly 100% of the time.
Repository owner
locked and limited conversation to collaborators
Aug 16, 2023
Describe your feature request
I would like an option to tell ripgrep, that despite being connected to a pipe, it should not search standard input, so that it will do a normal recursive search.
Don't know about the name.
--no-pipe
, perhaps?Motivation
ripgrep does not work from within Emacs when used as the grep-command on Windows. It exits immediately with error code 1, or hangs.
I suspect this is related to issue #951, something to do with stdin being a "fifo"? I'm not sure what that's supposed to mean, from what I can see Emacs is just running a bog standard inferior process - and indeed trying to run ripgrep as a Python subprocess exhibits the same problem, this hangs:
But never mind the reason, I would just like an option to fix it.
The text was updated successfully, but these errors were encountered: