Re: Manual consistency

[Julien Lepiller]

Le 11 juin 2020 04:33:56 GMT-04:00, Ricardo Wurmus <rekado@elephly.net> a écrit 
:
>
>Dmitry Alexandrov <dag@gnui.org> writes:
>
>> 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>
>
>This is good.
>
>The only minor problem is that with Texinfo we cannot insert
>conditional
>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 #.