🚀 go-pugleaf

When formatting a texinfo file with texinfo-format-buffer, I have run
into problems where i have a table emphasized by @var which contains
@dots{} as items, such as 

@table @var
@item <tag>
@item PARENT
Or 1 if there isn't one.
@item LENGTH
Number of entries.
@item OBJ1
@item @dots{}
@item OBJLENGTH
@end table

When i am formatting this, i get an error message stating that @DOTS
isn't recognized, presumably because @var converts the @dots{} to
@DOTS{} which is then an invalid command.  I've fixed this problem by
adding the line

(put 'DOTS 'texinfo-format 'texinfo-format-dots)

to texinfmt.el, but that's hardy an optimal solution.  Mightn't it be
a better idea to have @var, etc. be a bit smarter and not try to
convert commands and arguments to commands?

Also, wouldn't it make more sense in texinfo.tex to have

\def\asis#1{{\rm #1}}

instead of

\def\asis#1{#1}

?  Sometimes I want to protect some text from a surrounding @var or
whatever, and having @asis take care of that would seem to me to be
the sensible way of doing things.

(By the way, texinfo.tex doesn't have any such problems with nested
commands, or at least doesn't have this problem.  And i am using the
versions of these packages that came with emacs-18.56.)

david carlton
carlton@husc10.harvard.edu