axiom-developer
[Top][All Lists]

## [Axiom-developer] Re: \begin{chunk}

 From: root Subject: [Axiom-developer] Re: \begin{chunk} Date: Sun, 10 Sep 2006 09:32:00 -0400

> > There are axiom-specific latex tags. This is likely to increase
> > rather than decrease. This should be expected as we depend more
> > on latex as our tool. For instance, I have an as-yet-unpublished
> > tag set that removes the use of
> >
> >   <<randomchunck>>=
> >
> > and replaces it with latex syntax
> >
> >   \begin{chunk}{randomchunk}
>
> Tim, when do you plan to make this change?  I realize it can be
> (almost) automated but it would be nice to have that style going
> forward, if that's our final target.  I've been working with auctex and
> mmm-mode trying to convince auctex to quit using code chunks when it
> does its fontifying of the latex part of the document.  Also, if we use
> \begin{chunk} mmm-mode (which handles the dual-mode part of things)
> will need to be taught how to recognize the new environment.  (I know
> you don't need or use these, but for us mortals they are kind of nice
> ;-).  If that change is coming soon I should probably focus on the
> \begin{chunk} syntax (which is probably somewhat simpler to deal with
> anyway).

The change will probably come about once I figure out all the
details of 'environments', which is fairly hairy. TeX is not the
easiest language to learn. I wouldn't worry about the change.

> Also, one idea I want to mention now while there is still time to
> consider it - would it be difficult to have an optional tag for a chunk
> name identifying what language the code chunk is written in?  I ask
> because for a number of applications (emacs mode mapping, syntax
> highlighting in LaTeX using a package whose name escapes me at the
> moment) it would be nice to know what language the chunk is.  Normally
> a file is foo.lisp.pamphlet which works if all of the code chunks in
> that file are lisp, but I know some pamphlets aren't like this.   Would
> it be possible to specify a language (something like
> \begin{chunk}{randomchunk}{boot} in a file.lisp.pamphlet file, for
> example) so it is unambiguous and simple to determine how to deal with
> it?

ummm, I'm unsure of how to handle optional tags in environments
but I'll keep it on the design list.

t