Stefan Monnier wrote: > And this type of bug can be very nasty when it does occur. Even with > the equal length heuristic, the situation leading to bugs is not > really that excessively unlikely in certain situations, like, for > instance, quoting program output or input inside @verbatim or > @verbatiminclude.
I think such sample text should be indented, otherwise even a human reader could get confused. @verbatim and @verbatiminclude (and @format) do not indent. See `(texinfo)GNU Sample Texts' for an example of actual unindented verbatimly quoted program input. (It does not suffer from the bug we are discussing, but other similarly quoted text easily could.) The unindented @verbatim block is the last thing in the file and is clearly introduced as such. Because of that, there is no danger of confusion. The block of text is so large that it would look bad if indented. If there were a node "Sample Texinfo File" containing nothing but the quoted text, indenting the entire node would even look worse. The idea is to make the quoted text look as close as possible to the actual file. When literally quoting heavily indented text, with the purpose of illustrating that indentation, it might be difficult to distinguish unindented lines from lines with one or two lines of indentation if extra indentation were added, Of course, if you insert unindented @verbatim blocks _in the middle of a node_, then you have to be very careful to avoid confusion. Sincerely, Luc. _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel
