3 ms·
Idk if fish has ever shipped builtins that way, but doing so is pretty conventional and doesn't normally put those executables on the PATH. It's what libexec is
by pxc 3y ago
Idk if fish has ever shipped builtins that way, but doing so is pretty conventional and doesn't normally put those executables on the PATH. It's what libexec is for: https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.htm...
If you wanna add a builtin like that to your own distribution of fish, you could do it cleanly by keeping those binaries in /usr/lib or /usr/libexec and then wrapping them in a fish function that ships in fish's install prefix. (This is basically how fish's Python scripts for generating completions from manpages are shipped today.)
- em-bee 3y agodoesn't normally put those executables on the PATH right, i don't remember the details, but when it happened it was probably fixed quickly. could even have been a packaging error in a distribution.