> > > Did you try "@deffn{Escape \@@@{}"?
> > 
> > Yes.  I get something like
> > 
> >   stdin:6278: Missing `}' in @def arg.
> >   stdin:6279: Unmatched }.
> > 
> > while using texi2dvi.  So it fails.
> 
> Do you have problems in texi2dvi or in makeinfo (or both)?

In makeinfo (and consequently in texi2dvi).

> > BTW, the line numbers in error messages are incorrect (I'm using
> > the `-e' switch of texi2dvi which is the reason I think).
>
> Can you throw together a short .texi file which shows incorrect line
> numbers, and then post it?  I don't think I've seen this problem
> since Texinfo 4.0 was released (I assume you are using v4.0).

Looking into tex2dvi (v. 0.43 coming with the texinfo 4.0
distribution), I see that texi2dvi is the problem -- the comment says

  # A sed script that preprocesses Texinfo sources in order to keep
  # the iftex sections only.

Consequently, line numbers are incorrect if an error occurs.

> > What about replacing the macro lines with comment lines instead of
> > removing them completely?
> 
> What for?  What's wrong with the current modus operandi?

I suggest that texi2dvi's `comment_iftex_sed' sed script doesn't
remove `ifinfo' sections but just comment out to have correct line
numbers.


    Werner

_______________________________________________
Bug-texinfo mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-texinfo

Reply via email to