All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: antonin.godard@bootlin.com, Trevor Woerner <twoerner@gmail.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH 00/10] docs: highlight BitBake snippets with the bitbake language
Date: Thu, 27 Aug 2026 16:23:08 +0200	[thread overview]
Message-ID: <3e21159f-939c-4e66-9c8d-e6208b1bb2ed@cherry.de> (raw)
In-Reply-To: <DKZPWL5N9LAS.EB6LNEC08FQE@bootlin.com>

Hi Antonin,

On 8/27/26 2:16 PM, Antonin Godard via lists.yoctoproject.org wrote:
> Hi,
> 
> On Thu Aug 27, 2026 at 1:34 PM CEST, Trevor Woerner wrote:
>> On Thu 2026-08-27 @ 10:38:58 AM, Antonin Godard wrote:
>>> Hi,
>>>
>>> On Wed Aug 26, 2026 at 3:34 AM CEST, Trevor Woerner via lists.yoctoproject.org wrote:
>>> [...]
>>>> Not included
>>>> ------------
>>>>
>>>> Six blocks in ref-manual/ trip a defect in the released BitBake lexer,
>>>> fixed upstream but not yet in a release. They are a separate patch, held
>>>> until that release, so the rest is not blocked behind them.
>>>
>>> Would it make sense to apply a patch to Pygments in OE-Core to fix these issues
>>> until a new version of Pygments is released?
>>
>> It would be very easy for me to provide a patch that would fix these
>> things locally until (if) upstream pygments picks up my updates:
>>
>> https://github.com/pygments/pygments/pull/3284
>>
>> I had wanted to add such a patch when I first developed the bitbake
>> lexer for pygments but the last time I proposed adding a temporary,
>> local pygments update it was decided we should wait for upstream.
>> Therefore I stopped short of doing that here.
> 
> I think you misunderstood me :) What I meant is that we could patch
> python3-pygments in *OE-Core* (*not* provide the lexer from yocto-docs)
> temporarily, until your above pull request is merged, and we drop the
> patches in OE-Core after an update.
> 

Please don't, otherwise people will be forced to use the buildtools to 
build the docs.

Cheers,
Quentin


      reply	other threads:[~2026-08-27 14:23 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 ` [docs] " Quentin Schulz
2026-08-26 13:09   ` 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 [this message]

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=3e21159f-939c-4e66-9c8d-e6208b1bb2ed@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.