On 11/09/2006 01:53 AM, Gabriel Dos Reis wrote:
"Page, Bill" <[EMAIL PROTECTED]> writes:
[...]
| > > | So "xdvi axiom.sty.pamphlet.dvi" is absolutely no argument.
| >
| > > Unfortunately, for Axiom, that is going to be an argument for
| > > the short and mi-term.
| >
| > Are you so sure? Whe
| I think what Gaby is suggesting is that aaa.tex would be extracted
| to some directory other than the current directory, e.g.
Yes, exactly.
Yep. When Gaby was saying something about "from where latex is called"
that made me test this situation. You are right. In that way we can
avoid to ren
> Given recent discussions, I would very much appreciate Tim shime in.
I have no opinion.
Tim
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer
"Page, Bill" <[EMAIL PROTECTED]> writes:
[...]
| > > | So "xdvi axiom.sty.pamphlet.dvi" is absolutely no argument.
| >
| > > Unfortunately, for Axiom, that is going to be an argument for
| > > the short and mi-term.
| >
| > Are you so sure? Where should I branch from for that experiment?
| >
|
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
[...]
| And thank you, Bill. I really should change "appending .tex" to
| "appending .texinclude" or something like that.
We should appoint Bill as Axiom Speaker :-)
I'm semi serious :-)
-- Gaby
___
Axiom-d
"Page, Bill" <[EMAIL PROTECTED]> writes:
| On Wednesday, November 08, 2006 6:27 PM Ralf Hemmecke wrote:
| >
| > On 11/09/2006 12:17 AM, Gabriel Dos Reis wrote:
| > > Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| > >
| > > [...]
| > >
| > > | Since when you compile axiom.sty.tex also axiom.sty mus
On Wednesday, November 08, 2006 7:07 PM Ralf Hemmecke wrote:
> On 11/09/2006 12:37 AM, Gabriel Dos Reis wrote:
> > Ralf Hemmecke <[EMAIL PROTECTED]> writes:
>
> > | There is only *one* dvi file that will be produced and
> > | *not* one for every .nw file.
> >
> > Ah, but that is a fundamental di
On Wednesday, November 08, 2006 6:27 PM Ralf Hemmecke wrote:
>
> On 11/09/2006 12:17 AM, Gabriel Dos Reis wrote:
> > Ralf Hemmecke <[EMAIL PROTECTED]> writes:
> >
> > [...]
> >
> > | Since when you compile axiom.sty.tex also axiom.sty must be in
> > | the path \usepackage will always take axiom.
On 11/09/2006 12:37 AM, Gabriel Dos Reis wrote:
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| There is only *one* dvi file that will be produced and *not* one for
| every .nw file.
Ah, but that is a fundamental distinction between the respective
states of Axiom and your peoject.
Of course.
Ah, one last remark. I don't yet have a complete understanding of LEO,
but, in fact, what I am suggesting now should not prevent us from
introducing LEO at a later stage (I think). Noweb files are noweb files.
LEO maintains them in some way I suggest to do it in another way (maybe
only because
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| > Yes. This problem has many roots. Part of it is that
| > build-improvements extracts the TeX file in the same directory as it
| > latexs it. The problem can be papered over in many different way:
| > (1) add .tex unconditionally.
| > (2) replace
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
[...]
| There is only *one* dvi file that will be produced and *not* one for
| every .nw file.
Ah, but that is a fundamental distinction between the respective
states of Axiom and your peoject.
| So "xdvi axiom.sty.pamphlet.dvi" is absolutely no argumen
Thanks again for your patience.
Thank you for listening. ;-)
Ralf
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer
"Page, Bill" <[EMAIL PROTECTED]> writes:
[...]
| > > Bill Page wrote:
| > > | Changing axiom.sty.pamphlet to axiom-sty.pamphlet and added a
| > > | chunk named <>= still seems like the right thing
| > > | to do to avoid this "bug". I one sentence explanation in the
| > > | pamphlet file should b
On Wednesday, November 08, 2006 5:18 PM Ralf Hemmecke wrote:
> ...
> Wow. I must be doing something wrong. I already question whether
> I should use German to get my idea through. English doesn't
> seem to work. ;-)
> ...
> There is only *one* dvi file that will be produced and *not* one
> for e
On 11/09/2006 12:17 AM, Gabriel Dos Reis wrote:
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
[...]
| Since when you compile axiom.sty.tex also axiom.sty must be in the
| path \usepackage will always take axiom.sty.tex instead. So the option
| of moving the files to another place does not help sinc
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
[...]
| Since when you compile axiom.sty.tex also axiom.sty must be in the
| path \usepackage will always take axiom.sty.tex instead. So the option
| of moving the files to another place does not help since they must be
| visible at the same time.
Sorry,
On Wednesday, November 08, 2006 4:39 PM Ralf Hemmecke wrote:
>...
> Most of you opt now for renaming axiom.sty.pamphlet to something
> else (like axiom-sty.pamphlet). I rather like to see the general
> rule that the generation should go (Rule 2) :
>
> noweave file.pamphlet > file.pamphlet.tex
>
Yes. This problem has many roots. Part of it is that
build-improvements extracts the TeX file in the same directory as it
latexs it. The problem can be papered over in many different way:
(1) add .tex unconditionally.
(2) replace .pamphlet with .tex and pay attention
(3) extract to a diff
3) Files with unnecessarily long names are more awkward to use.
Ok I admit that reasons 2) and 3) are not very strong reasons...
Not even 1) is a reason. Why do you believe one can say
make dvi
in ALLPROSE and then say
xdvi myalps.dvi
to get the whole documentation although I have the convent
On 11/08/2006 04:00 PM, Gabriel Dos Reis wrote:
"Page, Bill" <[EMAIL PROTECTED]> writes:
| On Wednesday, November 08, 2006 8:19 AM Gaby wrote:
| > ...
| > Bill Page wrote:
| > | In my opinion it is only an accident that axiom.sty.pamphlet
| > | has this name and contains only one root chunk. In
"Page, Bill" <[EMAIL PROTECTED]> writes:
| On Wednesday, November 08, 2006 8:19 AM Gaby wrote:
| > ...
| > Bill Page wrote:
| > | In my opinion it is only an accident that axiom.sty.pamphlet
| > | has this name and contains only one root chunk. In general this
| > | is not the case.
| >
| > The a
Martin Rubey <[EMAIL PROTECTED]> writes:
| Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
|
| > Martin Rubey <[EMAIL PROTECTED]> writes:
| >
| > | Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
| > |
| > | > I very much like hyperlinks pointing to sections in other files. I
really
| > | > disliuk
On Wednesday, November 08, 2006 8:19 AM Gaby wrote:
> ...
> Bill Page wrote:
> | In my opinion it is only an accident that axiom.sty.pamphlet
> | has this name and contains only one root chunk. In general this
> | is not the case.
>
> The axiom.sty.pamphlet is inded very special. Its purpose and
"Page, Bill" <[EMAIL PROTECTED]> writes:
[...]
| Good question. If the rule is "add .tex" then the result is
|
| latex myalps.nw.tex --> myalps.nw.dvi
|
| not myalps.dvi. You must be doing something more to hide the .nw.
>From my perspective, I find .nw and .pamphlet as implementation
detail
Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
> Martin Rubey <[EMAIL PROTECTED]> writes:
>
> | Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
> |
> | > I very much like hyperlinks pointing to sections in other files. I really
> | > disliuke duplicating documentation for no good reasons. But, I do
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
[...]
| That is an argument. But perhaps for all those of us who are not so
| familiar with non-Linux, it would be more helpful to say which systems
| these are. The only system I know would be DOS. But then forget about
| the .pamphlet extension. You onl
Ralf Hemmecke wrote:
>>> | > The drastic way... Remove axiom.bib.pamphlet
>
> Sorry, I take that back. Only remove (most of) the (file referencing)
> content.
>
> I am very much in favour of having a central .bib file (or a collection
> of them in a central place), but with actual references to p
"Page, Bill" <[EMAIL PROTECTED]> writes:
| On Wednesday, November 08, 2006 3:11 AM Martin Rubey wrote:
| >
| > I pressed C-c C-c in gnus, not in the pamphlet... Sorry,
| > continuation below
| >
|
| What is 'gnus'?
News and mail reader: That is what I've been for ages now, to read
bpth newsgr
"Page, Bill" <[EMAIL PROTECTED]> writes:
[...]
| I think that in future updates to the pamphlet files we should
| encourage the use hyperref where relevant to include hypertex
| links directly in the dvi/pdf files.
That makes sense.
-- Gaby
___
Axio
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
[...]
| I hope that makes my intentions a bit clearer.
It does; thanks!
| > I very much like hyperlinks pointing to sections in other files. I
| > really disliuke duplicating documentation for no good reasons. But, I
| > don't know what ALLPROSE looks l
Martin Rubey <[EMAIL PROTECTED]> writes:
| Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
|
| > I very much like hyperlinks pointing to sections in other files. I really
| > disliuke duplicating documentation for no good reasons. But, I don't know
| > what ALLPROSE looks like in practice (sorry,
Ralf Hemmecke wrote:
>> I think perhaps the pamplet files should interact with hyperdoc. Or
>> rather hyperdoc should be replaced with a web browser interface that
>> would integrate with the dvi/pdf files including hyperlinks between
>> them.
>
> I am more in favour of any webbrowser than hyperdo
Oh, so much email over such a simple thing ... :-(
On Wednesday, November 08, 2006 6:29 AM Ralf Hemmecke wrote:
> ...
> Bill Page wrote:
> >It would be very strange to see
> >
> > latex name.tex --> name.tex.dvi
> > dvipdfm name.tex.dvi --> name.tex.dvi.pdf
> >
> >wouldn't it?
> "Page, Bill" <[EMAIL PROTECTED]> writes:
>
> [...]
>
> | However pamphlet files with multiple chunks interact badly with
> | the make dependency processing since changing or adding a single
> | chunk in a pamphlet file triggers re-extraction of all files
> | dependent on that pamphlet and subse
1) All other programs that I can think of that process an
input file with a given extension, generate output files
by replacing the extension with one appropriate to the
output. E.g.
latex name.tex --> name.dvi
dvipdfm name.dvi --> name.pdf
In latex this happens even if t
"Page, Bill" <[EMAIL PROTECTED]> writes:
> On Wednesday, November 08, 2006 3:11 AM Martin Rubey wrote:
> >
> > I pressed C-c C-c in gnus, not in the pamphlet... Sorry,
> > continuation below
> >
>
> What is 'gnus'?
the mailer/newsreader I use...
Thanks for your explanations, I think I underst
On Wednesday, November 08, 2006 3:11 AM Martin Rubey wrote:
>
> I pressed C-c C-c in gnus, not in the pamphlet... Sorry,
> continuation below
>
What is 'gnus'?
> Martin Rubey <[EMAIL PROTECTED]> writes:
>
> >
> > Ralf Hemmecke <[EMAIL PROTECTED]> writes:
> >
> > > What speaks so much agains
On 11/08/2006 11:09 AM, Humberto Ortiz-Zuazaga wrote:
Gabriel Dos Reis wrote:
The LP idea, and the pamphlet files by implication, works beautifully
when you get everything right from the start and you don't have to
look under the hood (e.g. debugging, etc.). By definition, if you're
not using
Gabriel Dos Reis wrote:
> The LP idea, and the pamphlet files by implication, works beautifully
> when you get everything right from the start and you don't have to
> look under the hood (e.g. debugging, etc.). By definition, if you're
> not using it for an evolving system -- which by definition
I think perhaps the pamplet files should interact with hyperdoc. Or
rather hyperdoc should be replaced with a web browser interface that
would integrate with the dvi/pdf files including hyperlinks between
them.
I am more in favour of any webbrowser than hyperdoc. Hyperdoc looks old.
The contents
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
> I am very much in favour of having a central .bib file (or a collection of
> them in a central place), but with actual references to papers and
> books. Even better would be what once was in discussion... Online
> documentation should directly link a ref
| > The drastic way... Remove axiom.bib.pamphlet
Sorry, I take that back. Only remove (most of) the (file referencing)
content.
I am very much in favour of having a central .bib file (or a collection
of them in a central place), but with actual references to papers and
books. Even better wo
On 11/08/2006 03:39 AM, Gabriel Dos Reis wrote:
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| >> Underscores would be no problem at all if filenames where | >>
properly tagged. Note that there is a latex package called url | >>
(/usr/share/texmf/tex/latex/misc/url.sty) which provides a \path | >
I pressed C-c C-c in gnus, not in the pamphlet... Sorry, continuation below
Martin Rubey <[EMAIL PROTECTED]> writes:
> Dear all,
>
> Ralf Hemmecke <[EMAIL PROTECTED]> writes:
>
> > What speaks so much against just adding .tex?
>
> I'd also speak in *favour* of simply adding .tex. It makes life
Dear all,
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
> What speaks so much against just adding .tex?
I'd also speak in *favour* of simply adding .tex. It makes life easier also in
other places:
### The following is only for those who use auctex in emacs for latexing!) ###
I use auctex and adde
Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
> I very much like hyperlinks pointing to sections in other files. I really
> disliuke duplicating documentation for no good reasons. But, I don't know
> what ALLPROSE looks like in practice (sorry, I cannot do everything...)
Do you have Axiom with A
On Tuesday, November 07, 2006 10:39 PM I wrote:
> ...
>
> I propose that we remove axiom.bib.pamphlet.
>
> There is no axiom.bib.tex as far as I can tell - only axiom.bib.
>
> But the idea of including citations to pamphlet files seems ill-
> conceived to me. There is no documentation in the ax
On Tuesday, November 07, 2006 7:59 PM Ralf Hemmecke wrote:
> ...
> I have a simple suggestion. Forget the Axiom user for a
> moment. First we need to have good documentation for developers.
> A user probably cares most about the "algebra" subdirectory.
> I don't care too much about interaction wi
>
> | On Tuesday, November 07, 2006 7:05 PM Ralf Hemmecke wrote:
> | >
> | > Waldek wrote:
> | > ...
> | > > | 3) axiom.bib.tex file contains 10 file names with
> | > > |unescaped underscores inside.
> | > ...
> | > Gaby wrote:
> | > > For problem (3), I'm awaiting for input from others.
>
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| >> Underscores would be no problem at all if filenames where
| >> properly tagged. Note that there is a latex package called url
| >> (/usr/share/texmf/tex/latex/misc/url.sty) which provides a \path
| >> command. Together with hyperref one can turn that
"Page, Bill" <[EMAIL PROTECTED]> writes:
| On Tuesday, November 07, 2006 7:05 PM Ralf Hemmecke wrote:
| >
| > Waldek wrote:
| > ...
| > > | 3) axiom.bib.tex file contains 10 file names with
| > > |unescaped underscores inside.
| > ...
| > Gaby wrote:
| > > For problem (3), I'm awaiting for
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
[...]
| > In the mean time, I think just renaming axiom.sty as Waldek
| > suggested is not so confusing, given the discussion in the rest
| > of this thread. Maybe instead of 'axiom-sty.pamphlet' something
| > like 'axiom-latex.pamphlet' might be a better
"Page, Bill" <[EMAIL PROTECTED]> writes:
[...]
| However pamphlet files with multiple chunks interact badly with
| the make dependency processing since changing or adding a single
| chunk in a pamphlet file triggers re-extraction of all files
| dependent on that pamphlet and subseqent dependent m
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
[...]
| What speaks so much against just adding .tex?
Simplicity in the extensions. And yes, portability matters if you
take it seriously.
| Portability? Look at the output of
|
| cd build-improvements
| find . -name '*.*.pamphlet'
|
| Is there a pla
"Page, Bill" <[EMAIL PROTECTED]> writes:
[...]
| > Bill Page wrote:
| > | Maybe it should be written:
| > |
| > | notangle file.pamphlet -R 'file.c' > file.c
| >
| > Yes, that is was it is written:
| >
| > $(builddir)/%.c: $(srcdir)/%.pamphlet
| > $(axiom_build_document) --t
Underscores would be no problem at all if filenames where
properly tagged. Note that there is a latex package called url
(/usr/share/texmf/tex/latex/misc/url.sty) which provides a \path
command. Together with hyperref one can turn that also into
hyperlinks.
I like this idea but I think it might
On Tuesday, November 07, 2006 7:32 PM Ralf Hemmecke wrote:
> ...
> I agree that LP suggests to think in terms of logical units for
> humans, but on the other hand I am still a bit old-fashioned
> (and maybe also human), since I would have hard times to look
> in the file system for the place of a
On Tuesday, November 07, 2006 7:05 PM Ralf Hemmecke wrote:
>
> Waldek wrote:
> ...
> > | 3) axiom.bib.tex file contains 10 file names with
> > |unescaped underscores inside.
> ...
> Gaby wrote:
> > For problem (3), I'm awaiting for input from others.
>
> The drastic way... Remove axiom.bib
However pamphlet files with multiple chunks interact badly with
the make dependency processing since changing or adding a single
chunk in a pamphlet file triggers re-extraction of all files
dependent on that pamphlet and subseqent dependent make processing.
To over come this, we would have modify
On 11/07/2006 10:45 PM, Gabriel Dos Reis wrote:
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| I oppose against special treatment of .sty files.
|
| The general rule should be
|
| notangle file.ext.pamphlet > file.ext
| noweave file.ext.pamphlet > file.ext.pamphlet.tex
|
| remove ".pamphlet" a
Ralf,
On Tuesday, November 07, 2006 6:31 PM you wrote:
> ...
> What speaks so much against just adding .tex?
> Portability? Look at the output of
>
> cd build-improvements
> find . -name '*.*.pamphlet'
>
> Is there a plan to rename them all?
>
Ugh! You are right. Despite Gaby's implication,
It is possible to use srcltx even if we don't keep the
*.pamphlet.* part if we assume that all .dvi files are
derived from .pamphlet files. Right? I think this is a
reasonable assumption for Axiom given the policy on literate
programming.
srcltx does nothing else than writing setting a counter f
| 3) axiom.bib.tex file contains 10 file names with unescaped underscores
|inside.
| BTW. I am a bit annoyed because of discrimination of underscores (I like
| them very much), so I am tempted to solve 3 by making underscore into
| an active character, which expands to ordinary underscore
On November 07, 2006 5:43 PM Ralf Hemmecke wrote:
> ...
> One suggestion could be to have particular chunk names that
> say what are the "top-level" chunks and which are the
> corresponding filenames for notangle.
Yes, I agree that the convention for notangle should interact
with chunk names. Th
I think the only convincing reason that Ralf gave for his
convention for noweave was interaction with point-and-click
in dvi. But this could be achieved through a different
patch to srcltx. No?
But I guess that patch would be a bit longer. In the patch I gave, I use
the fact that [EMAIL PROTECT
"Page, Bill" <[EMAIL PROTECTED]> writes:
[...]
| > this _is_ alredy broken by many files (in 'src/hyper') when we
| > have
| >
| > file.pamphlet -> file.c
| >
|
| Is there a case like this?
yes, many of the C pamphlet files. My eyes was caught by that, but
quickly my brain said it was OK, bec
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
[...]
| Still, I would rather like to see a general scheme than just adjusting
| locally. Keep the rules simple (or rather: introduce simple rules).
I, too, would like to see simple rules that resolve this issue in
general and simple manner (I can think
| And I _suggested_ to change the current rule.
I thought your suggestion was
remove ".pamphlet" and add ".tex". That rule seems to be a bit simpler
than having to explain why .sty files must be treated separately.
Is that correct?
If I ever suggested that, I must have made a terrible
On Tuesday, November 07, 2006 5:17 PM Waldek Hebisch wrote:
>
> Ralf Hemmecke wrote:
> > I oppose against special treatment of .sty files.
> >
> > The general rule should be
> >
> > notangle file.ext.pamphlet > file.ext
> > noweave file.ext.pamphlet > file.ext.pamphlet.tex
> >
> > remove ".pam
Waldek Hebisch <[EMAIL PROTECTED]> writes:
[...]
| this _is_ alredy broken by many files (in 'src/hyper') when we
| have
|
| file.pamphlet -> file.c
|
| or
|
|/-> file.h
| file.pamphlet -|
|\-> file.c
|
I considered that some time ago.
However, I must confe
On 11/07/2006 11:17 PM, Waldek Hebisch wrote:
Ralf Hemmecke wrote:
I oppose against special treatment of .sty files.
The general rule should be
notangle file.ext.pamphlet > file.ext
noweave file.ext.pamphlet > file.ext.pamphlet.tex
remove ".pamphlet" and add ".tex". That rule seems to be a b
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| On 11/07/2006 10:45 PM, Gabriel Dos Reis wrote:
| > Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| > | I oppose against special treatment of .sty files.
| > | | The general rule should be
| > | | notangle file.ext.pamphlet > file.ext
| > | noweave file.ext
Ralf Hemmecke wrote:
> I oppose against special treatment of .sty files.
>
> The general rule should be
>
> notangle file.ext.pamphlet > file.ext
> noweave file.ext.pamphlet > file.ext.pamphlet.tex
>
> remove ".pamphlet" and add ".tex". That rule seems to be a bit simpler
> than having to expl
On 11/07/2006 10:45 PM, Gabriel Dos Reis wrote:
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| I oppose against special treatment of .sty files.
|
| The general rule should be
|
| notangle file.ext.pamphlet > file.ext
| noweave file.ext.pamphlet > file.ext.pamphlet.tex
|
| remove ".pamphlet"
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| I oppose against special treatment of .sty files.
|
| The general rule should be
|
| notangle file.ext.pamphlet > file.ext
| noweave file.ext.pamphlet > file.ext.pamphlet.tex
|
| remove ".pamphlet" and add ".tex".
Ralf,
remove ".pamphlet" and ad
Waldek Hebisch <[EMAIL PROTECTED]> writes:
| I tried again 'make dvi' in build-improvements. There are still three
| problems:
| 1) typo in 'src/etc/Makefile.pamphlet'
| 2) confusion because Latex prefers 'axiom.sty.tex' in current directory
|to 'axiom.sty' in search path
| 3) axiom.bib.tex fi
I oppose against special treatment of .sty files.
The general rule should be
notangle file.ext.pamphlet > file.ext
noweave file.ext.pamphlet > file.ext.pamphlet.tex
remove ".pamphlet" and add ".tex". That rule seems to be a bit simpler
than having to explain why .sty files must be treated sep
> That sounds like a pretty neat idea. But wouldn't using TeX to do the
> tangling be inefficient for large programs? (This isn't a rhetorical
> question; I have no idea.)
i have no idea but i do have practical experience.
in work i have a project that is a literate program.
the pamphlet file h
root <[EMAIL PROTECTED]> writes:
...
> yes. i'm learning a lot about the tex language so it's taking time.
> latex does similiar processing to handle bibligraphic and index files.
For LaTeX, isn't an external program usually called to format the
index files?
> if latex can do code chunks directl
"Bill Page" <[EMAIL PROTECTED]> writes:
| Here is a patch to Rosetta.pamphlet to make it a real pamphlet
| (noweb) file:
This looks OK to me. Tim?
-- Gaby
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/l
> The filter from the FAQ does not work. I had to use:
>
> noweave -filter 'sed "/[EMAIL PROTECTED] /s/_/_/g;/[EMAIL PROTECTED]
> /s/_/_/g"'
>
> (apstrophes inside filter interacted with quoting inside noweave).
Urk! At some point I must have changed noweave without changing the
On October 22, 2006 9:30 PM Waldek Hebisch wrote:
> ...
> Inspired by noweb FAQ in am testing the following patch --
> tohether with previous patch it allowed me to run 'make dvi'
> with only two problems (Rosetta.pamphlet and more-rules.mk).
> 'more-rules.mk' is build only during main build, so f
Waldek Hebisch <[EMAIL PROTECTED]> writes:
| The filter from the FAQ does not work. I had to use:
|
| noweave -filter 'sed "/[EMAIL PROTECTED] /s/_/_/g;/[EMAIL PROTECTED]
/s/_/_/g"'
|
| (apstrophes inside filter interacted with quoting inside noweave).
I'm in the process of "trimming o
Gabriel Dos Reis wrote:
> Waldek Hebisch <[EMAIL PROTECTED]> writes:
>
> | There are more problems: apparently noweb can not correctly handle
> | files which have underscores in their names. For example latex run
> | on src/hyper/parse_aux.tex gives the following errors (I removed
> | other messag
"Bill Page" <[EMAIL PROTECTED]> writes:
[...]
| Shows that Gaby made the change to include the underscore _
| on 2006-09-18.
Yes, that is correct.
-- Gaby
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/li
Bill Page wrote:
> Thanks, Norman. I think we figured it out. There is really no
> mangling - just an "innocent" change with unexpected behaviour.
> Your FAQ is very useful:
>
> http://www.eecs.harvard.edu/nr/noweb/FAQ.html
>
> Q. How do I get an output file (root chunk) with an underscore
> in
"Bill Page" <[EMAIL PROTECTED]> writes:
| Could this be a LOCALE/LANG issue?
No. It is an issue on build-improvements while back when I made a
uniform rule to extracting the C files from the pamphlets.
| Or is this behaviour specific
| to the version of noweb distributed by Debian?
No, it is a
"Bill Page" <[EMAIL PROTECTED]> writes:
| On October 22, 2006 9:39 AM Waldek Hebisch wrote:
| > > Waldek Hebisch <[EMAIL PROTECTED]> writes:
| > >
| > > | ii nowebm 2.10c-3.3 A WEB-like
| > > | literate-programming tool
| > >
| > ...
| > There are more problems: apparently no
Waldek Hebisch <[EMAIL PROTECTED]> writes:
| There are more problems: apparently noweb can not correctly handle
| files which have underscores in their names. For example latex run
| on src/hyper/parse_aux.tex gives the following errors (I removed
| other messages which are caused by the two error
root <[EMAIL PROTECTED]> writes:
[...]
| the essense of literate programming can be done without noweb.
I'm glad to hear that; because it was not obvious to me people agreed
when I suggested similar ideas in different terms some months ago.
-- Gaby
___
--Original Message-
> From: Norman Ramsey [mailto:[EMAIL PROTECTED]
> Sent: October 22, 2006 6:38 PM
> To: Bill Page
> Cc: axiom-developer@nongnu.org; '[EMAIL PROTECTED];
> [EMAIL PROTECTED]; 'Reis''; 'Waldek Hebisch'
> Subject: Re: [Axiom-d
> > -Original Message-
> > From: Waldek Hebisch [mailto:[EMAIL PROTECTED]
> > Sent: October 22, 2006 11:01 AM
> > To: Bill Page
> > Cc: axiom-developer@nongnu.org; 'Waldek Hebisch';
> > '[EMAIL PROTECTED]; [EMAIL PROTEC
On 10/22/2006 07:31 PM, root wrote:
Although noweb implements three of four features I don't see it as a
requirement. Indeed there has been discussion of other formats such as
...
* latex macro forms which replace the <<>> syntax with
\begin{chunk}{chunkname}, not yet public.
Can
On October 22, 2006 2:10 PM Waldek Hebisch wrote:
> ...
> Correction: both verion of noweb give the same result. The real
> reason is that parse_aux.pamphlet in build-improvements is modified:
>
> --- ../../silver/axiom/src/hyper/parse_aux.pamphlet
> 2006-10-20 23:54:15.0 +0200
> +++
to:[EMAIL PROTECTED]
> > Subject: Re: [Axiom-developer] build-improvements and latex
> >
> >
> > Bill Page wrote:
> > > On October 22, 2006 9:39 AM Waldek Hebisch wrote:
> > > >
> > > > For example latex run on src/hyper/parse_aux.tex gives th
> > Although noweb implements three of four features I don't see it as a
> > requirement. Indeed there has been discussion of other formats such as
> ...
> > * latex macro forms which replace the <<>> syntax with
> > \begin{chunk}{chunkname}, not yet public.
>
> Can one infer that th
root <[EMAIL PROTECTED]> writes:
...
> Although noweb implements three of four features I don't see it as a
> requirement. Indeed there has been discussion of other formats such as
...
> * latex macro forms which replace the <<>> syntax with
> \begin{chunk}{chunkname}, not yet public
AM
> To: Bill Page
> Cc: axiom-developer@nongnu.org; 'Waldek Hebisch';
> '[EMAIL PROTECTED]; [EMAIL PROTECTED]; Reis'
> Subject: Re: [Axiom-developer] build-improvements and latex
>
>
> Bill Page wrote:
> > On October 22, 2006 9:39 AM Wa
On October 22, 2006 9:15 AM Ralf Hemmecke wrote:
> Tim Daly wrote:
> > So if straight latex is the base case of a valid literate
> > pamphlet file (since it contains 0 lines of code) then we
> > have a working definition.
>
> Cool, I have never read this somewhere before. ;-)
>
Yes, one might h
1 - 100 of 131 matches
Mail list logo
