[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Axiom-developer] (no subject)

From: root
Subject: [Axiom-developer] (no subject)
Date: Wed, 20 Nov 2002 07:36:39 -0500

In-reply-to: <address@hidden> (message from
        Joris van der Hoeven on Wed, 20 Nov 2002 12:31:07 +0100 (MET))
Subject: Re: [Texmacs-dev] [Axiom-developer] visual literate programming
Reply-to: address@hidden
References:  <address@hidden>
--text follows this line--

At the moment there are no formal requirements for a pamphlet file.
I hope to develop them in the future. In particular the plans call
for required sections on test cases, user help, examples, etc. which
will be "exploded" to various parts of the filesystem. The only case
used at the moment is in .c.pamphlet files which contain both the
.c and the .h code, both of which are broken out at compile time.
Also the cross-reference section will be used to automatically
load required pamphlets.

I'll retry the \subsubsection and \cite cases. I could easily have
screwed something up. I think that we can recognize the code
chunking mechanism in noweave's output and have TeXmacs handle it
properly. I'm not sure of all of the details of TexMacs or noweb
but we'll figure it out. 

Norman's noweb wraps code in the sequence, causing a "definition"
<<some identifying string>>=
where everything outside the <<>>= ... @ is considered text.
Code between the boundaries is basically a verbatim environment.

Code definitions are "used" by specifying:
<<some identifying string>>
Notice the lack of trailing equal sign.

Joris, can you point me at some specific part of the TeXmacs docs
that will help us develop a pamphlet "style" file. A style file
that properly handle noweb vanilla output would be quite useful.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]