From: Quentin Schulz <quentin.schulz@cherry.de>
To: twoerner@gmail.com, docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH 00/10] docs: highlight BitBake snippets with the bitbake language
Date: Wed, 26 Aug 2026 14:10:31 +0200 [thread overview]
Message-ID: <34c79745-33ff-41dd-bb85-144bb26b02a2@cherry.de> (raw)
In-Reply-To: <20260826013502.2674000-1-twoerner@gmail.com>
Hi Trevor,
On 8/26/26 3:34 AM, Trevor Woerner via lists.yoctoproject.org wrote:
> Pygments 2.21.0 added a BitBake lexer, so BitBake snippets can now say
> what they are instead of rendering as plain literal blocks. This tags
> the ones in yocto-docs.
>
> One patch per manual, which is also roughly one reviewable unit per
> patch. No prose changes, no reflowing, no reindenting - every hunk turns
> a literal-block introducer into a code-block directive and nothing else.
>
> Which blocks were converted was decided by reading, not by pattern
"by reading" following a paragraph definitely not written by you and
with all commits being AI-Generated is quite the stretch ;)
[...]
> Depends on
> ----------
>
> "docs: state the language of nine literal blocks explicitly", sent
Link to the ML please to make maintainers and reviewers job easier.
[...]
I think this is going the wrong direction. We should actually make
explicit the language of every :: that is NOT to be understood as
BitBake code and then make the default highlight language be BitBake.
The direct benefit is the ability to still backport whatever needs to be
backported without having to care about the highlight language being
explicitly bitbake (which won't be available in every branch but
master). The other benefit is that by default every new code snippet
will be understood as BitBake syntax, which is very likely what most of
the snippet should be, and if they aren't, then their language should be
made explicit. I'm thinking this could also maybe reduce the diff as I'm
hoping we have more BitBake syntax than shell/python/whatever else so
maybe easier to review as well. I believe
https://www.sphinx-doc.org/en/master/usage/configuration.html#confval-highlight_language
should be the way to do change the default highlight language (according
to
https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#literal-blocks
and
https://www.sphinx-doc.org/en/master/usage/restructuredtext/directives.html#directive-code-block)?
Cheers,
Quentin
next prev parent reply other threads:[~2026-08-26 12:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 1:34 [PATCH 00/10] docs: highlight BitBake snippets with the bitbake language Trevor Woerner
2026-08-26 1:34 ` [PATCH 01/10] ref-manual/variables.rst: use the bitbake code-block language Trevor Woerner
2026-08-26 1:34 ` [PATCH 02/10] ref-manual: " Trevor Woerner
2026-08-26 1:34 ` [PATCH 03/10] dev-manual: " Trevor Woerner
2026-08-26 1:34 ` [PATCH 04/10] migration-guides: " Trevor Woerner
2026-08-26 1:34 ` [PATCH 05/10] kernel-dev: " Trevor Woerner
2026-08-26 1:34 ` [PATCH 06/10] test-manual: " Trevor Woerner
2026-08-26 1:34 ` [PATCH 07/10] overview-manual: " Trevor Woerner
2026-08-26 1:34 ` [PATCH 08/10] security-manual: " Trevor Woerner
2026-08-26 1:34 ` [PATCH 09/10] sdk-manual: " Trevor Woerner
2026-08-26 1:34 ` [PATCH 10/10] docs-wide: " Trevor Woerner
2026-08-26 11:56 ` [PATCH 00/10] docs: highlight BitBake snippets with the bitbake language Paul Barker
2026-08-26 13:29 ` Trevor Woerner
2026-08-26 12:10 ` Quentin Schulz [this message]
2026-08-26 13:09 ` [docs] " Antonin Godard
2026-08-26 13:25 ` Trevor Woerner
2026-08-26 14:45 ` Quentin Schulz
2026-08-26 19:56 ` Trevor Woerner
2026-08-27 14:33 ` Quentin Schulz
2026-08-31 9:01 ` Antonin Godard
2026-08-31 13:18 ` Trevor Woerner
2026-08-31 14:16 ` Trevor Woerner
2026-08-31 15:19 ` Antonin Godard
2026-08-31 15:55 ` Trevor Woerner
2026-09-01 7:31 ` Antonin Godard
2026-08-26 14:34 ` Quentin Schulz
2026-08-26 15:10 ` Antonin Godard
2026-08-26 15:43 ` Quentin Schulz
2026-08-27 8:02 ` Antonin Godard
2026-08-27 8:38 ` Antonin Godard
2026-08-27 11:34 ` Trevor Woerner
2026-08-27 12:16 ` Antonin Godard
2026-08-27 14:23 ` Quentin Schulz
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=34c79745-33ff-41dd-bb85-144bb26b02a2@cherry.de \
--to=quentin.schulz@cherry.de \
--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