mirror of
https://github.com/fish-shell/fish-shell.git
synced 2026-05-02 11:01:15 -03:00
190d367bc4
Implicitly-universal variables have some downsides:
- It's surprising that "set fish_color_normal ..."
and "set fish_key_bindings fish_vi_key_bindings" propagate to other
shells and persist, especially since all other variables (and other
shells) would use the global scope.
- they don't play well with tracking configuration in Git.
- we don't know how to roll out updates to the default theme (which is
problematic since can look bad depending on terminal background
color scheme).
It's sort of possible to use only globals and unset universal variables
(because fish only sets them at first startup), but that requires
knowledge of fish internals; I don't think many people do that.
So:
- Set all color variables that are not already set as globals.
- To enable this do the following, once, after upgrading:
copy any existing universal color variables to globals, and:
- if existing universal color variables exactly match
the previous default theme, and pretend they didn't exist.
- else migrate the universals to ~/.config/fish/conf.d/fish_frozen_theme.fish,
which is a less surprising way of persisting this.
- either way, delete all universals to do the right thing for most users.
- Make sure that webconfig's "Set Theme" continues to:
- instantly update all running shells
- This is achieved by a new universal variable (but only for
notifying shells, so this doesn't actually need to be persisted).
In future, we could use any other IPC mechanism such as "kill -SIGUSR1"
or if we go for a new feature, "varsave" or "set --broadcast", see
https://github.com/fish-shell/fish-shell/issues/7317#issuecomment-701165897
https://github.com/fish-shell/fish-shell/pull/8455#discussion_r757837137.
- persist the theme updates, completely overriding any previous theme.
Use the same "fish_frozen_theme.fish" snippet as for migration (see above).
It's not meant to be edited directly. If people want flexibility
the should delete it.
It could be a universal variable instead of a conf snippet file;
but I figured that the separate file looks nicer
(we can have better comments etc.)
- Ask the terminal whether it's using dark or light mode, and use an
optimized default. Add dark/light variants to themes,
and the "unknown" variant for the default theme.
Other themes don't need the "unknown" variant;
webconfig already has a background color in context,
and CLI can require the user to specify variant explicitly if
terminal doesn't advertise colors.
- Every variable that is set as part of fish's default behavior
gets a "--label=default" tacked onto it.
This is to allow our fish_terminal_color_theme event handler to
know which variables it is allowed to update. It's also necessary
until we revert 7e3fac561d (Query terminal only just before reading
from it, 2025-09-25) because since commit, we need to wait until
the first reader_push() to get query results. By this time, the
user's config.fish may already have set variables.
If the user sets variables via either webconfig, "fish_config theme
{choose,save}", or directly via "set fish_color_...", they'd almost
always remove this label.
- For consistency, make default fish_key_bindings global
(note that, for better or worse, fish_add_path still remains as
one place that implicitly sets universal variables, but it's not
something we inject by default)
- Have "fish_config theme choose" and webconfig equivalents reset
all color variables. This makes much more sense than keeping a
hardcoded subset of "known colors"; and now that we don't really
expect to be deleting universals this way, it's actually possible
to make this change without much fear.
Should have split this into two commits (the changelog entries are
intertwined though).
Closes #11580
Closes #11435
Closes #7317
Ref: https://github.com/fish-shell/fish-shell/issues/12096#issuecomment-3632065704
116 lines
4.4 KiB
ReStructuredText
116 lines
4.4 KiB
ReStructuredText
fish_config - start the web-based configuration interface
|
|
=========================================================
|
|
|
|
Synopsis
|
|
--------
|
|
|
|
.. synopsis::
|
|
|
|
fish_config [browse]
|
|
fish_config prompt (choose | list | save | show)
|
|
fish_config theme
|
|
fish_config theme choose THEME [ --color-theme=(dark | light) ]
|
|
fish_config theme demo
|
|
fish_config theme dump
|
|
fish_config theme list
|
|
fish_config theme show [THEME...]
|
|
|
|
Description
|
|
-----------
|
|
|
|
``fish_config`` is used to configure fish.
|
|
|
|
Without arguments or with the ``browse`` command it starts the web-based configuration interface. The web interface allows you to view your functions, variables and history, and to make changes to your prompt and color configuration. It starts a local web server and opens a browser window. When you are finished, close the browser window and press the Enter key to terminate the configuration session.
|
|
|
|
If the ``BROWSER`` environment variable is set, it will be used as the name of the web browser to open instead of the system default.
|
|
|
|
With the ``prompt`` command ``fish_config`` can be used to view and choose a prompt from fish's sample prompts inside the terminal directly.
|
|
|
|
Available subcommands for the ``prompt`` command:
|
|
|
|
- ``choose`` loads a sample prompt in the current session.
|
|
- ``list`` lists the names of the available sample prompts.
|
|
- ``save`` saves the current prompt to a file (via :doc:`funcsave <funcsave>`).
|
|
- ``show`` shows what the given sample prompts (or all) would look like.
|
|
|
|
With the ``theme`` command ``fish_config`` can be used to view and choose a theme (meaning a color scheme) inside the terminal.
|
|
|
|
Available subcommands for the ``theme`` command:
|
|
|
|
- ``choose`` loads a theme in the current session.
|
|
To override :envvar:`fish_terminal_color_theme`, pass the ``--color-theme`` argument.
|
|
- ``demo`` displays some sample text in the current theme.
|
|
- ``dump`` prints the current theme in a loadable format.
|
|
- ``list`` lists the names of the available themes.
|
|
- ``show`` shows what the given themes (or all) would look like.
|
|
- *(deprecated, avoid use)* ``save`` saves the given theme to :ref:`universal variables <variables-universal>`.
|
|
|
|
The **-h** or **--help** option displays help about using this command.
|
|
|
|
.. _fish-config-theme-files:
|
|
|
|
Theme Files
|
|
-----------
|
|
|
|
``fish_config theme`` and the theme selector in the web config tool load their themes from theme files. These are stored in the fish configuration directory, typically ``~/.config/fish/themes``, with a .theme ending.
|
|
|
|
You can add your own theme by adding a file in that directory.
|
|
|
|
To get started quickly::
|
|
|
|
fish_config theme dump > ~/.config/fish/themes/my.theme
|
|
|
|
which will save your current theme in .theme format.
|
|
|
|
The format looks like this:
|
|
|
|
.. highlight:: none
|
|
|
|
::
|
|
|
|
# name: 'My Theme'
|
|
|
|
[light]
|
|
# preferred_background: ffffff
|
|
fish_color_normal 000000
|
|
fish_color_autosuggestion 7f7f7f
|
|
fish_color_command 0000ee
|
|
|
|
[dark]
|
|
# preferred_background: 000000
|
|
fish_color_normal ffffff
|
|
fish_color_autosuggestion 7f7f7f
|
|
fish_color_command 5c5cff
|
|
|
|
[unknown]
|
|
fish_color_normal normal
|
|
fish_color_autosuggestion brblack
|
|
fish_color_cancel -r
|
|
fish_color_command normal
|
|
|
|
The comments provide name and background color to the web config tool.
|
|
|
|
Themes can have three variants,
|
|
one for light mode,
|
|
one for dark mode,
|
|
and one for terminals that don't :ref:`report colors <term-compat-query-background-color>` (where :envvar:`fish_terminal_color_theme` is set to ``unknown``).
|
|
|
|
The other lines are just like ``set variable value``, except that no expansions are allowed. Quotes are, but aren't necessary.
|
|
|
|
.. _fish_config-color-variables:
|
|
|
|
Other than that, .theme files can contain any variable with a name that matches the regular expression ``'^fish_(?:pager_)?color_.*$'`` - starts with ``fish_``, an optional ``pager_``, then ``color_`` and then anything.
|
|
|
|
Example
|
|
-------
|
|
|
|
``fish_config`` or ``fish_config browse`` opens a new web browser window and allows you to configure certain fish settings.
|
|
|
|
``fish_config prompt show`` demos the available sample prompts.
|
|
|
|
``fish_config prompt choose disco`` makes the disco prompt the prompt for the current session. This can also be used in :ref:`config.fish <configuration>` to set the prompt.
|
|
|
|
``fish_config prompt save`` saves the current prompt to an :ref:`autoloaded <syntax-function-autoloading>` file.
|
|
|
|
``fish_config prompt save default`` chooses the default prompt and saves it.
|