Re: @verb issues

[Werner LEMBERG]

>> Please also fix `makeinfo` so that `@verb` doesn't create overlong
>> lines in info files.
> 
> This is not immediately easy for me to do.  @verb is treated
> sensibly when the argument does not contain a newline but multiple
> lines in its argument confuse texi2any.  This is something I will
> have to investigate at a later date.

OK, no problem.

> We could still require the @verb argument not to contain a newline
> and not do any line breaking inside.

Mhmm.  I like `@verb`'s current, identical behaviour for both
`texinfo.tex` and HTML output; I guess most people will agree that it
is the 'most natural' one for an in-paragraph command.  In other
words, I much prefer that `info` and the remaining output formats work
in the same way.

> Could you explain what you are using @verb for?

I've tried to use it for LilyPond code snippets appearing inline in
paragraphs.[*] It looked very well suited because, contrary to LaTeX's
`\verb` command, newlines can be part of the argument.  However, I
won't and can't use it because it doesn't work with `info` (yet):
While I can make LilyPond's documentation toolchain use an up-to-date
`texinfo.tex`, I can't expect the same for the user's `info` program.

In other words, my interest in a clean `@verb` implementation is of
academical nature now :-)


    Werner


[*] This gets emitted by a preprocessor script in case syntax
    highlighting for LilyPond code is switched off.  I now use `@code`
    with '@', '{', and '}' properly escaped.