unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Alexandrov <dag@gnui.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Manual consistency
Date: Wed, 10 Jun 2020 23:23:15 +0300	[thread overview]
Message-ID: <tuzifz64.dag@gnui.org> (raw)
In-Reply-To: <87wo4gf9hg.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 09 Jun 2020 19:13:31 +0200")

[-- Attachment #1: Type: text/plain, Size: 1571 bytes --]

Ricardo Wurmus <rekado@elephly.net> wrote:
> Ludovic Courtès <ludo@gnu.org> writes:
>> 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.
>>
>> 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.

May I chime in?

Do I get it right: you are suggesting to remove prompts from .texi and put them back in HTML output only — leaving other formats with not prompts?

And that is only to make them unselectable?  I do not quite understand, why this is needed at all (are there multiline examples in the manual, that expected to be blindly copypasted to terminal?), but in any case no hacks like ‘::before’ are required — ‘user-select: none’ is supported by all modern webengines (yet sometimes with prefix):

	  <style>
	    code .PS1 {
	        -webkit-user-select: none;
	        -moz-user-select: none; /* Not required since F***fox 69. */
	        user-select: none;
	    }
	  </style>
	
	  <pre><code><span class="PS1">$ </span>wget …/guix-install.sh
	<span class="PS1">$ </span>su -
	<span class="PS1"># </span>bash ./guix-install.sh
	  </code></pre>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2020-06-10 20:24 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 [this message]
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=tuzifz64.dag@gnui.org \
    --to=dag@gnui.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).