I've been trying to supply consult-find with multiple custom paths (which I'm figuring out dynamically depending on the default directory of a buffer -- I have a huge code base and only want to search some of it). Something like this:
(consult-find (my-cool-dir-list-builder))
Surprisingly, this fails to find any files whenever my-cool-dir-list-builder returns more that one path to search.
Long story short, this is the command consult-find is eventually running:
The -not ( -wholename */.* -prune ) part comes from the consult-find-args (it's the default). By the way, the paths I provide are absolute, but Consult rewrites them into relative form.
Now, the unfortunate thing is, a relative path like ../.. satisfies the -wholename */.* test (which I don't think is intentional).
I don't know what the correct fix is. Just thought I'd report this.
Hi!
I've been trying to supply
consult-findwith multiple custom paths (which I'm figuring out dynamically depending on the default directory of a buffer -- I have a huge code base and only want to search some of it). Something like this:Surprisingly, this fails to find any files whenever
my-cool-dir-list-builderreturns more that one path to search.Long story short, this is the command
consult-findis eventually running:The
-not ( -wholename */.* -prune )part comes from theconsult-find-args(it's the default). By the way, the paths I provide are absolute, but Consult rewrites them into relative form.Now, the unfortunate thing is, a relative path like
../..satisfies the-wholename */.*test (which I don't think is intentional).I don't know what the correct fix is. Just thought I'd report this.
Thanks!