Travis A. Everett

There is. The _ideal_ outcome of these is to improve resholve and/or binlore to fix it for everyone, but when you need a short-term workaround, you can add `execer` lore...

I'll have to iterate towards "how to"; it's a little more fundamental for now. I'll definitely need help scaling it out, but I'm leery of investing a lot of potential...

good catch :) changed from "long-tail lore" to "lore for less-common packages"

> Is this a bug? Not really a bug, per se, but it is something resholve can't handle yet--so it's fine to have an open issue about it. > Currently...

Shell is too dynamic for a 100% solution to be feasible, so resholve generally aims to grow towards something like a 80-90%ish sort of solution. This class of resolution basically...

The effort to resholve airgeddon hinges on this as well. https://github.com/v1s1t0r1sh3r3/airgeddon/blob/c58bb8f086ab47cf918399f019bd502dbd430b76/airgeddon.sh#L383 for example will fail into trying to download the strings.

Egh :) _My kingdom for a cli syntax parser that's a better fit for what we need._ I think the positional arg is causing this. ~~Probably need to make a...

I pushed a tentative fix in https://github.com/abathur/resholve/commit/39f5012b419c97343b31d3aebba542d9c1c62907 if you're able to test it?

> Shouldn’t ls have been resolved, or am I misunderstanding how fake directives are supposed to work? As implemented, fake directives preempt resolution, and sub-exec is part of resolution. That...

This is expected (for now, at least). It's documented in the manpage (here's an excerpt from the plaintext copy): https://github.com/abathur/resholve/blob/80e93633c824175e8afb25b0fa02aee35203e6fc/docs/resholve.1.txt#L202-L213 In the near-ish term, we can probably: - [ ]...