Closed ForLoveOfCats closed 4 years ago
What version of ripgrep is this and what OS is this? The empty string at the begining of the type list should be the problem but I don't know why you get that.
Ok, I have essentially the same environgment (linux rg version) so no clue there. There is an empty string at the end of the type list though coming from splitting the output from rg --type-list
on newline. That one is filtered out to avoid these kind of problems.
I guess the simplest solution to this is just to handle empty strings gracefully when processing the list. Should make it more resiliant to any strangeness in this area.
Pushed a fix now. Let's see if this works.
I can confirm that the issue has been resolved on my system! Thanks for your time and effort on this library!
When running the simple
(rg-run "foo" "*.baz" default-directory)
the errorWrong type argument: stringp, nil
is emitted. This doesn't make much sense as the tests are littered with calls such as this one(rg-run "foo" "*.baz" (concat default-directory "dirlocals"))
. My local rg.el version is up to date with Melpa (not Melpa stable).Debugger trace: