I can tell you I would rather maintain the four lines of C++ without
the largely useless commentary.
That's a simple AXIOM program, but I'm sure one can easily translate it
into any programming language.
foo(a: Integer, b: Integer): Integer ==
if a 0 then
if a b then return
...
And... the problem is be no means specific to AXIOM.
foo(a: Integer, b: Integer): Integer ==
if a 0 then
if a b then return foo(b,a)
return foo(b-a,a)
return b
Question: Does the program have a bug?
I think that your question is related to the fact that if we
When you are happy with your vim file send me a copy and
I will add it to the zips directory in the distribution.
Tim,
I uploaded the latest version and I don't think I will modify it again,
unless some error is pointed out or some nice improvement is made or
suggested.
Inside there are two
Fabio,
Uploaded to where?
To vim.org:
http://www.vim.org/scripts/script.php?script_id=4765
Fabio
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
https://lists.nongnu.org/mailman/listinfo/axiom-developer
Please check if it works also for you.
I'll do that later.
But it seems that I'm not completely satisfied.
I had to separate axiom commands and axiom operations because the
output, in these cases, has a different layout. Moreover, with the
while+for cycle there was some little trouble, so I
Fabio,
Note that if you search for category, domain, and package names
using the Axiom interpreter it will not show all of the names.
For instance, AlgebraicFunction is hidden (see the variable
$globalExposureGroupAlist on line 24164 of books/bookvol5.pamphlet).
Directly grepping the books will
Please check if it works also for you.
Wait. I realized that you have removed the \ and \ markers. Why?
Becuase I changed syntax rules of matching: for elements which are made up
only of keywords (that is, character in 48-57,_,a-z,A-Z,,!,? ) then I
declare something like
syn keyword
Meanwhile, I've only removed redundant spaces and remove -nosman after
AXIOMsys. That is ignored in this place anyway.
I ran the script and it works as before.
Please let's further develop via github. I don't like so much sending
files around.
https://github.com/hemmecke/vim-panaxiom
ok,
Please let's further develop via github. I don't like so much sending
files around.
https://github.com/hemmecke/vim-panaxiom
Ralf,
I added the last changes I made.
In particular, I changed colors definition so that it is modular and it
can be very easy for the user to customize them, or even
What about the attached script?
It's developed with FriCAS, but would that work with AXIOM?
For simplicity, instead of axDomain, my script outputs axdomains.
That's easily fixable by introducing a third parameter to the keywords
shell function.
Ralph, thanks for the script.
If I got it right,
Tim, thanks for your comments and hints.
If you want the names of all of the categories, domains, and packages
(assuming you have axiom in a directory called axiom):
cd ~/axiom/books
fgrep abbrev bookvol10.2.pamphlet
fgrep abbrev bookvol10.3.pamphlet
fgrep abbrev bookvol10.4.pamphlet
fgrep
Ralph
I still prefer correct spelling.
Oooops! Sorry...
Just replace the keywords function by:
keywords () {
echo )what $1 | $EXE $1.vim
}
And send my the 4 files.
They are all the same and they read
Unknown option: -nosman
To use a specific workspace use, e.g.: spad -ws -nosman
fgrep abbrev bookvol10.2.pamphlet
fgrep abbrev bookvol10.3.pamphlet
fgrep abbrev bookvol10.4.pamphlet
fgrep abbrev bookvol10.5.pamphlet
10.2 is all the categories, 10.3 is all the domains,
10.4 is almost all the packages, 10.5 is the new numeric packages.
...
You might want to look at the
Unknown option: -nosman
To use a specific workspace use, e.g.: spad -ws -nosman
Goodbye.
That's a funny and useless error message. ;-) But why does it say spad?
Well. Try the direct call to AXIOMsys as I've showed you in my last
mail. You probably must set the AXIOM variable right.
Wooow!
Ralf, I got it work.
Please check if it works also for you.
I had to separate axiom commands and axiom operations because the output,
in these cases, has a different layout. Moreover, with the while+for cycle
there was some little trouble, so I changed it to pure sed (and one per
line: a
1) Are curly brackets ever used in axiom syntax?
It seems to me they are not and they have no meaning in axiom: if it is
so, I can remove them from sanity check, simplifying things.
I don't believe they have any meaning.
Ok, I will remove them from the sanity check
2) If I give the command
I didn't know of this file: after I asked on the list and I made the
first version of my file in 2004, I didn't look around anymore for a
syntax file. Last month I was writing a small input file in pamphlet
format and I was upset to not having syntax highlight for axiom code in
the chunk
I have only one remark: I used axiom to generate
categories/domains/packages/operators names. Are them exactly the same
in fricas? I don't know this. From this point of view, maybe they can't
be completely interchangeable.
If I were you, I would simply write a little script that a user could
Umm, maybe I don’t get what you did but there was a vim syntax highlighting
file http://axiom-wiki.newsynthesis.org/AxiomInVim
I didn't know of this file: after I asked on the list and I made the first
version of my file in 2004, I didn't look around anymore for a syntax
file. Last month I
Some time ago I asked on the list if there was a syntax file to have vim
input files highlighted in vim: the answer was no.
After some time, I built one myself.
Unlikely, I forgot to submit it so to share it with other interested
people (if any...!)
I did it today: interested people can
If I recall a previous command line via the up arrow and then I edit it,
the line will usually be messed up.
If I start axiom with -nox it works fine but I will lose the tab
completion.
Is there a way to have both features or do I need to choose which one is
more useful to me?
Thanks
The problem with having Axiom automatically perform a irreducibility
check is that the check could be time consuming. Suppose you have a
polynomial of high degree whose factorization takes, say, a couple of
minutes. With an automatic irreducibility test, AXIOM would factor the
polynomial
I realized that when constructing finite fields providing a user choosen
polynomial, Axiom doesn't check whether the used polynomial is
irreducible or not.
For example:
(10) - factor(x^8+x^4+x^2+x+1::PF 2)
(10) -
43 432
(10) (x + x + 1)(x + x + x + x +
Maybe I solved my problem.
At least, I have found the cause, but not the reason.
I said that I created a new ubuntu box: it compiled there.
So the problem was in my settings.
I created a new user on my (real) machine: on the new user, it compiled.
So the problem was in my _user_ settings.
I
First of all, thanks for having isolated the question in a new thread.
Moreover, let me also say that my question arises from the fact that
during some computations axiom aborts, after some hours, with the
following error message
--
(150) -
System error:
The storage for
I built ubuntu on a 64 bit machine and then did
git clone http://github.com/daly/axiom.git
cd axiom
export AXIOM=`pwd`/mnt/ubuntu
export PATH=$AXIOM/bin:$PATH
make
and it builds properly here.
I tried exactly the same as you, but the result doesn't change.
The logs are here, if they can
Can you rerun the make as root?
Sure I can.
And I am doing it.
It is compiling and up to now, without errors.
It already passed the critical point.
Meanwhile, in another shell I started a compilation as normal user and it
already stopped at the usual point.
As soon as the root shell will
user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
This as user. As root it is the same.
what are your ulimit settings?
ulimit -a
Fabio S. wrote:
Can you rerun the make as root?
Sure I can.
And I am doing
Can you rerun the make as root?
Compilation ended. It seems ok. At least, I have the binary...
Here is the log
http://dl.dropbox.com/u/7972796/make-root.log
I am also making another test: I created a new ubuntu box in virtualbox
and I didn't touch anything, just the minimum for compiling. I
Tim,
the output of
make NOISE=
is quite long, of course. The last part in the screen is:
---
Overfull \hbox (4.50002pt too wide) detected at line 8232
\OT1/cmr/m/n/10 1183
Overfull \hbox (4.50002pt too wide) detected at line
make NOISE=
is quite long, of course. The last part in the screen is:
Maybe you should try
make NOISE= fabio.log
and upload that file somewhere.
I uploaded it to Dropbox.
Here are the results:
the file make.log
http://dl.dropbox.com/u/7972796/make.log
is the result of a plain make.
compilation, I will check for the environment variable as soon
as I am back in the office (later or tomorrow morning).
Fabio
No, the problem isn't ram. I have seen this problem
before but it is my memory that is failing. I'll look
at it shortly.
Fabio S. wrote:
Tim,
the output of
make NOISE
Fabio,
type
echo $AXIOM
and let me know what your AXIOM shell variable is.
It appears that it might not be set correctly.
It should be
export AXIOM=/home/stumbo/download/axiom/mnt/ubuntu
If you set it to that value and then do
make clean
make
it should build. The makefile knows where the build
ok. I'll try a build from those sources again.
Perhaps I made a mistake somewhere.
Did you say you had a 64 bit system?
Yes.
Thanks a lot.
Fabio
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
Sorry to annoy, but I can't succeed in compiling axiom.
I am trying to do it on an ubuntu64 10.04 system. I followed all
instructions on the download page, namely:
echo 0 /proc/sys/kernel/randomize_va_space
apt-get install m4 libxpm-dev libxt-dev x-dev libx11-dev
apt-get install libxext-dev
axiom.sty should be placed last in the include list.
axiom.sty uses \providecommand which will define the macro only
if it does not already exist so it will not cause redefinition conflicts.
You are right. Many thanks and please forgive me for a try that I should
have done before posting. I
I have a (small) problem with axiom.sty: I am writing a pamphlet file
considering it a as tex file, using the chunck enviroment.
For this, of course, I use the package axiom.sty.
Everything works right, with the only minor problem that when I use also
the amsmath package there are two new
System error:
The storage for VECTOR is exhausted.
Currently, 10765 pages are allocated.
Use ALLOCATE to expand the space.
protected-symbol-warn called with (NIL)
Question: How exactly do I issue an ALLOCATE command? Also,
it is possible (if so, how) to continue the computation
after an
Well, I've been running your code for about 6 hours or so on
the fastest machine I have and also on an Ubuntu machine.
Neither one has completed so far but they continue to compute.
As to the complete system crash my best guess is that your system
has thermal checked, i.e., overheated and thus
First, let me thank all of you for your support: I will use all the hints
in my next computations.
Effectively, I didn't think to do computations modulo a prime, even if it
is a common trick.
Neither I thought about changing the domain where computing the groebner
basis, but this is due to
I just installed the latest silver version from
http://www.axiom-developer.org/axiom-website/download.html
on my ubuntu system and I tried to do some computation.
While axiom was working, after maybe 10-20 minutes, the
system crashed (very) badly, like just unplugging the power.
The same
I just installed the latest silver version from
http://www.axiom-developer.org/axiom-website/download.html
on my ubuntu system and I tried to do some computation.
While axiom was working, after maybe 10-20 minutes, the
system crashed (very) badly, like just unplugging the power.
The same
42 matches
Mail list logo
