how do I force ripgrep to search the CWD instead of reading from a pipe?

[AndersMunch]

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:

import subprocess
subprocess.check_output(['rg','SomeSearchTerm'])

But never mind the reason, I would just like an option to fix it.

[BurntSushi]

Why doesn't rg foo ./ work?

[AndersMunch]

Good point. rg foo . does work. I just never used the second argument, so I didn't think of it.

[BurntSushi]

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.

[TwoF1nger]

Does it make sense for -r to also override the heuristics and ignore the opened stdin? It currently doesn't. (15.1.0)

Edit: Oh, my bad. -r does something completely different here. Sorry.