Yocto Project Documentation
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Quentin Schulz" <quentin.schulz@cherry.de>,
	<docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 3/3] brief-yoctoprojectqs/index.rst: switch shell block to to console lexer
Date: Fri, 28 Nov 2025 14:46:18 +0100	[thread overview]
Message-ID: <DEKDH2B5L1HA.1TTPB0U4MFRJA@bootlin.com> (raw)
In-Reply-To: <83cdb96c-fbf6-4a5c-a2a7-97f748a3ba1b@cherry.de>

Hi,

On Fri Nov 28, 2025 at 2:30 PM CET, Quentin Schulz wrote:
> Hi Antonin,
>
> On 11/28/25 2:11 PM, Antonin Godard wrote:
>> Hi,
>> 
>> On Thu Nov 27, 2025 at 5:47 PM CET, Quentin Schulz via lists.yoctoproject.org wrote:
>> [...]
>>>>    #. Choose a configuration (for example, ``poky-master``):
>>>>    
>>>> -   .. code-block:: shell
>>>> +   .. code-block:: console
>>>>    
>>>
>>> Neither shell nor console. I would suggest to simply use a literal block
>>> (::), c.f.
>>> https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#rst-literal-blocks
>> 
>> Thanks, I'll change that.
>> 
>> I just noticed but I think the default lexer for literal blocks is Python unless
>> you explicitly set it to something else in the global configuration[1]. I think
>
> Ah, and I had missed that. I changed it to shell for my company's user 
> manuals but I didn't know it was Python by default (well some sort of 
> Python).
>
>> it makes sense to change it to "text" as the rendering looks odd in most places
>> where it thinks it's Python code, whereas most of the time it's either text
>> snippets or bitbake assignments.
>> 
> I would recommend picking a sensible default. Since there doesn't exist 
> a BitBake lexer (and I don't see a MR for that in pygments) yet, I guess 
> going for "text" or "none" will do. Good catch!
>
> This though will get rid of highlights where it is (to me) somewhat 
> useful, see most blocks in 
> https://docs.yoctoproject.org/ref-manual/variables.html. Maybe it isn't 
> *that* worth it. Up to you.

Yes, re-reading some of the docs I also noticed it would get rid of some useful
highlighting, so I think for text blocks we should use .. code-block:: text when
we think about it. I'll use that for the quick start guide.

Thanks!
Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2025-11-28 13:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27 16:37 [PATCH 0/3] bitbake-setup updates Antonin Godard
2025-11-27 16:37 ` [PATCH 1/3] poky.yaml.in: add DISTRO_RELEASE_SERIES Antonin Godard
2025-11-27 16:37 ` [PATCH 2/3] brief-yoctoprojectqs/index.rst: update available bitbake-setup configurations Antonin Godard
2025-11-27 16:37 ` [PATCH 3/3] brief-yoctoprojectqs/index.rst: switch shell block to to console lexer Antonin Godard
2025-11-27 16:47   ` [docs] " Quentin Schulz
2025-11-28 13:11     ` Antonin Godard
2025-11-28 13:14       ` Antonin Godard
2025-11-28 13:30       ` Quentin Schulz
2025-11-28 13:46         ` Antonin Godard [this message]
2025-12-01  8:35 ` [PATCH 0/3] bitbake-setup updates 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=DEKDH2B5L1HA.1TTPB0U4MFRJA@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@cherry.de \
    --cc=thomas.petazzoni@bootlin.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