Question - what's the proper way to ignore an executable

Let’s say you have a 3rd party script that tries to be support multiple different binaries (vlc and mpv as an example) and uses command -v mpv to check for it on the path.

We probably just want to pick one and ignore the other.

What is the proper way to handle that?

[peterhoeg]

I was going about it in the wrong way. Apologies for the noise.

[abathur]

Gotcha. Fair. Explicit is good…

You could probably add a tail comment block in resholve’s format with the corresponding resholve directive, but I suspect that’s too far from the invocations to be satisfying (and it would need maintenance if the resholve schema changes).

I guess we could sanction a descriptively-named ~magic non-existing command that resholve special-cases, but documenting it would muddy the message that resholve doesn’t entail injecting cruft into scripts that renders them unusable in other environments…

I suppose you could do a cheap version of the same with a descriptive internal function that just runs “$@”? (Though I’ll note that seeing through invoking shell functions is on the ~someday list. No plan, but I might eventually break it. Better lore/parsers for common commands are higher up the list I think.)