🚀 go-pugleaf

I couldn't find a group that was just about LaTeXinfo, so the above
groups seemed the most likely to have anybody who would know
anything about LaTeXinfo.

Could anybody direct me to a more appropriate group, or help me with a
few little problems.  For anybody that can help, my questions are on
the next page.

ta

Stephen J. Bevan			bevan@cs.man.ac.uk



1. Is there an equivalent of TeXinfo's @itemx?  I want to list various
   command line options that all have the same effect and consequently
   the same explanation.  Using \item to do this results in an extra
   blank line between the items.  For example 

\item[-error-summary]
\item[-error-summary-on]  Display a summary indicating ....

----------------
-error-summary

-error-summary-on  Display a summary indicating ....
----------------

rather than the following which I used to get using @itemx in TeXinfo

----------------
-error-summary
-error-summary-on  Display a summary indicating ....
----------------

2. How do I get blank lines around sections contained in
   \begin{example}\end{example}.  The manual states that the
   \begin\end lines are ignored, so you have to put a blank line in to
   account for this.  Therefore if I do the following :-

-------------------
end of a paragraph.

\begin{example}
Some example I want to give
\end{example}

Start of next paragraph.
---------------------

I expect to see the following in when I view the .dvi file :-

--------------------
end of a paragraph

Some example I want to give

Start of next paragraph
----------------------

However, instead, I get :-

--------------------
end of a paragraph
Some example I want to give
Start of next paragraph
----------------------

This does _not_ happen when I use \begin{verbatim}\end{verbatim} i.e.
I get the blanks I want.  I could solve this I guess by putting a
blank just after the \begin{example} and just before the
\end{example}, but this seems a kludge.  After reading the LaTeXinfo
manual a few times it has dawned on me that maybe the blank line stuff
only works for the info version of the output.  If so great, but it
seems a inconsistent to say the least.