2018-12-16 08:23:36 +08:00
|
|
|
# -*- coding: utf-8 -*-
|
|
|
|
#
|
|
|
|
# Configuration file for the Sphinx documentation builder.
|
|
|
|
#
|
|
|
|
# This file does only contain a selection of the most common options. For a
|
|
|
|
# full list see the documentation:
|
|
|
|
# http://www.sphinx-doc.org/en/master/config
|
|
|
|
|
|
|
|
import glob
|
|
|
|
import os.path
|
2019-09-19 14:51:40 +08:00
|
|
|
import subprocess
|
2022-01-16 20:23:09 +08:00
|
|
|
import sys
|
2021-12-13 02:44:47 +08:00
|
|
|
from sphinx.errors import SphinxWarning
|
|
|
|
from docutils import nodes
|
2018-12-16 08:23:36 +08:00
|
|
|
|
|
|
|
# -- Helper functions --------------------------------------------------------
|
|
|
|
|
2019-05-05 18:09:25 +08:00
|
|
|
|
2020-10-29 06:18:48 +08:00
|
|
|
# A :issue: role to link to github issues.
|
|
|
|
# Used like :issue:`2364`
|
|
|
|
def issue_role(name, rawtext, text, lineno, inliner, options=None, content=None):
|
|
|
|
options = options or {}
|
|
|
|
try:
|
|
|
|
issue_num = int(text.strip())
|
|
|
|
if issue_num <= 0:
|
|
|
|
raise ValueError
|
|
|
|
except ValueError:
|
2020-12-06 22:33:04 +08:00
|
|
|
msg = inliner.reporter.error('Invalid issue number: "%s"' % text, line=lineno)
|
2020-10-29 06:18:48 +08:00
|
|
|
prb = inliner.problematic(rawtext, rawtext, msg)
|
|
|
|
return [prb], [msg]
|
2020-12-06 22:33:04 +08:00
|
|
|
template = issue_url + "/{n}"
|
2020-10-29 06:18:48 +08:00
|
|
|
ref = template.format(n=issue_num)
|
|
|
|
issue_text = "#{issue_no}".format(issue_no=issue_num)
|
|
|
|
link = nodes.reference(text=issue_text, refuri=ref, **options)
|
|
|
|
return [link], []
|
|
|
|
|
2020-12-06 22:33:04 +08:00
|
|
|
|
2020-10-29 06:18:48 +08:00
|
|
|
# -- Load our extensions -------------------------------------------------
|
2019-03-15 04:52:25 +08:00
|
|
|
def setup(app):
|
docs synopsis: add HTML highlighing and automate manpage markup
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
2022-01-09 22:09:46 +08:00
|
|
|
# Our own pygments lexers
|
2019-03-15 04:52:25 +08:00
|
|
|
from sphinx.highlighting import lexers
|
2019-05-05 18:09:25 +08:00
|
|
|
|
2019-03-15 04:52:25 +08:00
|
|
|
this_dir = os.path.dirname(os.path.realpath(__file__))
|
2022-01-16 20:23:09 +08:00
|
|
|
sys.path.insert(0, this_dir)
|
|
|
|
from fish_indent_lexer import FishIndentLexer
|
docs synopsis: add HTML highlighing and automate manpage markup
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
2022-01-09 22:09:46 +08:00
|
|
|
from fish_synopsis import FishSynopsisDirective, FishSynopsisLexer
|
2022-01-16 20:23:09 +08:00
|
|
|
|
|
|
|
lexers["fish-docs-samples"] = FishIndentLexer()
|
docs synopsis: add HTML highlighing and automate manpage markup
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
2022-01-09 22:09:46 +08:00
|
|
|
lexers["fish-synopsis"] = FishSynopsisLexer()
|
|
|
|
app.add_directive("synopsis", FishSynopsisDirective)
|
2020-10-29 06:18:48 +08:00
|
|
|
|
|
|
|
app.add_config_value("issue_url", default=None, rebuild="html")
|
|
|
|
app.add_role("issue", issue_role)
|
|
|
|
|
2019-03-15 04:52:25 +08:00
|
|
|
|
2019-04-30 18:47:26 +08:00
|
|
|
# The default language to assume
|
2019-05-05 18:09:25 +08:00
|
|
|
highlight_language = "fish-docs-samples"
|
2019-03-15 04:52:25 +08:00
|
|
|
|
2018-12-16 08:23:36 +08:00
|
|
|
# -- Project information -----------------------------------------------------
|
|
|
|
|
2019-05-05 18:09:25 +08:00
|
|
|
project = "fish-shell"
|
2022-01-09 23:47:58 +08:00
|
|
|
copyright = "2022, fish-shell developers"
|
2019-05-05 18:09:25 +08:00
|
|
|
author = "fish-shell developers"
|
2020-10-29 06:18:48 +08:00
|
|
|
issue_url = "https://github.com/fish-shell/fish-shell/issues"
|
2018-12-16 08:23:36 +08:00
|
|
|
|
2019-09-19 14:51:40 +08:00
|
|
|
# Parsing FISH-BUILD-VERSION-FILE is possible but hard to ensure that it is in the right place
|
|
|
|
# fish_indent is guaranteed to be on PATH for the Pygments highlighter anyway
|
2019-09-22 03:04:21 +08:00
|
|
|
ret = subprocess.check_output(
|
|
|
|
("fish_indent", "--version"), stderr=subprocess.STDOUT
|
|
|
|
).decode("utf-8")
|
2018-12-16 08:23:36 +08:00
|
|
|
# The full version, including alpha/beta/rc tags
|
2019-09-22 02:58:42 +08:00
|
|
|
release = ret.strip().split(" ")[-1]
|
2019-09-19 14:51:40 +08:00
|
|
|
# The short X.Y version
|
2019-09-22 02:58:42 +08:00
|
|
|
version = release.rsplit(".", 1)[0]
|
2018-12-16 08:23:36 +08:00
|
|
|
|
|
|
|
|
|
|
|
# -- General configuration ---------------------------------------------------
|
|
|
|
|
|
|
|
# The suffix(es) of source filenames.
|
|
|
|
# You can specify multiple suffix as a list of string:
|
|
|
|
#
|
|
|
|
# source_suffix = ['.rst', '.md']
|
2019-05-05 18:09:25 +08:00
|
|
|
source_suffix = ".rst"
|
2018-12-16 08:23:36 +08:00
|
|
|
|
|
|
|
# The master toctree document.
|
2019-05-05 18:09:25 +08:00
|
|
|
master_doc = "index"
|
2018-12-16 08:23:36 +08:00
|
|
|
|
2022-01-15 01:54:01 +08:00
|
|
|
# The languages this uses, also used for content autogenerated by Sphinx.
|
2018-12-16 08:23:36 +08:00
|
|
|
#
|
|
|
|
# This is also used if you do content translation via gettext catalogs.
|
|
|
|
# Usually you set "language" from the command line for these cases.
|
2022-01-15 01:54:01 +08:00
|
|
|
#
|
|
|
|
# It also sets the html lang= attribute which would be useful to e.g. screenreaders.
|
|
|
|
# Currently we only have english.
|
|
|
|
language = "en"
|
2018-12-16 08:23:36 +08:00
|
|
|
|
|
|
|
# List of patterns, relative to source directory, that match files and
|
|
|
|
# directories to ignore when looking for source files.
|
|
|
|
# This pattern also affects html_static_path and html_extra_path.
|
2021-07-14 22:57:22 +08:00
|
|
|
exclude_patterns = []
|
2018-12-16 08:23:36 +08:00
|
|
|
|
|
|
|
# The name of the Pygments (syntax highlighting) style to use.
|
|
|
|
pygments_style = None
|
|
|
|
|
|
|
|
|
|
|
|
# -- Options for HTML output -------------------------------------------------
|
|
|
|
|
|
|
|
# The theme to use for HTML and HTML Help pages. See the documentation for
|
|
|
|
# a list of builtin themes.
|
2019-04-06 09:13:26 +08:00
|
|
|
# !!! If you change this you also need to update the @import at the top
|
2020-10-03 01:23:08 +08:00
|
|
|
# of _static/pygments.css
|
2020-10-03 04:44:42 +08:00
|
|
|
html_theme_path = ["."]
|
2020-10-03 01:23:08 +08:00
|
|
|
html_theme = "python_docs_theme"
|
2021-01-17 02:33:12 +08:00
|
|
|
|
2022-06-21 05:40:13 +08:00
|
|
|
# Shared styles across all doc versions.
|
|
|
|
html_css_files = ["/docs/shared/style.css"]
|
|
|
|
|
2021-01-17 02:33:12 +08:00
|
|
|
# Don't add a weird "_sources" directory
|
|
|
|
html_copy_source = False
|
2018-12-16 08:23:36 +08:00
|
|
|
|
|
|
|
# Custom sidebar templates, must be a dictionary that maps document names
|
|
|
|
# to template names.
|
|
|
|
#
|
|
|
|
# The default sidebars (for documents that don't match any pattern) are
|
|
|
|
# defined by theme itself. Builtin themes are using these templates by
|
|
|
|
# default: ``['localtoc.html', 'relations.html', 'sourcelink.html',
|
|
|
|
# 'searchbox.html']``.
|
|
|
|
#
|
2019-11-05 15:45:57 +08:00
|
|
|
html_sidebars = {"**": ["globaltoc.html", "searchbox.html", "localtoc.html"]}
|
2018-12-16 08:23:36 +08:00
|
|
|
|
|
|
|
|
|
|
|
# -- Options for LaTeX output ------------------------------------------------
|
|
|
|
|
2021-07-13 23:49:32 +08:00
|
|
|
# The default font is "GNU FreeSans" or something which I've never heard of.
|
|
|
|
# Make this something that might actually be installed.
|
2018-12-16 08:23:36 +08:00
|
|
|
latex_elements = {
|
2022-06-17 00:43:28 +08:00
|
|
|
"fontpkg": r"""
|
2021-07-13 23:49:32 +08:00
|
|
|
\setmainfont{Noto Serif}
|
|
|
|
\setsansfont{Noto Sans}
|
|
|
|
\setmonofont{Noto Sans Mono}
|
2022-06-17 00:43:28 +08:00
|
|
|
""",
|
2018-12-16 08:23:36 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
# Grouping the document tree into LaTeX files. List of tuples
|
|
|
|
# (source start file, target name, title,
|
|
|
|
# author, documentclass [howto, manual, or own class]).
|
|
|
|
latex_documents = [
|
2019-05-05 18:09:25 +08:00
|
|
|
(
|
2021-07-14 22:57:22 +08:00
|
|
|
master_doc,
|
2019-05-05 18:09:25 +08:00
|
|
|
"fish-shell.tex",
|
|
|
|
"fish-shell Documentation",
|
|
|
|
"fish-shell developers",
|
|
|
|
"manual",
|
2021-07-14 22:57:22 +08:00
|
|
|
),
|
2018-12-16 08:23:36 +08:00
|
|
|
]
|
|
|
|
|
2021-07-13 23:49:32 +08:00
|
|
|
# The default pdflatex doesn't handle unicode.
|
|
|
|
# Switch to an engine that does (why pdflatex still exists and is still the default? I don't know)
|
2022-06-17 00:43:28 +08:00
|
|
|
latex_engine = "xelatex"
|
2018-12-16 08:23:36 +08:00
|
|
|
|
|
|
|
# -- Options for manual page output ------------------------------------------
|
|
|
|
|
2019-05-05 18:09:25 +08:00
|
|
|
|
2019-03-31 17:05:09 +08:00
|
|
|
def get_command_description(path, name):
|
2022-06-17 00:43:28 +08:00
|
|
|
"""Return the description for a command, by parsing its synopsis line"""
|
2021-12-09 19:33:33 +08:00
|
|
|
with open(path) as opened:
|
|
|
|
for line in opened:
|
2022-06-17 00:43:28 +08:00
|
|
|
if line.startswith(name + " - "):
|
|
|
|
_, desc = line.split(" - ", 1)
|
2019-03-31 17:05:09 +08:00
|
|
|
return desc.strip()
|
2022-06-17 00:43:28 +08:00
|
|
|
elif line.startswith("``" + name + "`` - "):
|
|
|
|
_, desc = line.split("`` - ", 1)
|
|
|
|
return desc.strip("`")
|
2019-05-05 18:09:25 +08:00
|
|
|
raise SphinxWarning("No description in file %s" % os.path.basename(path))
|
2019-02-11 06:38:04 +08:00
|
|
|
|
2022-06-17 00:43:28 +08:00
|
|
|
|
2021-05-14 00:20:47 +08:00
|
|
|
# Newer sphinxen apparently create another subdirectory which breaks our man lookup.
|
|
|
|
# Unbreak it (#7996)
|
|
|
|
man_make_section_directory = False
|
2019-02-11 06:38:04 +08:00
|
|
|
|
2018-12-16 08:23:36 +08:00
|
|
|
# One entry per manual page. List of tuples
|
|
|
|
# (source start file, name, description, authors, manual section).
|
2019-06-23 22:13:47 +08:00
|
|
|
man_pages = [
|
2021-11-05 22:46:27 +08:00
|
|
|
(master_doc, "fish-doc", "", [author], 1),
|
|
|
|
("tutorial", "fish-tutorial", "", [author], 1),
|
|
|
|
("language", "fish-language", "", [author], 1),
|
|
|
|
("interactive", "fish-interactive", "", [author], 1),
|
|
|
|
("relnotes", "fish-releasenotes", "", [author], 1),
|
|
|
|
("completions", "fish-completions", "", [author], 1),
|
2020-11-22 21:39:48 +08:00
|
|
|
(
|
|
|
|
"fish_for_bash_users",
|
|
|
|
"fish-for-bash-users",
|
2021-11-05 22:46:27 +08:00
|
|
|
"",
|
2020-11-22 21:39:48 +08:00
|
|
|
[author],
|
|
|
|
1,
|
|
|
|
),
|
2021-11-05 22:46:27 +08:00
|
|
|
("faq", "fish-faq", "", [author], 1),
|
2019-06-23 22:13:47 +08:00
|
|
|
]
|
2019-05-05 18:09:25 +08:00
|
|
|
for path in sorted(glob.glob("cmds/*")):
|
2021-07-13 23:47:13 +08:00
|
|
|
docname = os.path.splitext(path)[0]
|
2018-12-16 08:23:36 +08:00
|
|
|
cmd = os.path.basename(docname)
|
2019-05-05 18:09:25 +08:00
|
|
|
man_pages.append((docname, cmd, get_command_description(path, cmd), "", 1))
|
2018-12-16 08:23:36 +08:00
|
|
|
|
|
|
|
|
|
|
|
# -- Options for Texinfo output ----------------------------------------------
|
|
|
|
|
|
|
|
# Grouping the document tree into Texinfo files. List of tuples
|
|
|
|
# (source start file, target name, title, author,
|
|
|
|
# dir menu entry, description, category)
|
|
|
|
texinfo_documents = [
|
2019-05-05 18:09:25 +08:00
|
|
|
(
|
|
|
|
master_doc,
|
|
|
|
"fish-shell",
|
|
|
|
"fish-shell Documentation",
|
|
|
|
author,
|
|
|
|
"fish-shell",
|
2021-11-05 04:26:54 +08:00
|
|
|
"the friendly interactive shell",
|
2019-05-05 18:09:25 +08:00
|
|
|
"Miscellaneous",
|
|
|
|
)
|
2018-12-16 08:23:36 +08:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
|
|
# -- Options for Epub output -------------------------------------------------
|
|
|
|
|
|
|
|
# Bibliographic Dublin Core info.
|
|
|
|
epub_title = project
|
|
|
|
|
|
|
|
# The unique identifier of the text. This can be a ISBN number
|
|
|
|
# or the project homepage.
|
|
|
|
#
|
|
|
|
# epub_identifier = ''
|
|
|
|
|
|
|
|
# A unique identification for the text.
|
|
|
|
#
|
|
|
|
# epub_uid = ''
|
|
|
|
|
|
|
|
# A list of files that should not be packed into the epub file.
|
2019-05-05 18:09:25 +08:00
|
|
|
epub_exclude_files = ["search.html"]
|
2018-12-16 08:23:36 +08:00
|
|
|
|
2021-10-27 01:44:40 +08:00
|
|
|
# Enable smart-quotes
|
|
|
|
# default action is 'qDe': quotes, Dashes, ellipsis. Skip dashes for --options
|
|
|
|
smartquotes = True
|
2022-06-17 00:43:28 +08:00
|
|
|
smartquotes_action = "qe"
|
2021-07-13 23:52:32 +08:00
|
|
|
|
2022-06-17 00:43:28 +08:00
|
|
|
linkcheck_ignore = [r"https://github.com/fish-shell/fish-shell/issues/\d+"]
|