From: Ricardo Wurmus <rekado@elephly.net>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Manual consistency
Date: Fri, 05 Jun 2020 22:16:46 +0200 [thread overview]
Message-ID: <875zc5e09d.fsf@elephly.net> (raw)
In-Reply-To: <703B1E0F-BE41-469D-9357-D3FFAA5CF8FD@lepiller.eu>
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. That will allow us to show the
> prompt while making it non-selectable I think, which is nice visually
> and for copy-pasting. I'm not a texinfo guru though, so I don't know
> if it is feasible.
We can wrap each line in an @example with @code and then style each of
these lines.
So we would do something like this:
--8<---------------cut here---------------start------------->8---
@example
@code{cd /tmp}
@code{tar --warning=no-timestamp -xf \
/path/to/guix-binary-@value{VERSION}.x86_64-linux.tar.xz}
@code{mv var/guix /var/ && mv gnu /}
@end example
--8<---------------cut here---------------end--------------->8---
and then add this CSS rule:
--8<---------------cut here---------------start------------->8---
div.example pre.example code::before {
content: "$ ";
}
--8<---------------cut here---------------end--------------->8---
In the manual sometimes the prompt is # (for root) and sometimes it is $
(when it’s any other user). We cannot distinguish these cases unless we
abuse the Texinfo format by wrapping examples to allow for a more
explicit rule to match.
--
Ricardo
next prev parent reply other threads:[~2020-06-05 20:17 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
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 [this message]
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=875zc5e09d.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).