From: Trevor Woerner <twoerner@gmail.com>
To: docs@lists.yoctoproject.org
Subject: [PATCH v2 0/8] docs: editorial repairs to the examples
Date: Tue, 22 Sep 2026 14:32:41 -0400 [thread overview]
Message-ID: <20260922183249.2433345-1-twoerner@gmail.com> (raw)
These are repairs to the examples themselves. No block is given a
language and no block changes how it is highlighted; what changes is the
text of the examples. Each commit stands on its own: a reader is better
served by every one of them whether or not anything else in this area
lands.
They also clear the way for a later series that states the language of
each code block. A block cannot say it is a console session without a
prompt, or C with a bare "..." in place of the code it omits, or anything
at all while it holds more than one file under a single "::". These
remove exactly those obstacles.
1. a preamble on the root prompts written as a bare "#", which the
rest already carry
2. the copy button reduced to the command, for every prompt shape
rather than just "$ "
3. a prompt on the command blocks the prose says to run, and on
transcripts only the opening line, plus dropping the bare trailing
"$" a returning prompt leaves behind
4. elided code written as a comment in the language around it
5. placeholders the reader must replace put in angle brackets
6. real accounts and home directories replaced with /home/user and a
bare "$"
7. kernel metadata examples split so each block holds one file, with
the filename moved to the block's caption
8. the ARCHIVER_MODE varflag examples given comments BitBake can parse,
since a "#" after a value is not an inline comment
The first three are related, and the third has been under discussion.
The great majority of command blocks already carry a prompt, so patch 3
finishes a convention rather than proposing one, and patches 1 and 2
remove the cost that convention imposes on a reader.
Patch 2 is the substance: copybutton_prompt_text was the literal "$ ",
so on a block prompted any other way nothing matched, and sphinx-
copybutton then falls back to copying every line, prompt and output
alike. That took in the root prompts, the Windows sessions in
dev-manual/start.rst and the pydevshell session, so the pattern now names
each prompt shape the manuals use. A mouse selection is left alone, so it
still takes the output; that is deliberate, and was your call on the v1
thread.
Patch 1 comes first because patch 2 treats "#" as a prompt only when a
preamble precedes it. That is not a shortcut: a bare "#" opens a root
prompt, a comment and a line of program output alike, and the manuals
use it for output and for comments far more often than for a prompt.
Giving the stragglers the preamble the rest already use makes the rule
true rather than approximate.
Every commit builds with zero warnings under -W, which is the Makefile
default, and each was built on its own rather than only at the tip.
sphinx-lint over the touched files is unchanged from master-next.
changes in v2:
- rebased on master-next, which is where it now applies; the one
conflict was the ARCHIVER_MODE block, where d5216e3fd4be had already
removed the srpm varflag
- dropped the two already applied, "partition" and the list
continuation, so this is eight patches rather than ten
- patch 2 no longer touches the stylesheet: a mouse selection keeps the
output, and only the copy button is changed
- patch 7 takes the theme's whole font stack for the caption
- patch 1 uses a generic root@machine prompt where the surrounding text
names no board
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Trevor Woerner (8):
docs: give the root prompts a preamble
docs: copy only the command from a console block
docs: show a prompt on commands the reader is meant to type
docs: write an elided passage as a comment
docs: mark the placeholders in examples
docs: remove real accounts from the examples
kernel-dev: give each example block one thing to hold
ref-manual: put the ARCHIVER_MODE comments on their own lines
documentation/brief-yoctoprojectqs/index.rst | 2 +-
documentation/bsp-manual/bsp.rst | 4 +-
documentation/conf.py | 28 +++-
.../contributor-guide/recipe-style-guide.rst | 2 +-
.../contributor-guide/submit-changes.rst | 62 ++++----
.../dev-manual/creating-fragments.rst | 4 +-
documentation/dev-manual/debugging.rst | 13 +-
documentation/dev-manual/devtool.rst | 8 +-
documentation/dev-manual/disk-space.rst | 4 +-
documentation/dev-manual/hashequivserver.rst | 2 +-
documentation/dev-manual/layers.rst | 12 +-
.../dev-manual/limiting-resources.rst | 2 +-
documentation/dev-manual/new-recipe.rst | 6 +-
documentation/dev-manual/packages.rst | 2 +-
.../dev-manual/python-development-shell.rst | 1 -
documentation/dev-manual/qemu.rst | 10 +-
documentation/dev-manual/start.rst | 2 +-
.../dev-manual/upgrading-recipes.rst | 18 +--
documentation/dev-manual/wayland.rst | 6 +-
documentation/dev-manual/wic.rst | 44 +++---
documentation/kernel-dev/advanced.rst | 139 ++++++++++--------
documentation/kernel-dev/common.rst | 37 +++--
.../migration-guides/migration-2.1.rst | 4 +-
.../migration-guides/migration-2.5.rst | 4 +-
.../migration-guides/migration-3.2.rst | 2 +-
.../migration-guides/migration-4.0.rst | 2 +-
.../migration-guides/migration-5.2.rst | 16 +-
.../migration-guides/migration-5.3.rst | 10 +-
.../migration-guides/release-notes-4.2.rst | 2 +-
.../migration-guides/release-notes-5.3.rst | 2 +-
documentation/overview-manual/concepts.rst | 2 +-
documentation/profile-manual/usage.rst | 4 +-
documentation/ref-manual/classes.rst | 8 +-
.../ref-manual/devtool-reference.rst | 10 +-
documentation/ref-manual/faq.rst | 6 +-
documentation/ref-manual/fragments.rst | 16 +-
documentation/ref-manual/qa-checks.rst | 4 +-
documentation/ref-manual/variables.rst | 35 +++--
documentation/sdk-manual/extensible.rst | 6 +-
.../sphinx-static/theme_overrides.css | 28 ++++
.../test-manual/reproducible-builds.rst | 2 +-
documentation/test-manual/runtime-testing.rst | 4 +-
42 files changed, 320 insertions(+), 255 deletions(-)
--
2.50.0.173.g8b6f19ccfc3a
next reply other threads:[~2026-09-22 18:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 18:32 Trevor Woerner [this message]
2026-09-22 18:32 ` [PATCH v2 1/8] docs: give the root prompts a preamble Trevor Woerner
2026-09-23 10:17 ` [docs] " Quentin Schulz
2026-09-24 16:00 ` Trevor Woerner
2026-09-22 18:32 ` [PATCH v2 2/8] docs: copy only the command from a console block Trevor Woerner
2026-09-23 10:41 ` [docs] " Quentin Schulz
2026-09-23 10:43 ` Quentin Schulz
2026-09-22 18:32 ` [PATCH v2 3/8] docs: show a prompt on commands the reader is meant to type Trevor Woerner
2026-09-23 10:49 ` [docs] " Quentin Schulz
2026-09-24 15:59 ` Trevor Woerner
2026-09-22 18:32 ` [PATCH v2 4/8] docs: write an elided passage as a comment Trevor Woerner
2026-09-23 10:50 ` [docs] " Quentin Schulz
2026-09-22 18:32 ` [PATCH v2 5/8] docs: mark the placeholders in examples Trevor Woerner
2026-09-23 10:57 ` [docs] " Quentin Schulz
2026-09-24 15:58 ` Trevor Woerner
2026-09-22 18:32 ` [PATCH v2 6/8] docs: remove real accounts from the examples Trevor Woerner
2026-09-23 11:02 ` [docs] " Quentin Schulz
2026-09-24 15:55 ` Trevor Woerner
2026-09-22 18:32 ` [PATCH v2 7/8] kernel-dev: give each example block one thing to hold Trevor Woerner
2026-09-23 11:05 ` [docs] " Quentin Schulz
2026-09-22 18:32 ` [PATCH v2 8/8] ref-manual: put the ARCHIVER_MODE comments on their own lines Trevor Woerner
2026-09-23 11:09 ` [docs] " Quentin Schulz
2026-09-24 15:55 ` Trevor Woerner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260922183249.2433345-1-twoerner@gmail.com \
--to=twoerner@gmail.com \
--cc=docs@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox