2019-03-31 09:05:09 +00:00
.. _cmd-bg:
2018-12-17 01:39:33 +00:00
bg - send jobs to background
2019-01-03 04:10:47 +00:00
============================
2018-12-17 01:39:33 +00:00
2018-12-18 01:58:24 +00:00
Synopsis
--------
2018-12-16 21:08:41 +00:00
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 14:09:46 +00:00
.. synopsis ::
bg [PID ...]
2018-12-16 21:08:41 +00:00
2018-12-19 02:44:30 +00:00
Description
2019-01-03 04:10:47 +00:00
-----------
2018-12-16 21:08:41 +00:00
2020-01-31 03:38:56 +00:00
`` bg `` sends :ref: `jobs <syntax-job-control>` to the background, resuming them if they are stopped.
2018-12-16 21:08:41 +00:00
2021-02-28 12:56:23 +00:00
A background job is executed simultaneously with fish, and does not have access to the keyboard. If no job is specified, the last job to be used is put in the background. If `` PID `` is specified, the jobs containing the specified process IDs are put in the background.
2018-12-16 21:08:41 +00:00
2021-02-28 12:56:23 +00:00
For compatibility with other shells, job expansion syntax is supported for `` bg `` . A PID of the format `` %1 `` will be interpreted as the PID of job 1. Job numbers can be seen in the output of :ref: `jobs <cmd-jobs>` .
When at least one of the arguments isn't a valid job specifier,
2018-12-19 20:02:45 +00:00
`` bg `` will print an error without backgrounding anything.
2018-12-16 21:08:41 +00:00
2021-02-28 12:56:23 +00:00
When all arguments are valid job specifiers, `` bg `` will background all matching jobs that exist.
2018-12-16 21:08:41 +00:00
2018-12-19 02:44:30 +00:00
Example
2019-01-03 04:10:47 +00:00
-------
2018-12-16 21:08:41 +00:00
2021-02-28 12:56:23 +00:00
`` bg 123 456 789 `` will background the jobs that contain processes 123, 456 and 789.
2018-12-16 21:08:41 +00:00
If only 123 and 789 exist, it will still background them and print an error about 456.
2018-12-19 20:02:45 +00:00
`` bg 123 banana `` or `` bg banana 123 `` will complain that "banana" is not a valid job specifier.
2021-02-28 12:56:23 +00:00
`` bg %1 `` will background job 1.
