"exited abnormally with code 1" when trying "type" or "glob" about deadgrep HOT 2 CLOSED

@pmiddend ripgrep returns an exit code of 1 when there are no results. It doesn't mean that there's anything wrong necessarily. I've always thought that it's a slightly odd behaviour, but it's consistent with grep.

@PuercoPop FWIW deadgrep does try to enforce a match of a known search term, so you shouldn't be able to specify a search type of erb.

have you considered a dedicated process buffer like magit that can be opened on $?

I do think we'll need some kind of debugging tool to help with bug reports. I'm reluctant to expose all the raw search data as it can be big when you have a lot of results, and it's not very readable when Emacs shows the raw ASCII control characters. It's also possible to have multiple searches running simultaneously, unlike magit, so I can't have a single *deadgrep-output* buffer.

from deadgrep.

I ran into a similar issue when trying to pass erb as the type, turns out rg doesn't support the erb type .(although you can add it as a command flag).

To get a better idea of what is going on in your case I recommend you can rg from the CLI to be able to read its error message. You'll need to findout how deadgrep is invoking rg. To do so, you can use edebug on deadgrep--start to get the values of return by (format "rg %s" search-term) and (deadgrep--format-command.

@Wilfred have you considered a dedicated process buffer like magit that can be opened on $?

from deadgrep.