[Axiom-developer] Pamphlet format discussion

Note that section 12.3 of the AUCTeX manual explains how to insert the chunk environment into AUCTeX. Thus emacs users should be able to customize chunk environments trivially. In chunk.el you add (TeX-add-style-hook "chunk" (lambda () (LaTeX-add-environments '("chunk" "chunkname" Tim

[Axiom-developer] Pamphlet format discussion

The current silver version in axiom.sty uses the latex alltt environment. This environment is shipped with standard latex. As I mentioned before we could easily choose to use fancyvrb rather that alltt. The alltt envir

[Axiom-developer] Pamphlet format discussion

> I don't understand. What are the active characters in a begin{chunk} > environment. Why do you need to escape `[[', for example? Normally you would not. I'm suggesting that it is entirely possible to side-step the escape question for any given set of characters for any given language in a trivia

[Axiom-developer] Pamphlet format discussion

I should also note that the idea of using tangle/weave processing on standard latex documents using lisp is not new, and not my idea. Some of the input files in the IBM/NAG versions of Axiom were generated by scanning the Jenks book and generating the hyperdoc pages. That is why the Jenks book sou

[Axiom-developer] Pamphlet format discussion

Steve writes: > The idea is to allow different concepts to be associated with the > sequences. For example, @[some [EMAIL PROTECTED] when appearing in a code > chunk > could escape into raw latex. Each of these special syntax options means a learning curve for the new user. These special syntax m

Re: [Axiom-developer] Pamphlet format discussion

--- Bill Page <[EMAIL PROTECTED]> wrote: > Certainly I don't want to spend my time working on this, but I was > thinking more of people like Norman Ramsey and other people who > already use noweb. Why not embrace the concept of co-operating with > other open source projects instead of re-inventin

Re: [Axiom-developer] Pamphlet format discussion

On 7/21/07, C Y <[EMAIL PROTECTED]> wrote: ... Once the autoconf work becomes mainstream, this won't matter. The build logic can presumably be set up such that if noweb is specified as the literate programming tool, the other tools never need to be touched by the build. In that scenario, as lon

Re: [Axiom-developer] Pamphlet format discussion

C Y <[EMAIL PROTECTED]> writes: > Ideally, once these things are done they will require very little work > as long as a working Lisp environment is present, but again it would > matter ONLY to the people wanting to use it. The only point at which > it becomes a real issue is if the pamphlets go in

Re: [Axiom-developer] Pamphlet format discussion

--- Bill Page <[EMAIL PROTECTED]> wrote: > On 21 Jul 2007 03:42:15 -0500, Gabriel Dos Reis wrote: > > The objection as, I understand it, is against having the common toy > > (Axiom) move to duplicating functionalities (already provided by > > external tools) and having to maintain the source code

Re: [Axiom-developer] Pamphlet format discussion

... Tim Daly wrote: | There are no "current and future" resources. This is a volunteer effort | and we only get to decide our own resource usage. Objecting to the use | other people make of their time isn't a topic of debate. On 21 Jul 2007 03:42:15 -0500, Gabriel Dos Reis wrote: The objection,

Re: [Axiom-developer] Pamphlet format discussion

On 21 Jul 2007 03:29:01 -0500, Gabriel Dos Reis wrote: "Bill Page" writes: [...] | Integrating noweb into Axiom to support the current pamphlet file | format seems entirely reasonable to me. I think calling noweb as a | system supplied utility is the best approach. Please don't go out of your

[Axiom-developer] Pamphlet format discussion

Cliff, Andrey, Steve, I hope to demonstrate the ability to extract a small, well defined portion of a pamphlet file in response to an axiom help command using the lisp-level weave. Thus I'd like to be able to say )help DHMATRIX )examples which involves extracting just the portion of the dhmatr

[Axiom-developer] Pamphlet format discussion

Cliff, Andrey It would be trivial to add another argument to the chunk to allow your optional language argument. See the silver file src/doc/axiom.sty.pamphlet, lines 16-63 In particular, see line 50. To add the optional argument line 50, which now reads: \newenvironment{chunk}[1]{ would be

[Axiom-developer] Pamphlet format discussion

Stephen, The current silver axiom.sty definition of the axiom environment definition uses the alltt verbatim environment which is shipped with standard latex. This could trivially be changed to use the fancyvrb environment. See the silver file src/doc/axiom.sty.pamphlet, lines 16-63 In particular

Re: [Axiom-developer] Pamphlet format discussion

"Bill Page" <[EMAIL PROTECTED]> writes: [...] | Integrating noweb into Axiom to support the current pamphlet file | format seems entirely reasonable to me. I think calling noweb as a | system supplied utility is the best approach. Please don't go out of your way to "copy" noweb into Axiom. Make

Re: [Axiom-developer] Pamphlet format discussion

[EMAIL PROTECTED] writes: [...] | Architectural decisions are reasonably subject to objection and vote. | Construction decisions follow from necessity and aren't appropriate | for voting. Since the construction is that of a common toy, it makes sense that active maintainers have a say on where

Re: [Axiom-developer] Pamphlet format discussion

[EMAIL PROTECTED] writes: | Bill writes: | >>> Integrating noweb into Axiom to support the current pamphlet file | >>> format seems entirely reasonable to me. I think calling noweb as a | >>> system supplied utility is the best approach | | Tim writes: | >> In the current system the result would

[Axiom-developer] Pamphlet format discussion

Bill writes: >>> Integrating noweb into Axiom to support the current pamphlet file >>> format seems entirely reasonable to me. I think calling noweb as a >>> system supplied utility is the best approach Tim writes: >> In the current system the result would be the same from the user >> perspective.

[Axiom-developer] Pamphlet format discussion

Bill, Tim writes: >> I agree that the status quo use of noweb is entirely adequate. >> We differ in the future planned use. I believe that noweb functionality >> (tangle/weave) needs to be integrated into Axiom so that the pamphlet >> file format becomes entirely native, enabling long term goals

Re: [Axiom-developer] Pamphlet format discussion

On 7/21/07, Tim Daly wrote: I agree that the status quo use of noweb is entirely adequate. We differ in the future planned use. I believe that noweb functionality (tangle/weave) needs to be integrated into Axiom so that the pamphlet file format becomes entirely native, enabling long term goals.

[Axiom-developer] Pamphlet format discussion

Bill, I agree that the status quo use of noweb is entirely adequate. We differ in the future planned use. I believe that noweb functionality (tangle/weave) needs to be integrated into Axiom so that the pamphlet file format becomes entirely native, enabling long term goals. Tim _

[Axiom-developer] Pamphlet format discussion

Steve, I agree that we need a weave function in order to enable possible extensions of functionality, and for integration with Axiom as a whole. We differ in the implementation question of that weave function. Tim ___ Axiom-developer mailing list A

[Axiom-developer] Pamphlet format discussion

Bill, Is a fair statement of your position: The status quo use of noweb is entirely adequate. Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer

[Axiom-developer] Pamphlet format discussion

Andrey, Is a fair statement of your position: Latex is sufficient to handle all current requirements, thus removing the need for noweb and its syntax. Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/

[Axiom-developer] Pamphlet format discussion

Steve, So the statement of your concern is: We need a weave function in order to enable possible extensions of functionality, and for integration with Axiom as a whole. Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.no

[Axiom-developer] Pamphlet format discussion

Steve, Another try: Would a correct summary of your concern be: We need to provide a weave function in order to enable possible future pamphlet format extensions. Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.o

[Axiom-developer] Pamphlet format discussion

Stephen, Would a correct summary of your concern be: Axiom pamphlet format should not be restricted to latex syntax? Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer