Yocto Project Documentation
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Trevor Woerner" <twoerner@gmail.com>
Cc: "Quentin Schulz" <quentin.schulz@cherry.de>,
	<docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] docs: document the conventions used in the manuals
Date: Tue, 22 Sep 2026 09:32:38 +0200	[thread overview]
Message-ID: <DLLO5AQ7R6L7.1068CI3MBB0FC@bootlin.com> (raw)
In-Reply-To: <arHbV_euXtr9_t0x@localhost.localdomain>

On Tue Sep 22, 2026 at 3:35 AM CEST, Trevor Woerner wrote:
> On Mon 2026-09-21 @ 04:34:35 PM, Antonin Godard wrote:
>> Hi,
>> 
>> On Sat Sep 19, 2026 at 8:17 AM CEST, Trevor Woerner wrote:
>> > On Mon 2026-09-14 @ 06:39:59 PM, Quentin Schulz wrote:
>> [...]
>> > having a
>> > prompt clearly shows what are commands to type and what is output. For
>> > the sake of uniformity I would rather not have code-block examples that
>> > have and others that don't have prompts.
>> 
>> I agree.
>> 
>> >
>> > As for the "what to copy" issue. Every code-block has a "copy" symbol
>> > that appears in the code-block when you hover over the code-block. If
>> > the code-block contains things to type with prompts and you click on the
>> > copy icon of a code-block, the commands are copied and the prompts are
>> > not. However, if the user highlights what to copy by clicking and
>> > dragging with the mouse, they will get both the commands as well as the
>> > prompts. However, that is configurable! It is possible to configure any
>> > code-block identified as console to not copy the prompts, even when
>> > clicked-and-dragged with the mouse.
>> 
>> Do you have a working solution for this?
>
> Yes (to follow).

Actually it seems to be already working for me. After building the docs, I
cannot select either "$" or "root@qemux86-64:~#" so things seem to be working as
expected?

Antonin


  reply	other threads:[~2026-09-22  7:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  3:14 [PATCH] docs: document the conventions used in the manuals Trevor Woerner
2026-08-31  8:18 ` [docs] " Antonin Godard
2026-08-31  8:20   ` Antonin Godard
2026-08-31 13:32   ` Trevor Woerner
2026-09-14 16:39     ` Quentin Schulz
2026-09-19  6:17       ` Trevor Woerner
2026-09-21 14:34         ` Antonin Godard
2026-09-22  1:35           ` Trevor Woerner
2026-09-22  7:32             ` Antonin Godard [this message]
2026-09-22 11:42               ` Trevor Woerner
     [not found]       ` <18D6A461E5931E16.876402@lists.yoctoproject.org>
2026-09-20  8:45         ` Trevor Woerner

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=DLLO5AQ7R6L7.1068CI3MBB0FC@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@cherry.de \
    --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