"Bill Page" <[EMAIL PROTECTED]> writes:
| Gaby,
|
| On August 13, 2006 10:24 AM you wrote:
| >
| > M. Edward (Ed) Borasky writes:
| > [...]
| >
| > | 3. If you have GCL installed, does Axiom still build its
| > |own copy, or does it know about the installed version?
| >
| > You can convin
Camm,
When you have a moment could you please confirm that I am not
leading Gaby astray here. :-)
Thanks.
On August 12, 2006 10:34 PM Gaby wrote:
>
> "Bill Page" <[EMAIL PROTECTED]> writes:
>
> | On August 12, 2006 8:56 PM Gaby wrote:
> | > ...
> | > There are still some patches against GCL t
Gaby,
On August 13, 2006 10:24 AM you wrote:
>
> M. Edward (Ed) Borasky writes:
> [...]
>
> | 3. If you have GCL installed, does Axiom still build its
> |own copy, or does it know about the installed version?
>
> You can convince Axiom to use the installed GCL by defining the
> variable GC
On August 14, 2006 3:04 PM William Sit wrote:
> ...
> BTW, there is an error in [SandBoxNewAutodocPamphlet]:
>
> Traceback (most recent call last): File
> "/var/zope/Products/ZWiki/plugins/Fit.py", line 29, in ? from
> fit.Parse
> import Parse ImportError: No module named fit.Parse
>
> The file
Ralf Hemmecke wrote:
>
> > As Bill, I think hard-coded modification date is preferable, as it
> > allows minor modification (e.g. fixing typo). Of course, it depends on
> > the semantics you espect on the date.
>
> I also vote for hardcoded version or date information in a file. If you
> take t
Le lundi 14 août 2006 à 23:32 +0200, Vanuxem Grégory a écrit :
> Hello,
>
>
> Hypertex does not work for me with the last version of axiom (gold)
> checked out from cvs at Savannah. I have just a white window with two
> buttons (exit and help) that do not work.
I forgot to say that I do not use
Hello,
Hypertex does not work for me with the last version of axiom (gold)
checked out from cvs at Savannah. I have just a white window with two
buttons (exit and help) that do not work. Here is the output:
===
syntax error: expecte
David MENTRE <[EMAIL PROTECTED]> writes:
| Hello,
|
| Ok, so why not modifiying 'document' itself, like in:
Really, I don't believe the issue is that of "gaby mode".
document is doing too many things at the same time.
There was a comparison with tar earlier. However, tar does many
things at t
As Bill, I think hard-coded modification date is preferable, as it
allows minor modification (e.g. fixing typo). Of course, it depends on
the semantics you espect on the date.
I also vote for hardcoded version or date information in a file. If you
take the modification time of the file, it migh
Hello,
Ok, so why not modifiying 'document' itself, like in:
--start document--
#!/bin/sh
REDIRECT=""
FILE=""
gaby_mode=no
while : ; do
case "$1" in
"") break;;
-o)
REDIRECT=$2; shift;;
-gaby-mode)
gaby_mode=yes;;
*)
FILE=
root <[EMAIL PROTECTED]> writes:
| > As you can see, document insists on LaTeXing a file, which, as I said,
| > when in a design-code-build-test mode, I'm not interested in. It just
| > wastes my time. I rather have a separate [hase for building .dvi
| > files than trying to conflate everything
> As you can see, document insists on LaTeXing a file, which, as I said,
> when in a design-code-build-test mode, I'm not interested in. It just
> wastes my time. I rather have a separate [hase for building .dvi
> files than trying to conflate everything together. Maybe that mode
> will be only
root <[EMAIL PROTECTED]> writes:
| > It stands in my way for having a more structured build system.
| >
| > When in the cyle design-code-build-test; I don't need all those dvi
| > that document insist on building. I have configure generate my
| > Makefiles, but document want to generate its own.
Hello,
As Bill, I think hard-coded modification date is preferable, as it
allows minor modification (e.g. fixing typo). Of course, it depends on
the semantics you espect on the date.
William Sit <[EMAIL PROTECTED]> writes:
> Come to think of it, each pamphlet file should include a revision
> his
Bill Page wrote:
>
> On August 14, 2006 2:13 AM William Sit wrote:
> >
> > When a pamphlet file is rendered, the date of the pdf file is always
> > \today. That seems to be misleading, as many of the source files have
> > not been updated for ages.
>
> I think the use of \today in the LaTeX sou
root <[EMAIL PROTECTED]> writes:
[...]
| > | The guiding principle in this case is that
| > |
| > | Axiom never writes outside its own directory
| >
| > This *is simply untrue*, at least if you build Axiom+GCL.
|
| it is untrue?
Yes, GCL's configure redirects to /dev/null.
Frankly, the Au
> It stands in my way for having a more structured build system.
>
> When in the cyle design-code-build-test; I don't need all those dvi
> that document insist on building. I have configure generate my
> Makefiles, but document want to generate its own.
>
> document was a necessary step to get A
Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
[...]
| I have a private script for automatically building Axiom; do you think
| there is a was to set up a cron job on those systems?
I found answer to my question. It is "yes".
Thanks!
-- Gaby
___
Axi
[snip]
> | It's not a question of theology or flavors (or flavours).
>
> I'm sorry to say, but a principle followed blinded without taking into
> account reality is theology.
>
> [...]
>
> | If you state a principle there is nothing else to explain.
>
> That *is* theology.
ok. if you
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| > | > The 'document' script is intended to centralize all of the information
| > | > necessary to extract information from a file in various ways within the
| > | > axiom system. It is ultimately intended to support the drag-and-drop
| > | > feature I'm
Alfredo Portes [EMAIL PROTECTED] wrote:
> >I can understand Gaby. For working offline it would be good to have the
> >wiki locally and have it updated like any SCM repository. But it seems
> >that cannot be easily achieved, because at least one needs to set up
> >Zope, Zwiki, latexwiki, mathaction
"Bill Page" <[EMAIL PROTECTED]> writes:
| On August 14, 2006 11:37 AM Gabriel Dos Reis wrote:
| >
| > root <[EMAIL PROTECTED]> writes:
| >
| > | Gaby,
| > |
| > | I'd suggest testing your configure scripts on both the MAC
| > and FreeBSD,
| >
| > I don't have access to a MAC of a freebsd, tha
> Oh, another person who does not like "document" very much...
'document' is a script intended to collect the usual document handling
functions which standard options. i put it there so i can use it to
build files during make and later to build files during development.
it's unlikely that you woul
I can understand Gaby. For working offline it would be good to have thewiki locally and have it updated like any SCM repository. But it seems
that cannot be easily achieved, because at least one needs to set upZope, Zwiki, latexwiki, mathaction on the local computer. That is hard enough. The inst
root <[EMAIL PROTECTED]> writes:
| > | > > I disagree with the idea that writing to /dev/null should be banned.
| > | >
| > | > But isn't /dev/null quite Unix-specific? It basically means that in
| > | > order to build Axiom one must have a Unix-like environment. Not that I
| > | > want to make
The Makefile principles are also in Makefile.pamphlet, near line 157.
The restriction about not writing outside the source tree is on line 202.
t
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom
The SRC/INT/OBJ/MNT principles are in README (near line 416)
The Makefile principles are in Makefile.pamphlet, first paragraph
t
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer
| > The 'document' script is intended to centralize all of the information
| > necessary to extract information from a file in various ways within the
| > axiom system. It is ultimately intended to support the drag-and-drop
| > feature I'm working on as well as a )compile command in Axiom. Many
|
It's not a question of theology or flavors (or flavours). The issue
again comes back to basic, easily stated, easily learned, universally
followed principles. In Axiom
all files are literate.
all directories have Makefiles that handle their subtrees.
all Makefiles have a stanza per fi
| > Can we just have the documentations as part of the SVN
| > repository?
SVN is a source code repository. The wiki is a web site with
dynamic content, e.g. the results of Axiom calculations, and
the status of issue reports etc. So I think the answer to your
question is: No.
I can understand
On August 14, 2006 11:37 AM Gabriel Dos Reis wrote:
>
> root <[EMAIL PROTECTED]> writes:
>
> | Gaby,
> |
> | I'd suggest testing your configure scripts on both the MAC
> and FreeBSD,
>
> I don't have access to a MAC of a freebsd, thay is why I repeatedly
> call for testing and feedback. If yo
On August 14, 2006 11:34 AM Gaby wrote:
> ...
> | >
> | > Can we just have the documentations as part of the SVN
> | > repository?
> | >
> |
> "Bill Page" <[EMAIL PROTECTED]> writes:
> | ??? What "documentations" are you talking about?
>
> The one we currently have as wiki.
>
Your question,
> | > > I disagree with the idea that writing to /dev/null should be banned.
> | >
> | > But isn't /dev/null quite Unix-specific? It basically means that in
> | > order to build Axiom one must have a Unix-like environment. Not that I
> | > want to make the build process more complicated, but I a
root <[EMAIL PROTECTED]> writes:
| Gaby,
|
| I'd suggest testing your configure scripts on both the MAC and FreeBSD,
I don't have access to a MAC of a freebsd, thay is why I repeatedly
call for testing and feedback. If you have problems, please send me
the logs so that I can look into the probl
"Bill Page" <[EMAIL PROTECTED]> writes:
| On August 13, 2006 11:03 PM Gaby wrote:
| >
| > Bill Page writes:
| >
| > [...]
| >
| > | Mostly I would conclude from this excersize that simply building
| > | a wiki (however sexy or easy to use) and hoping that people will
| > | simply show up to cre
root <[EMAIL PROTECTED]> writes:
| > > I disagree with the idea that writing to /dev/null should be banned.
| >
| > But isn't /dev/null quite Unix-specific? It basically means that in
| > order to build Axiom one must have a Unix-like environment. Not that I
| > want to make the build process m
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| > The 'document' script is intended to centralize all of the information
| > necessary to extract information from a file in various ways within the
| > axiom system. It is ultimately intended to support the drag-and-drop
| > feature I'm working on as we
root <[EMAIL PROTECTED]> writes:
[...]
| Frankly I can't figure out why the Makefiles are so hard to learn.
I don't think Makefiles in general are that very hard. Just like one
may write very twisted spaghetti codes in higher level programming
languages, one can write hard to understand Makefil
root <[EMAIL PROTECTED]> writes:
[...]
| In general, it is very difficult to coordinate multiple developers
| working in parallel using their own working methods. It is unlikely
| that we will all use the same techniques.
That is true. However, to make sure we don't end up in a bizarre
situatio
root <[EMAIL PROTECTED]> writes:
| > > Another alternative that I have been thinking about is only
| > > supporting a "diff and patch" interface for the online wiki version
| > > of the source and documentation.
| >
| > Maybe some people like diff and patch, I don't. I am not a computer and
| >
On August 14, 2006 2:13 AM William Sit wrote:
>
> When a pamphlet file is rendered, the date of the pdf file is always
> \today. That seems to be misleading, as many of the source files have
> not been updated for ages.
I think the use of \today in the LaTeX source is inappropriate unless
for som
On August 14, 2006 3:35 AM William Sit wrote:
>
> I updated http://Zwiki.org/NewAutodocPamphlet to use hyperref package
> and everything works fine there.
>
Nice. I would still like to know why LaTeX does strange things to
< and > in the raw.
> I then tried to copy it to [SandBox NewAutodocPamp
On August 14, 2006 4:55 AM William Stein wrote:
Hello,
SAGE Days 2 will take place October 6-10, 2006.
Come and work very hard to build, using the best open source tools
available, what I hope will soon be the finest general purpose
mathematics software available:
http://modular.math.wash
The 'document' script is intended to centralize all of the information
necessary to extract information from a file in various ways within the
axiom system. It is ultimately intended to support the drag-and-drop
feature I'm working on as well as a )compile command in Axiom. Many
(but not all) of t
On 08/14/2006 04:38 AM, root wrote:
I strongly believe that axiom--main--1 should be a "testing" branch and
things from their should only enter the silver/trunk if they do not
break anything serious. Note that silver/trunk is supposed to become Gold.
I could be mistaken or confused. Are you su
http://zwiki.org/NewAutodocPamphlet
I am not a lisp programmer at all, but the lisp code is missing ">>" so
I guess, a line like
Why don't people use http://wiki.axiom-developer.org/FAQ for that?
Who would look for a file called PROCON?
Ralf
On 08/14/2006 03:41 AM, root wrote:
sigh.
noweb, configure, GCL, latex, svn, arch, darcs, etc
i think we need to create a new top level file called "PROCON"
which contains a pa
Bill:
I updated http://Zwiki.org/NewAutodocPamphlet to use hyperref package
and everything works fine there.
I then tried to copy it to [SandBox NewAutodocPamphlet] and parent it
under [SandBoxPamphlet]. I get some problems when previewing.
Most of these were temporarily solved by avoiding any "h
So the solution to the spam problem that I like most right now is
to embed the existing Axiom Wiki site inside Plone and use the
standard Wiki skin to keep the same look and feel
I think this is definitely worth a try. If you're being targetted by
persistent spammers I too think that requiring
49 matches
Mail list logo
