mirror of
https://github.com/fish-shell/fish-shell
synced 2024-12-28 13:53:10 +00:00
c0d1e41313
Recent synopsis changes move from literal code blocks to [RST line blocks]. This does not translate well to HTML: it's not rendered in monospace, so aligment is lost. Additionally, we don't get syntax highlighting in HTML, which adds differences to our code samples which are highlighted. We hard-wrap synopsis lines (like code blocks). To align continuation lines in manpages we need [backslashes in weird places]. Combined with the **, *, and `` markup, it's a bit hard to get the alignment right. Fix these by moving synopsis sources back to code blocks and compute HTML syntax highlighting and manpage markup with a custom Sphinx extension. The new Pygments lexer can tokenize a synopsis and assign the various highlighting roles, which closely matches fish's syntax highlighing: - command/keyword (dark blue) - parameter (light blue) - operator like and/or/not/&&/|| (cyan) - grammar metacharacter (black) For manpage output, we don't project the fish syntax highlighting but follow the markup convention in GNU's man(1): bold text type exactly as shown. italic text replace with appropriate argument. To make it easy to separate these two automatically, formalize that (italic) placeholders must be uppercase; while all lowercase text is interpreted literally (so rendered bold). This makes manpages more consistent, see string-join(1) and and(1). Implementation notes: Since we want manpage formatting but Sphinx's Pygments highlighing plugin does not support manpage output, add our custom "synopsis" directive. This directive parses differently when manpage output is specified. This means that the HTML and manpage build processes must not share a cache, because the parsed doctrees are cached. Work around this by using separate cache locations for build targets "sphinx-docs" (which creates HTML) and "sphinx-manpages". A better solution would be to only override Sphinx's ManualPageBuilder but that would take a bit more code (ideally we could override ManualPageWriter but Sphinx 4.3.2 doesn't really support that). --- Alternative solution: stick with line blocks but use roles like :command: or :option: (or custom ones). While this would make it possible to produce HTML that is consistent with code blocks (by adding a bit of CSS), the source would look uglier and is harder to maintain. (Let's say we want to add custom formatting to the [|] metacharacters in HTML. This is much easier with the proposed patch.) --- [RST line blocks]: https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#line-blocks [backslashes in weird places]: https://github.com/fish-shell/fish-shell/pull/8626#discussion_r782837750
57 lines
2.6 KiB
ReStructuredText
57 lines
2.6 KiB
ReStructuredText
.. _cmd-fish_config:
|
|
|
|
fish_config - start the web-based configuration interface
|
|
=========================================================
|
|
|
|
Synopsis
|
|
--------
|
|
|
|
.. synopsis::
|
|
|
|
fish_config [browse]
|
|
fish_config prompt (choose | list | save | show)
|
|
fish_config theme (choose | demo | dump | list | save | show)
|
|
|
|
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 :ref:`funcsave <cmd-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 sample theme in the current session.
|
|
- ``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 sample themes.
|
|
- ``save`` saves the current prompt to :ref:`universal variables <variables-universal>`.
|
|
- ``show`` shows what the given sample theme (or all) would look like.
|
|
|
|
The themes are loaded from the theme directory shipped with fish or a ``themes`` directory in the fish configuration directory (typically ``~/.config/fish/themes``).
|
|
|
|
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.
|