forked from fish-shell/fish-shell
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Teach autoloader to read embedded files
This will load the functions and completions from inside of the fish binary. That means its no longer necessary to *install* a self-installable build for basic functionality. The functions/completions will be loaded *last*, so they are still overridable via a file on disk (with the exception of generated_completions, which we only use as a fallback if no completions exist). It still needs to extract files that are to be used by other tools, including the man pages, fish_config.py, the man page completion generator. The remaining issues: - It no longer prompts to install, but if you tried `fish_config` after this it would fail to open the tool, and it would be easy to forget to update those files So: When and how should this remind you that these files need to be extracted? Do we want e.g. a builtin that checks the version file (`status installed`)? This could then be run by `fish_config` and `help` and tell you to run `fish --install`. - `builtin --help` will fail - we could read these things from inside, but we'd need groff for that. Do we want to pre-process these and put them in the builtins themselves? Do we want to print these on demand in `__fish_print_help` to groff? - It's not gated behind the installable feature. - What directories need to still be defined? Does $__fish_data_dir need to keep existing? Technically this *could* be the main distribution method. Maybe we could let distro packages skip the embedded documentation and external files, but keep the functions/completions in the binary.
- Loading branch information
Showing
4 changed files
with
184 additions
and
72 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.