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
"Page, Bill" <[EMAIL PROTECTED]> writes:
| Axiom Developers;
|
| Over a year ago we were discussing how best to represent Axiom's
| algebra dependency graph. This is a complex problem because Axiom
| has over 1,300 mathematically modules that are tightly integrated
| with each other - even to the
> Does somebody know what happens here?
>
> Ralf
>
> )expose PrimitiveElement
> primitiveElement([x^2-2,x^2-3]$List(Polynomial Fraction Integer),[z2,z3])
>
> >> Error detected within library code:
> (1 . failed) cannot be coerced to mode (OrderedVariableList (z2 z3 %A))
>
>
AFAICS x^2
Axiom Developers;
Over a year ago we were discussing how best to represent Axiom's
algebra dependency graph. This is a complex problem because Axiom
has over 1,300 mathematically modules that are tightly integrated
with each other - even to the point of generating a large number
cyclical dependenc
> Hi Waldek,
>
> Thanks for your reponse.
> It is my purpose.
>
> My main idea is to get expand (cos (2*x)) working as expand (cos (x+y)).
>
> Do you know if it's possible or must I write my own package ?
>
So, you want expand (cos (2*x)) giving you:
2 2
- sin(x) +
> 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
On Wednesday, November 08, 2006 3:30 PM Tim Daly wrote:
>
> Latex should now be on the compile farm machines --t
>
> ...
>
> Comment By: Robert Liesenfeld (xunil)
> Date: 2006-11-08 20:26
>
> Message:
> Logged In: YES
> user_id=1054
>
> This should be installed on most of the compile farm
> mac
Latex should now be on the compile farm machines --t
--- Start of forwarded message ---
To: [EMAIL PROTECTED]
From: "SourceForge.net" <[EMAIL PROTECTED]>
Subject: [ alexandria-Support Requests-1551244 ] Latex on Compile Farm
Content-Type: text/plain; charset="UTF-8"
X-SourceForge-Tracker-
Waldek Hebisch wrote:
Many systems (Linux, BSD and supposedly also Mac OS X) provide 'openpty'
function as a preferred method to open a pty (for example on Linux
+#ifdef HAVE_OPENPTY
+#include
+#endif
On Mac OS X 10.4 using XCode 2.2 I need to #include instead.
--
Humberto Ortiz-Zuazaga
P
"Page, Bill" <[EMAIL PROTECTED]> writes:
[...]
| Maybe we will have to seriously consider cross-compilation
| afterall. :-)
He? You went into great details explaining to skeptical Gaby that was
not a good idea ;-/
-- Gaby
___
Axiom-developer mailin
Axiom Developers,
Well, here's our next target for Axiom build-improvements:
http://www.flypentop.com/view/page.home/home?s=algebra
Maybe we will have to seriously consider cross-compilation
afterall. :-)
Regards,
Bill Page.
PS. I want one for Christmas!
_
"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
Waldek Hebisch <[EMAIL PROTECTED]> writes:
| Richard Harke wrote:
| > I'm attempting to build the build-improvements branch on linux-ia64
| > build stops with message
| > Exactly one loader option must be chosen: dlopen=yes statsysbfd=no
| >dynsysbfd=no locbfd=yes custreloc=no
| >
| > I h
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
Richard Harke wrote:
> On Tue November 7 2006 23:05, billpage wrote:
> > Changes http://wiki.axiom-developer.org/AxiomDeveloperFAQ/diff
>
> > ===
> > FAQ 1: Xlib.h is not found
> > =
Richard Harke wrote:
> I'm attempting to build the build-improvements branch on linux-ia64
> build stops with message
> Exactly one loader option must be chosen: dlopen=yes statsysbfd=no
>dynsysbfd=no locbfd=yes custreloc=no
>
> I have only a vague idea of what these mean and no idea how t
"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 Wednesday, November 08, 2006 4:52 AM Richard Harke wrote:
>
> I'm attempting to build the build-improvements branch on linux-ia64
> build stops with message
> Exactly one loader option must be chosen: dlopen=yes statsysbfd=no
>dynsysbfd=no locbfd=yes custreloc=no
>
> I have only a vagu
> Waldek Hebisch <[EMAIL PROTECTED]> writes:
>
> | I wrote that there are three problem latexing build improvement
> | but in fact there are more. Namely, Makefile mark .dvi files
> | as .PRECIOUS so that even if Latex fails, garbled .dvi lies on
> | disk and is used (skipping Latex run) on the n
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
> On Tuesday, November 07, 2006 4:24 PM Waldek Hebisch wrote:
>
> > ...
> > I propose: rename capital Greek letters according to
> > Bill Page proposal. Adjust 'util.ht' to match (all other
> > hypertex pages should access Greek letters only via macros
> > defined in 'util.ht').
> > Next, remo
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
I'm attempting to build the build-improvements branch on linux-ia64
build stops with message
Exactly one loader option must be chosen: dlopen=yes statsysbfd=no
dynsysbfd=no locbfd=yes custreloc=no
I have only a vague idea of what these mean and no idea how to make the
choice into the build
On Tue November 7 2006 23:05, billpage wrote:
> Changes http://wiki.axiom-developer.org/AxiomDeveloperFAQ/diff
> ===
> FAQ 1: Xlib.h is not found
> ===
>
> You need to ha
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
64 matches
Mail list logo
