[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: @verb issues
From: |
Werner LEMBERG |
Subject: |
Re: @verb issues |
Date: |
Sat, 10 Dec 2022 11:47:47 +0000 (UTC) |
> The commands were clearly based on the corresponding LaTeX commands,
> which we should take as authoritative.
OK.
> LaTeX \verb doesn't break on a space, so Texinfo @verb shouldn't
> either. I am going to revert the changes to texinfo.tex and look at
> using in the HTML output. (Sorry.)
No problem. My main concern is consistency – and whatever you do,
please document it.
> If it is going to be useful to have a command for code samples that
> is breakable across lines, which does not need the special
> characters @, { and } to be escaped, then we should consider adding
> another command for this purpose, rather than changing @verb.
Yes. On the other hand, since it wasn't requested until yet I guess
that the need of such a command is not urgent, if at all.
Werner
- Re: @verb issues, (continued)
- Re: @verb issues, Gavin Smith, 2022/12/04
- Re: @verb issues, Gavin Smith, 2022/12/04
- Re: @verb issues, Werner LEMBERG, 2022/12/04
- Re: @verb issues, Gavin Smith, 2022/12/04
- Re: @verb issues, Werner LEMBERG, 2022/12/04
- Re: @verb issues, Gavin Smith, 2022/12/04
- Re: @verb issues, Werner LEMBERG, 2022/12/04
- Re: @verb issues, Gavin Smith, 2022/12/07
- Re: @verb issues, Werner LEMBERG, 2022/12/07
- Re: @verb issues, Gavin Smith, 2022/12/10
- Re: @verb issues,
Werner LEMBERG <=
- w-nolinebreak-text class in HTML output, Gavin Smith, 2022/12/10
- Re: w-nolinebreak-text class in HTML output, Patrice Dumas, 2022/12/10
- Re: @verb issues, Gavin Smith, 2022/12/04
Re: @verb issues, Werner LEMBERG, 2022/12/04