Files
fish-shell/doc_src/conf.py

316 lines
9.8 KiB
Python
Raw Normal View History

2018-12-15 16: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
from glob import glob
2018-12-15 16:23:36 -08:00
import os.path
import subprocess
import sys
help: get section titles from Sphinx functions/help and completions/help duplicate a lot of information from doc_src. Get this information from Sphinx. Drop short section titles such as "help globbing" in favor of the full HTML anchor: help language#wildcards-globbing I think the verbosity is no big deal because we have tab completion, we're trading in conciseness for consistency and better searchability. In future, we can add back shorter invocations like "help globbing" (especially given that completion descriptions often already repeated the anchor path), but it should be checked by CI. Also - Remove some unused Sphinx anchors - Remove an obsoleted script. - Test that completions are in sync with Sphinx sources. (note that an alternative would be to check in the generated help_sections.rs file, see https://internals.rust-lang.org/t/how-fail-on-cargo-warning-warnings-from-build-rs/23590/5) Here's a list of deleted msgids. Some of them were unused, for others there was a better message (+ translation). $variable $variable 变量 (command) command substitution (命令) 命令替换 < and > redirections < 和 > 重定向 Autoloading functions 自动加载函数 Background jobs 后台作业 Builtin commands 内建命令 Combining different expansions 合并不同的展开 Command substitution (SUBCOMMAND) 命令替换 (子命令) Defining aliases 定义别名 Escaping characters 转义字符 Help on how to reuse previously entered commands 关于如何重复使用先前输入的命令的帮助 How lists combine 列表如何组合 Job control 作业控制 Local, global and universal scope 局域、全局和通用作用域 Other features 其他功能 Programmable prompt 可编程提示符 Shell variable and function names Shell 变量和函数名 Some common words 一些常用词 The status variable 状况变量 Variable scope for functions 函数的变量作用域 Vi mode commands Vi 模式命令 What set -x does `set -x` 做什么 Writing your own completions 自己写补全 ifs and elses if 和 else var[x..y] slices var[x..y] 切片 {a,b} brace expansion {a,b} 大括号展开 ~ expansion ~ 展开 Closes #11796
2025-11-05 13:44:42 +01:00
from pathlib import Path
from sphinx.highlighting import lexers
from sphinx.errors import SphinxWarning
from docutils import nodes
2018-12-15 16:23:36 -08:00
try:
import sphinx_markdown_builder
extensions = [
"sphinx_markdown_builder",
]
except ImportError:
pass
2018-12-15 16:23:36 -08:00
# -- Helper functions --------------------------------------------------------
# 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:
msg = inliner.reporter.error('Invalid issue number: "%s"' % text, line=lineno)
prb = inliner.problematic(rawtext, rawtext, msg)
return [prb], [msg]
template = issue_url + "/{n}"
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], []
help: get section titles from Sphinx functions/help and completions/help duplicate a lot of information from doc_src. Get this information from Sphinx. Drop short section titles such as "help globbing" in favor of the full HTML anchor: help language#wildcards-globbing I think the verbosity is no big deal because we have tab completion, we're trading in conciseness for consistency and better searchability. In future, we can add back shorter invocations like "help globbing" (especially given that completion descriptions often already repeated the anchor path), but it should be checked by CI. Also - Remove some unused Sphinx anchors - Remove an obsoleted script. - Test that completions are in sync with Sphinx sources. (note that an alternative would be to check in the generated help_sections.rs file, see https://internals.rust-lang.org/t/how-fail-on-cargo-warning-warnings-from-build-rs/23590/5) Here's a list of deleted msgids. Some of them were unused, for others there was a better message (+ translation). $variable $variable 变量 (command) command substitution (命令) 命令替换 < and > redirections < 和 > 重定向 Autoloading functions 自动加载函数 Background jobs 后台作业 Builtin commands 内建命令 Combining different expansions 合并不同的展开 Command substitution (SUBCOMMAND) 命令替换 (子命令) Defining aliases 定义别名 Escaping characters 转义字符 Help on how to reuse previously entered commands 关于如何重复使用先前输入的命令的帮助 How lists combine 列表如何组合 Job control 作业控制 Local, global and universal scope 局域、全局和通用作用域 Other features 其他功能 Programmable prompt 可编程提示符 Shell variable and function names Shell 变量和函数名 Some common words 一些常用词 The status variable 状况变量 Variable scope for functions 函数的变量作用域 Vi mode commands Vi 模式命令 What set -x does `set -x` 做什么 Writing your own completions 自己写补全 ifs and elses if 和 else var[x..y] slices var[x..y] 切片 {a,b} brace expansion {a,b} 大括号展开 ~ expansion ~ 展开 Closes #11796
2025-11-05 13:44:42 +01:00
def extract_sections(app, env):
if app.builder.name != "man":
return
output_file = app.config.fish_help_sections_output
if output_file == "":
return
import re
sections = []
for docname, info in env.tocs.items():
for node in info.traverse():
if not isinstance(node, nodes.reference):
continue
anchor = node["anchorname"]
if re.match(r"^#id\d+$", anchor):
continue
if anchor and docname.startswith("cmds/"):
continue
if anchor and docname == "relnotes":
continue
sections.append(docname + anchor)
sections.sort()
for section in sections:
assert re.match(r"[\w-]", section), (
f"Unsupported characters in section path: {section}"
)
help_sections = "".join(f"{section}\n" for section in sections)
Path(output_file).write_text(help_sections)
help: get section titles from Sphinx functions/help and completions/help duplicate a lot of information from doc_src. Get this information from Sphinx. Drop short section titles such as "help globbing" in favor of the full HTML anchor: help language#wildcards-globbing I think the verbosity is no big deal because we have tab completion, we're trading in conciseness for consistency and better searchability. In future, we can add back shorter invocations like "help globbing" (especially given that completion descriptions often already repeated the anchor path), but it should be checked by CI. Also - Remove some unused Sphinx anchors - Remove an obsoleted script. - Test that completions are in sync with Sphinx sources. (note that an alternative would be to check in the generated help_sections.rs file, see https://internals.rust-lang.org/t/how-fail-on-cargo-warning-warnings-from-build-rs/23590/5) Here's a list of deleted msgids. Some of them were unused, for others there was a better message (+ translation). $variable $variable 变量 (command) command substitution (命令) 命令替换 < and > redirections < 和 > 重定向 Autoloading functions 自动加载函数 Background jobs 后台作业 Builtin commands 内建命令 Combining different expansions 合并不同的展开 Command substitution (SUBCOMMAND) 命令替换 (子命令) Defining aliases 定义别名 Escaping characters 转义字符 Help on how to reuse previously entered commands 关于如何重复使用先前输入的命令的帮助 How lists combine 列表如何组合 Job control 作业控制 Local, global and universal scope 局域、全局和通用作用域 Other features 其他功能 Programmable prompt 可编程提示符 Shell variable and function names Shell 变量和函数名 Some common words 一些常用词 The status variable 状况变量 Variable scope for functions 函数的变量作用域 Vi mode commands Vi 模式命令 What set -x does `set -x` 做什么 Writing your own completions 自己写补全 ifs and elses if 和 else var[x..y] slices var[x..y] 切片 {a,b} brace expansion {a,b} 大括号展开 ~ expansion ~ 展开 Closes #11796
2025-11-05 13:44:42 +01:00
def remove_fish_indent_lexer(app):
if app.builder.name in ("man", "markdown"):
del lexers["fish-docs-samples"]
# -- Load our extensions -------------------------------------------------
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 15:09:46 +01:00
# Our own pygments lexers
this_dir = os.path.dirname(os.path.realpath(__file__))
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 15:09:46 +01:00
from fish_synopsis import FishSynopsisDirective, FishSynopsisLexer
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 15:09:46 +01:00
lexers["fish-synopsis"] = FishSynopsisLexer()
app.add_directive("synopsis", FishSynopsisDirective)
app.add_config_value("issue_url", default=None, rebuild="html")
app.add_config_value(
"fish_help_sections_output",
default="",
rebuild="man",
types=str,
)
app.add_role("issue", issue_role)
app.connect("builder-inited", remove_fish_indent_lexer)
help: get section titles from Sphinx functions/help and completions/help duplicate a lot of information from doc_src. Get this information from Sphinx. Drop short section titles such as "help globbing" in favor of the full HTML anchor: help language#wildcards-globbing I think the verbosity is no big deal because we have tab completion, we're trading in conciseness for consistency and better searchability. In future, we can add back shorter invocations like "help globbing" (especially given that completion descriptions often already repeated the anchor path), but it should be checked by CI. Also - Remove some unused Sphinx anchors - Remove an obsoleted script. - Test that completions are in sync with Sphinx sources. (note that an alternative would be to check in the generated help_sections.rs file, see https://internals.rust-lang.org/t/how-fail-on-cargo-warning-warnings-from-build-rs/23590/5) Here's a list of deleted msgids. Some of them were unused, for others there was a better message (+ translation). $variable $variable 变量 (command) command substitution (命令) 命令替换 < and > redirections < 和 > 重定向 Autoloading functions 自动加载函数 Background jobs 后台作业 Builtin commands 内建命令 Combining different expansions 合并不同的展开 Command substitution (SUBCOMMAND) 命令替换 (子命令) Defining aliases 定义别名 Escaping characters 转义字符 Help on how to reuse previously entered commands 关于如何重复使用先前输入的命令的帮助 How lists combine 列表如何组合 Job control 作业控制 Local, global and universal scope 局域、全局和通用作用域 Other features 其他功能 Programmable prompt 可编程提示符 Shell variable and function names Shell 变量和函数名 Some common words 一些常用词 The status variable 状况变量 Variable scope for functions 函数的变量作用域 Vi mode commands Vi 模式命令 What set -x does `set -x` 做什么 Writing your own completions 自己写补全 ifs and elses if 和 else var[x..y] slices var[x..y] 切片 {a,b} brace expansion {a,b} 大括号展开 ~ expansion ~ 展开 Closes #11796
2025-11-05 13:44:42 +01:00
app.connect("env-updated", extract_sections)
# The default language to assume
highlight_language = "fish-docs-samples"
2018-12-15 16:23:36 -08:00
# -- Project information -----------------------------------------------------
project = "fish-shell"
copyright = "fish-shell developers"
author = "fish-shell developers"
issue_url = "https://github.com/fish-shell/fish-shell/issues"
2018-12-15 16:23:36 -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
if "FISH_BUILD_VERSION_FILE" in os.environ:
f = open(os.environ["FISH_BUILD_VERSION_FILE"], "r")
ret = f.readline().strip()
elif "FISH_BUILD_VERSION" in os.environ:
ret = os.environ["FISH_BUILD_VERSION"]
else:
ret = subprocess.check_output(
("../build_tools/git_version_gen.sh", "--stdout"), stderr=subprocess.STDOUT
).decode("utf-8")
predetermined_timestamp = os.environ.get("FISH_SPHINX_BUILD_DATE")
if predetermined_timestamp:
today = predetermined_timestamp
2018-12-15 16:23:36 -08:00
# The full version, including alpha/beta/rc tags
2019-09-21 11:58:42 -07:00
release = ret.strip().split(" ")[-1]
# The short X.Y version
2019-09-21 11:58:42 -07:00
version = release.rsplit(".", 1)[0]
2018-12-15 16: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']
source_suffix = ".rst"
2018-12-15 16:23:36 -08:00
# The master toctree document.
master_doc = "index"
2018-12-15 16:23:36 -08:00
# The languages this uses, also used for content autogenerated by Sphinx.
2018-12-15 16: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.
#
# It also sets the html lang= attribute which would be useful to e.g. screenreaders.
# Currently we only have english.
language = "en"
2018-12-15 16: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.
fish_exclude_patterns = "cmds/*.inc.rst"
exclude_patterns = [fish_exclude_patterns]
2018-12-15 16: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-05 18:13:26 -07:00
# !!! If you change this you also need to update the @import at the top
# of _static/pygments.css
html_theme_path = ["."]
html_theme = "python_docs_theme"
# Shared styles across all doc versions.
html_css_files = []
# Don't add a weird "_sources" directory
html_copy_source = False
2018-12-15 16: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']``.
#
html_sidebars = {"**": ["globaltoc.html", "searchbox.html", "localtoc.html"]}
2018-12-15 16:23:36 -08:00
# -- Options for LaTeX output ------------------------------------------------
# The default font is "GNU FreeSans" or something which I've never heard of.
# Make this something that might actually be installed.
2018-12-15 16:23:36 -08:00
latex_elements = {
"fontpkg": r"""
\setmainfont{Noto Serif}
\setsansfont{Noto Sans}
\setmonofont{Noto Sans Mono}
""",
2018-12-15 16: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 = [
(
master_doc,
"fish-shell.tex",
"fish-shell Documentation",
"fish-shell developers",
"manual",
),
2018-12-15 16:23:36 -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)
latex_engine = "xelatex"
2018-12-15 16:23:36 -08:00
# -- Options for manual page output ------------------------------------------
def get_command_description(path, name):
"""Return the description for a command, by parsing its synopsis line"""
with open(path) as opened:
for line in opened:
if line.startswith(name + " - "):
_, desc = line.split(" - ", 1)
return desc.strip()
elif line.startswith("``" + name + "`` - "):
_, desc = line.split("`` - ", 1)
return desc.strip("`")
raise SphinxWarning("No description in file %s" % os.path.basename(path))
# Newer sphinxen apparently create another subdirectory which breaks our man lookup.
# Unbreak it (#7996)
man_make_section_directory = False
man_show_urls = True
2018-12-15 16:23:36 -08:00
# One entry per manual page. List of tuples
# (source start file, name, description, authors, manual section).
man_pages = [
(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),
Stop reading terminfo database Our use of the terminfo database in /usr/share/terminfo/$TERM is both 1. a way for users to configure app behavior in their terminal (by setting TERM, copying around and modifying terminfo files) 2. a way for terminal emulator developers to advertise support for backwards-incompatible features that are not otherwise easily observable. To 1: this is not ideal (it's very easy to break things). There's not many things that realistically need configuration; let's use shell variables instead. To 2: in practice, feature-probing via terminfo is often wrong. There's not many backwards-incompatible features that need this; for the ones that do we can still use terminfo capabilities but query the terminal via XTGETTCAP directly, skipping the file (which may not exist on the same system as the terminal). --- Get rid of terminfo. If anyone finds a $TERM where we need different behavior, we can hardcode that into fish. * Allow to override this with `fish_features=no-ignore-terminfo fish` Not sure if we should document this, since it's supposed to be removed soon, and if someone needs this (which we don't expect), we'd like to know. * This is supported on a best-effort basis; it doesn't match the previous behavior exactly. For simplicity of implementation, it will not change the fact that we now: * use parm_left_cursor (CSI Ps D) instead of cursor_left (CSI D) if terminfo claims the former is supported * no longer support eat_newline_glitch, which seems no longer present on today's ConEmu and ConHost * Tested as described in https://github.com/fish-shell/fish-shell/pull/11345#discussion_r2030121580 * add `man fish-terminal-compatibility` to state our assumptions. This could help terminal emulator developers. * assume `parm_up_cursor` is supported if the terminal supports XTGETTCAP * Extract all control sequences to src/terminal_command.rs. * Remove the "\x1b(B" prefix from EXIT_ATTRIBUTE_MODE. I doubt it's really needed. * assume it's generally okay to output 256 colors Things have improved since commit 3669805627 (Improve compatibility with 0-16 color terminals., 2016-07-21). Apparently almost every actively developed terminal supports it, including Terminal.app and GNU screen. * That is, we default `fish_term256` to true and keep it only as a way to opt out of the the full 256 palette (e.g. switching to the 16-color palette). * `TERM=xterm-16color` has the same opt-out effect. * `TERM` is generally ignored but add back basic compatiblity by turning off color for "ansi-m", "linux-m" and "xterm-mono"; these are probably not set accidentally. * Since `TERM` is (mostly) ignored, we don't need the magic "xterm" in tests. Unset it instead. * Note that our pexpect tests used a dumb terminal because: 1. it makes fish do a full redraw of the commandline everytime, making it easier to write assertions. 2. it disables all control sequences for colors, etc, which we usually don't want to test explicitly. I don't think TERM=dumb has any other use, so it would be better to print escape sequences unconditionally, and strip them in the test driver (leaving this for later, since it's a bit more involved). Closes #11344 Closes #11345
2025-03-20 22:02:38 +01:00
("terminal-compatibility", "fish-terminal-compatibility", "", [author], 1),
("completions", "fish-completions", "", [author], 1),
("prompt", "fish-prompt-tutorial", "", [author], 1),
2020-11-22 14:39:48 +01:00
(
"fish_for_bash_users",
"fish-for-bash-users",
"",
2020-11-22 14:39:48 +01:00
[author],
1,
),
("faq", "fish-faq", "", [author], 1),
]
for path in sorted(set(glob("cmds/*.rst")) - set(glob(fish_exclude_patterns))):
2021-07-13 17:47:13 +02:00
docname = os.path.splitext(path)[0]
2018-12-15 16:23:36 -08:00
cmd = os.path.basename(docname)
man_pages.append((docname, cmd, get_command_description(path, cmd), "", 1))
2018-12-15 16: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 = [
(
master_doc,
"fish-shell",
"fish-shell Documentation",
author,
"fish-shell",
"the friendly interactive shell",
"Miscellaneous",
)
2018-12-15 16: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.
epub_exclude_files = ["search.html"]
2018-12-15 16:23:36 -08:00
# Enable smart-quotes
# default action is 'qDe': quotes, Dashes, ellipsis. Skip dashes for --options
smartquotes = True
smartquotes_action = "qe"
linkcheck_ignore = [r"https://github.com/fish-shell/fish-shell/issues/\d+"]