All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
	"YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] is there any way to render content in italics in a code block?
Date: Fri, 09 Jan 2026 10:39:12 +0100	[thread overview]
Message-ID: <DFJYIQV433MB.1DVI67253GCB@bootlin.com> (raw)
In-Reply-To: <5eef4c2b-95ae-cc22-b44c-a03e29982c79@crashcourse.ca>

On Thu Jan 8, 2026 at 10:33 PM CET, Robert P. J. Day wrote:
>
>   one aspect of sphinx that gripes my wagger is that there does not
> seem to be any easy way to tag something in italics in a code block.
>
> here:
>
> https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-execution.html
>
> the code line:
>
>  $ bitbake target
>
> really needs the word "target" in italics to show that it's meant to
> be replaced. and, no, this isn't minor nitpicking -- the whole section
> on overrides desperately needs to be able to show what things a
> developer is meant to replace.
>
>   is there any way to do this?

I don't know but the best bet would be to find a lexer capable of doing this in
here: https://pygments.org/docs/lexers/
As those are the ones used by Sphinx.

Antonin

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



  reply	other threads:[~2026-01-09  9:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 21:36 is there any way to render content in italics in a code block? Robert P. J. Day
2026-01-09  9:39 ` Antonin Godard [this message]
2026-01-15 10:06 ` [docs] " Quentin Schulz
2026-01-15 15:58   ` Robert P. J. Day
2026-01-15 16:17     ` Quentin Schulz
2026-01-15 21:19       ` Robert P. J. Day

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=DFJYIQV433MB.1DVI67253GCB@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=rpjday@crashcourse.ca \
    /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.