[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Manual consistency

From: Julien Lepiller
Subject: Re: Manual consistency
Date: Thu, 11 Jun 2020 07:00:24 -0400
User-agent: K-9 Mail for Android

Le 11 juin 2020 04:33:56 GMT-04:00, Ricardo Wurmus <> a écrit 
>Dmitry Alexandrov <> writes:
>> Ricardo Wurmus <> wrote:
>>> Ludovic Courtès <> writes:
>>>> Ricardo Wurmus <> skribis:
>>>>> Julien Lepiller <> 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
>> 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 …/
>>      <span class="PS1">$ </span>su -
>>      <span class="PS1"># </span>bash ./
>>        </code></pre>
>This is good.
>The only minor problem is that with Texinfo we cannot insert
>tags within the context of an example section, so we would have to
>rewrite the HTML via post-processing.

Maybe that's what we want to do? If a line in <pre> satrts with "$ " or "# " 
wrap with a span. That way, we can make them unselectable in html, and they 
still appear in the info manual. We also keep the distinction between $ and #.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]