mirror of
https://github.com/fish-shell/fish-shell
synced 2025-01-15 06:24:01 +00:00
22332b892d
The documentation states that running `fish_config theme save` after `fish_config theme choose [theme_name]` will result in "saving" the currently chosen theme, but this does not match the actual behavior of `fish_config theme save` which expects a trailing argument specifying the name of the theme to select/persist. Given that the documented way has been included in a release and that it makes more sense than calling `fish_config theme save xxx` when you are *loading from* xxx and not *saving to* xxx, this patch revises `fish_config.fish` to support the documented behavior. When `fish_config theme save xxx` is used, xxx is loaded w/ its specified colors saved to the according variables in the universal scope. But if `fish_config theme save` is used without a theme's name specified, then the currently specified (known) fish color variables are persisted from whatever scope they're currently in (usually in the global scope from previewing a theme) to universal variables of the same name. This does *not* catch color variables unknown to fish! If a theme and a prompt agree on some variable to hold some color but it's not a color variable known to fish, it won't be persisted! Closes #9088. |
||
|---|---|---|
| .. | ||
| completions | ||
| functions | ||
| groff | ||
| tools | ||
| __fish_build_paths.fish.in | ||
| config.fish | ||
| lynx.lss | ||