🚀 go-pugleaf

ajayshah@alhena.usc.edu (Ajay Shah) writes:

>I just finished uploading the Texinfo manual and it seems to be pretty
>far from TeX in look and feel.  I was surprised to see no mention in
>the manual of how new Texinfo commands may be written in terms of
>existing ones.  

>Is one supposed to say @iftex \def???
>But that would screw up things when you try to use the macro in the
>main text, and the info file would not reflect that definition.

>        -ans.

>-- 

>Ajay Shah, (213)749-8133, ajayshah@usc.edu

Well, how would emacs know how to format your new functions. texinfo is
restricted compared to ordinary tex. If you are not fanatic with tex, you may
want to try out latexinfo, which is a latex counterpart of texinfo. As the
names suggests, it is based on latex instead of tex. I find that an advantage
since I'm more acustomed to latex than palin tex. Furthermore this package
contains a number of enhancements, extendability being one. This is implemented
using the latex notion of styles. The idea is to create a special style,
containing the new stuff, and then write an elisp file to format the new
macros, which is automatically included upon formating. You still have to do it
yourself, but it goes a long way to automate process.

Another nice feature is a auto nodify commando.

Check it out, it's a real nice package. (I can supply you with an ftp address
if necessary).



------------------------------------------------------------------------------
Christian Lynbech

DAIMI						office: R0.32   phone: 5034
University of Aarhus,DK-Denmark                 email: lynbech@daimi.aau.dk
------------------------------------------------------------------------------
			  EMACS, The One True Editor                       


Hit the philistines three times over the head with the Elisp reference manual.

                                        - petonic@hal.com (Michael A. Petonic)