From: Ricardo Wurmus <rekado@elephly.net>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Manual consistency
Date: Wed, 10 Jun 2020 15:08:52 +0200 [thread overview]
Message-ID: <87o8prf4pn.fsf@elephly.net> (raw)
In-Reply-To: <D48B5B9E-03F2-45E3-82A8-22D99052FFCE@lepiller.eu>
Julien Lepiller <julien@lepiller.eu> writes:
> Le 9 juin 2020 13:13:31 GMT-04:00, Ricardo Wurmus <rekado@elephly.net> a écrit :
>>
>>Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> Hi,
>>>
>>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>>
>>>> Julien Lepiller <julien@lepiller.eu> writes:
>>>>
>>>>> If there is a way to mark a sentence to wrap it into a class, we
>>could
>>>>> also do some CSS magic with :before.
>>>>
>>>> Texinfo puts all examples inside div.example pre.example, but the
>>>> individual lines are not wrapped in spans, so we cannot style each
>>line
>>>> individually. A :before rule would thus only change the first line,
>>>> which is not enough.
>>>
>>> What about adding some more post-processing in doc/build.scm? :-)
>>
>>If we’re okay with wrapping individual lines in @code{…} that won’t be
>>necessary. Having each logical line of code within @code results in
>>
>> <pre class="example">
>> <code>this line</code>
>> <code>that line</code>
>> </pre>
>>
>>and that’s something we *can* style with CSS.
>
> But we can't differentiate root commands and user commands that way.
… if that’s *really* necessary we can post-process in doc/build.scm, but
I think there’s little value in showing a different prompt. While I
have seen it elsewhere, it’s not a universal convention to use “#” as a
root prompt and “$” for an unprivileged prompt.
If we want to clearly indicate that this is done by the root user I
suggest including “su -” at the top of the listing.
--
Ricardo
next prev parent reply other threads:[~2020-06-10 13:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 17:34 Manual consistency zimoun
2020-06-05 18:02 ` Julien Lepiller
2020-06-05 19:50 ` Ricardo Wurmus
2020-06-09 15:55 ` Ludovic Courtès
2020-06-09 17:13 ` Ricardo Wurmus
2020-06-09 18:12 ` Julien Lepiller
2020-06-10 13:08 ` Ricardo Wurmus [this message]
2020-06-10 15:20 ` Ludovic Courtès
2020-06-10 20:23 ` Dmitry Alexandrov
2020-06-11 8:33 ` Ricardo Wurmus
2020-06-11 11:00 ` Julien Lepiller
2020-06-11 18:52 ` Dmitry Alexandrov
2020-06-11 20:53 ` Ricardo Wurmus
2020-06-11 22:58 ` Dmitry Alexandrov
2020-06-05 20:16 ` Ricardo Wurmus
2020-06-09 20:56 ` George Clemmer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8prf4pn.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).