From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <twoerner@gmail.com>, <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH 03/10] docs: show a prompt on commands the reader is meant to type
Date: Tue, 22 Sep 2026 14:19:59 +0200 [thread overview]
Message-ID: <DLLU9BGBPRP7.2N2XWEQWTHZ7I@bootlin.com> (raw)
In-Reply-To: <20260922020339.481929-4-twoerner@gmail.com>
Hi,
On Tue Sep 22, 2026 at 4:03 AM CEST, Trevor Woerner via lists.yoctoproject.org wrote:
> Most command blocks in the manuals start their lines with "$", but a
> scattering of them do not, and those read as a file listing rather than
> as something to run. Give them the prompt the surrounding pages already
> use.
>
> Transcripts take a prompt on their opening line alone. Two things that
> matter only once a line is a command go with that: a bare "$" at the end,
> the prompt returning after the command finished, and a trailing "\" on a
> Windows path, which a shell reads as a continuation into the output.
>
> AI-Generated: codex/claude-opus 5 (xhigh)
> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> ---
> documentation/brief-yoctoprojectqs/index.rst | 2 +-
> .../contributor-guide/recipe-style-guide.rst | 2 +-
> .../contributor-guide/submit-changes.rst | 60 +++++++++----------
> .../dev-manual/creating-fragments.rst | 4 +-
> documentation/dev-manual/debugging.rst | 1 -
> documentation/dev-manual/devtool.rst | 8 +--
> documentation/dev-manual/disk-space.rst | 4 +-
> documentation/dev-manual/hashequivserver.rst | 2 +-
> .../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 | 8 +--
> documentation/dev-manual/start.rst | 2 +-
> documentation/dev-manual/wayland.rst | 6 +-
> documentation/kernel-dev/common.rst | 3 -
> .../migration-guides/migration-2.1.rst | 4 +-
> .../migration-guides/migration-2.5.rst | 4 +-
> .../migration-guides/migration-4.0.rst | 2 +-
> .../migration-guides/migration-5.3.rst | 10 ++--
> .../migration-guides/release-notes-4.2.rst | 2 +-
> .../migration-guides/release-notes-5.3.rst | 2 +-
> documentation/ref-manual/classes.rst | 8 +--
> .../ref-manual/devtool-reference.rst | 2 -
> documentation/ref-manual/fragments.rst | 16 ++---
> documentation/ref-manual/qa-checks.rst | 4 +-
> documentation/ref-manual/variables.rst | 6 +-
> .../test-manual/reproducible-builds.rst | 2 +-
> documentation/test-manual/runtime-testing.rst | 4 +-
> 29 files changed, 86 insertions(+), 93 deletions(-)
>
> diff --git a/documentation/brief-yoctoprojectqs/index.rst b/documentation/brief-yoctoprojectqs/index.rst
> index f7e4606f1f7b..e138df6c9351 100644
> --- a/documentation/brief-yoctoprojectqs/index.rst
> +++ b/documentation/brief-yoctoprojectqs/index.rst
> @@ -373,7 +373,7 @@ layer>`:
>
> First, clone the layer next to the other layers::
>
> - git clone -b &DISTRO_NAME_NO_CAP; https://git.yoctoproject.org/meta-raspberrypi ../layers/meta-raspberrypi
> + $ git clone -b &DISTRO_NAME_NO_CAP; https://git.yoctoproject.org/meta-raspberrypi ../layers/meta-raspberrypi
>
> #. **Add Your Layer to the Layer Configuration File:** Before you can use
> it, you must add the layer and its dependencies to your :ref:`structure-build-conf-bblayers.conf`
> diff --git a/documentation/contributor-guide/recipe-style-guide.rst b/documentation/contributor-guide/recipe-style-guide.rst
> index 84c6bb14e8b0..fe12a8e6d826 100644
> --- a/documentation/contributor-guide/recipe-style-guide.rst
> +++ b/documentation/contributor-guide/recipe-style-guide.rst
> @@ -436,7 +436,7 @@ By default, patches created with ``git format-patch`` have a `Git` version signa
> To avoid having a `Git` signature at the end of generated or updated patches,
> you can use `Git` configuration settings::
>
> - git config --global format.signature ""
> + $ git config --global format.signature ""
I would take the opportunity to use the "console" lexer here, instead of using
the default one:
.. code-block:: console
$ git config --global format.signature ""
Applies to patch 01/10 too, this one, and maybe the other patches.
Antonin
next prev parent reply other threads:[~2026-09-22 12:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 2:03 [PATCH 00/10] docs: editorial repairs to the examples Trevor Woerner
2026-09-22 2:03 ` [PATCH 01/10] docs: give the root prompts a preamble Trevor Woerner
2026-09-22 2:03 ` [PATCH 02/10] docs: copy only the command from a console block Trevor Woerner
2026-09-22 12:20 ` [docs] " Antonin Godard
2026-09-22 14:40 ` Trevor Woerner
2026-09-22 15:16 ` Antonin Godard
2026-09-22 2:03 ` [PATCH 03/10] docs: show a prompt on commands the reader is meant to type Trevor Woerner
2026-09-22 12:19 ` Antonin Godard [this message]
2026-09-22 14:23 ` [docs] " Trevor Woerner
2026-09-22 2:03 ` [PATCH 04/10] docs: write an elided passage as a comment Trevor Woerner
2026-09-22 2:03 ` [PATCH 05/10] docs: mark the placeholders in examples Trevor Woerner
2026-09-22 2:03 ` [PATCH 06/10] docs: remove real accounts from the examples Trevor Woerner
2026-09-22 2:03 ` [PATCH 07/10] kernel-dev: give each example block one thing to hold Trevor Woerner
2026-09-22 12:19 ` [docs] " Antonin Godard
2026-09-22 2:03 ` [PATCH 08/10] ref-manual: put the ARCHIVER_MODE comments on their own lines Trevor Woerner
2026-09-22 2:03 ` [PATCH 09/10] ref-manual: drop "partition" as a wic kickstart command Trevor Woerner
2026-09-22 12:19 ` [docs] " Antonin Godard
2026-09-22 2:03 ` [PATCH 10/10] dev-manual: indent a list continuation so the code block ends Trevor Woerner
2026-09-22 12:19 ` [docs] " Antonin Godard
2026-09-22 12:19 ` [docs] [PATCH 00/10] docs: editorial repairs to the examples Antonin Godard
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=DLLU9BGBPRP7.2N2XWEQWTHZ7I@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=twoerner@gmail.com \
/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