[Axiom-developer] Re: Axiom on Windows
On Tue, 2011-02-01 at 17:08 -0500, daly wrote: Jeffrey, One of the problems is that Axiom has been forked into FriCAS and Open-Axiom but those versions have not properly specialized the files. This will result in damage to an Axiom installation. I see from your shell variables that Open-Axiom seems to be the last installed version. Tim Daly On Tue, 2011-02-01 at 16:05 -0500, axiom-developer-ow...@nongnu.org wrote: As list administrator, your authorization is requested for the following mailing list posting: List:Axiom-developer@nongnu.org From:k...@kenevans.net Subject: Axiom on Windows Reason: Post by non-member to a members-only list At your convenience, visit: http://lists.nongnu.org/mailman/admindb/axiom-developer to approve or deny the request. email message attachment Forwarded Message From: Kenneth Evans k...@kenevans.net To: axiom-developer@nongnu.org Subject: Axiom on Windows Date: Tue, 01 Feb 2011 14:44:51 -0600 Hi I am new to Axiom and am trying to use it on Windows 7, 64-bit. (I am experienced with Mathematica but have never previously used Axiom.) Most of the bits and pieces to make this work appear to be out there, but are not very well documented or easy to find. Clearly, several people have taken the time to make installers, etc. Surely someone is actually using it successfully on Windows. I myself have it working to some extent. This is what I did: Downloaded: http://axiom-wiki.newsynthesis.org/AxiomBinaries axiom-windows-0.1.4.exe http://sourceforge.net/projects/open-axiom/files/ open-axiom-1.3.0-windows-i386.exe http://axiom-wiki.newsynthesis.org/FriCASBinaries Fricas-Rev.263.exe I installed them in the order OpenAxiom, FriCAS, Axiom (not having much information on which of the three to use). They all installed and made desktop shortcuts. The ones for OpenAxiom and Axiom, more or less worked from the shortcuts with the command-line interface. The one for FriCas failed with a socket error (can't open socket listing file). They all put their paths in PATH, which could possibly be a problem. I uninstalled FriCAS. The others I installed and reinstalled as I found one did some things right and the other other things right. Currently they are both installed with Axiom first in the PATH. I got the QT windows version of TeXmacs. http://axiom-wiki.newsynthesis.org/TeXmacs texmacs-installer.exe I got it running. It is apparently set up for Axiom. I cloned the axiom plug-in and made it work for OpenAxiom using snippets of information gleaned via the web. So I can now run both as sessions in TeXmacs. Axiom works better for me. I can, in fact, do a lot of what Axiom as a CAS is supposed to do. The main problem with TeXmacs is that when it is covered by another window, clicking on the title bar causes it to maximize, rather than just coming on top -- very annoying. The main problem I have right now with the CAS is that I cannot get it to read .axiom.input. I would like to do this to, at a minimum, set my working directory to My Documents/Axiom where I expect to keep my .input files. This is what happens (with Axiom in the command-line interface to keep it simple): 1. )cd doesn't work (1) - )cd System error: Cannot get the truename of #p~/. protected-symbol-warn called with (NIL) (1) - Using )system ls, I can see that I am in My Documents, actually c:\Users\evans\Documents. I would guess Axiom didn't do this as it doesn't seem to know it (Axiom) is there. It is probably some kind of windows default. )cd Axiom doesn't work. In fact, nothing I have tried works except: )cd c:/Users/evans/Documents/Axiom Even after that )cd still doesn't work, but )read filename-without-path works. Before doing that )cd Axiom or ./Axiom didn't work. Is there some way to get around this? Note that $HOME is defined as c:\Users\evans\Documents. You would think it might try $HOME if ~ fails. 2. It does not read .axiom.input. I have tried putting it where it should be (c:\Users\evans) in My Documents and in other places. Does anyone know how to make it read .axiom.input. These are some things from the environment that might be applicable: HOME=c:\Users\evans HOMEDRIVE=C: HOMEPATH=\Users\evans LOCALAPPDATA=C:\Users\evans\AppData\Local OPENAXIOM=C:/Program Files (x86)/OpenAxiom/lib/open-axiom/i686-pc-mingw32/1.3.0 USERNAME=evans USERPROFILE=C:\Users\evans Thanks in advance for any help. -Ken ___ Axiom-developer mailing list Axiom-developer@nongnu.org
Re: [Axiom-developer] Re: Axiom on Windows
Hi, For Axiom: http://axiom-wiki.newsynthesis.org/AxiomBinaries axiom-windows-0.1.4.exe There is no native support for Axiom in Windows. Many of the issues you are reporting are because of this and not because of the other projects. So this file should probably be removed as it does not reflect the Axiom project at http://axiom-developer.org. I will remove it. For Axiom support in Windows you should follow: http://axiom-developer.org/axiom-website/download.html For Fricas: http://axiom-wiki.newsynthesis.org/FriCASBinaries Fricas-Rev.263.exe was an attempt to make an installer for Fricas, and it required to have an AXIOM variable. Note that this file was never distributed by the Fricas project and it was just something uploaded to the wiki in case people wanted to try it. There was no intention to harm other projects. The wiki page has now been updated. Proper support in Windows for Fricas is done by using Cygwin. http://fricas.sourceforge.net/download.html For OpenAxiom: OpenAxiom has the only current installer on Windows that I know of. OpenAxiom does not use the AXIOM variable since the project was started almost. I will make sure today that this is the case in the installer and it was not something left from the old plugin to texmacs. If that is the case I will fix this ASAP. Again these installers were not created by any of the projects and in no way it means you cannot have all 3 projects in your computer. On Tue, Feb 1, 2011 at 5:11 PM, daly d...@axiom-developer.org wrote: On Tue, 2011-02-01 at 17:08 -0500, daly wrote: Jeffrey, One of the problems is that Axiom has been forked into FriCAS and Open-Axiom but those versions have not properly specialized the files. This will result in damage to an Axiom installation. I see from your shell variables that Open-Axiom seems to be the last installed version. Tim Daly On Tue, 2011-02-01 at 16:05 -0500, axiom-developer-ow...@nongnu.org wrote: As list administrator, your authorization is requested for the following mailing list posting: List: Axiom-developer@nongnu.org From: k...@kenevans.net Subject: Axiom on Windows Reason: Post by non-member to a members-only list At your convenience, visit: http://lists.nongnu.org/mailman/admindb/axiom-developer to approve or deny the request. email message attachment Forwarded Message From: Kenneth Evans k...@kenevans.net To: axiom-developer@nongnu.org Subject: Axiom on Windows Date: Tue, 01 Feb 2011 14:44:51 -0600 Hi I am new to Axiom and am trying to use it on Windows 7, 64-bit. (I am experienced with Mathematica but have never previously used Axiom.) Most of the bits and pieces to make this work appear to be out there, but are not very well documented or easy to find. Clearly, several people have taken the time to make installers, etc. Surely someone is actually using it successfully on Windows. I myself have it working to some extent. This is what I did: Downloaded: http://axiom-wiki.newsynthesis.org/AxiomBinaries axiom-windows-0.1.4.exe http://sourceforge.net/projects/open-axiom/files/ open-axiom-1.3.0-windows-i386.exe http://axiom-wiki.newsynthesis.org/FriCASBinaries Fricas-Rev.263.exe I installed them in the order OpenAxiom, FriCAS, Axiom (not having much information on which of the three to use). They all installed and made desktop shortcuts. The ones for OpenAxiom and Axiom, more or less worked from the shortcuts with the command-line interface. The one for FriCas failed with a socket error (can't open socket listing file). They all put their paths in PATH, which could possibly be a problem. I uninstalled FriCAS. The others I installed and reinstalled as I found one did some things right and the other other things right. Currently they are both installed with Axiom first in the PATH. I got the QT windows version of TeXmacs. http://axiom-wiki.newsynthesis.org/TeXmacs texmacs-installer.exe I got it running. It is apparently set up for Axiom. I cloned the axiom plug-in and made it work for OpenAxiom using snippets of information gleaned via the web. So I can now run both as sessions in TeXmacs. Axiom works better for me. I can, in fact, do a lot of what Axiom as a CAS is supposed to do. The main problem with TeXmacs is that when it is covered by another window, clicking on the title bar causes it to maximize, rather than just coming on top -- very annoying. The main problem I have right now with the CAS is that I cannot get it to read .axiom.input. I would like to do this to, at a minimum, set my working directory to My Documents/Axiom where I expect to keep my .input files. This is what happens (with Axiom in the command-line interface to keep it simple): 1. )cd doesn't work (1) - )cd System error:
Re: [Axiom-developer] Re: Axiom on Windows
I just installed the OpenAxiom installer: http://sourceforge.net/projects/open-axiom/files/open-axiom-1.3.0-windows-i386.exe As I expected, there is no AXIOM variable being installed: (1) - )system %AXIOM% '%AXIOM%' is not recognized as an internal or external command, operable program or batch file. The commands not working for you: (1) - )cd The current OpenAxiom default directory is C:/OpenAxiom/bin/ (1) - )cd c:\temp The current OpenAxiom default directory is c:/temp/ I will try reading the input file later, as this is something I have not done before in Windows. Let me know if you have questions, and for problems with the installer you can report it in one of the OpenAxiom mailing lists: http://www.open-axiom.org/lists.html On Tue, Feb 1, 2011 at 5:11 PM, daly d...@axiom-developer.org wrote: On Tue, 2011-02-01 at 17:08 -0500, daly wrote: Jeffrey, One of the problems is that Axiom has been forked into FriCAS and Open-Axiom but those versions have not properly specialized the files. This will result in damage to an Axiom installation. I see from your shell variables that Open-Axiom seems to be the last installed version. Tim Daly On Tue, 2011-02-01 at 16:05 -0500, axiom-developer-ow...@nongnu.org wrote: As list administrator, your authorization is requested for the following mailing list posting: List: Axiom-developer@nongnu.org From: k...@kenevans.net Subject: Axiom on Windows Reason: Post by non-member to a members-only list At your convenience, visit: http://lists.nongnu.org/mailman/admindb/axiom-developer to approve or deny the request. email message attachment Forwarded Message From: Kenneth Evans k...@kenevans.net To: axiom-developer@nongnu.org Subject: Axiom on Windows Date: Tue, 01 Feb 2011 14:44:51 -0600 Hi I am new to Axiom and am trying to use it on Windows 7, 64-bit. (I am experienced with Mathematica but have never previously used Axiom.) Most of the bits and pieces to make this work appear to be out there, but are not very well documented or easy to find. Clearly, several people have taken the time to make installers, etc. Surely someone is actually using it successfully on Windows. I myself have it working to some extent. This is what I did: Downloaded: http://axiom-wiki.newsynthesis.org/AxiomBinaries axiom-windows-0.1.4.exe http://sourceforge.net/projects/open-axiom/files/ open-axiom-1.3.0-windows-i386.exe http://axiom-wiki.newsynthesis.org/FriCASBinaries Fricas-Rev.263.exe I installed them in the order OpenAxiom, FriCAS, Axiom (not having much information on which of the three to use). They all installed and made desktop shortcuts. The ones for OpenAxiom and Axiom, more or less worked from the shortcuts with the command-line interface. The one for FriCas failed with a socket error (can't open socket listing file). They all put their paths in PATH, which could possibly be a problem. I uninstalled FriCAS. The others I installed and reinstalled as I found one did some things right and the other other things right. Currently they are both installed with Axiom first in the PATH. I got the QT windows version of TeXmacs. http://axiom-wiki.newsynthesis.org/TeXmacs texmacs-installer.exe I got it running. It is apparently set up for Axiom. I cloned the axiom plug-in and made it work for OpenAxiom using snippets of information gleaned via the web. So I can now run both as sessions in TeXmacs. Axiom works better for me. I can, in fact, do a lot of what Axiom as a CAS is supposed to do. The main problem with TeXmacs is that when it is covered by another window, clicking on the title bar causes it to maximize, rather than just coming on top -- very annoying. The main problem I have right now with the CAS is that I cannot get it to read .axiom.input. I would like to do this to, at a minimum, set my working directory to My Documents/Axiom where I expect to keep my .input files. This is what happens (with Axiom in the command-line interface to keep it simple): 1. )cd doesn't work (1) - )cd System error: Cannot get the truename of #p~/. protected-symbol-warn called with (NIL) (1) - Using )system ls, I can see that I am in My Documents, actually c:\Users\evans\Documents. I would guess Axiom didn't do this as it doesn't seem to know it (Axiom) is there. It is probably some kind of windows default. )cd Axiom doesn't work. In fact, nothing I have tried works except: )cd c:/Users/evans/Documents/Axiom Even after that )cd still doesn't work, but )read filename-without-path works. Before doing that )cd Axiom or ./Axiom didn't work. Is there some way to get around this? Note that $HOME is defined as c:\Users\evans\Documents. You
Re: [Axiom-developer] Re: Axiom on Windows
To all -- In the interest of cutting down the amount of FUD one can find here and there: OpenAxiom-1.3.x does not depend on user setting an AXIOM environment variable. Said differently, whether you set or not set AXIOM variable does not affect the behaviour of OpenAxiom. Nor installing OpenAxiom should affect it. -- Gaby On Tue, Feb 1, 2011 at 4:11 PM, daly d...@axiom-developer.org wrote: On Tue, 2011-02-01 at 17:08 -0500, daly wrote: Jeffrey, One of the problems is that Axiom has been forked into FriCAS and Open-Axiom but those versions have not properly specialized the files. This will result in damage to an Axiom installation. I see from your shell variables that Open-Axiom seems to be the last installed version. Tim Daly On Tue, 2011-02-01 at 16:05 -0500, axiom-developer-ow...@nongnu.org wrote: As list administrator, your authorization is requested for the following mailing list posting: List: Axiom-developer@nongnu.org From: k...@kenevans.net Subject: Axiom on Windows Reason: Post by non-member to a members-only list At your convenience, visit: http://lists.nongnu.org/mailman/admindb/axiom-developer to approve or deny the request. email message attachment Forwarded Message From: Kenneth Evans k...@kenevans.net To: axiom-developer@nongnu.org Subject: Axiom on Windows Date: Tue, 01 Feb 2011 14:44:51 -0600 Hi I am new to Axiom and am trying to use it on Windows 7, 64-bit. (I am experienced with Mathematica but have never previously used Axiom.) Most of the bits and pieces to make this work appear to be out there, but are not very well documented or easy to find. Clearly, several people have taken the time to make installers, etc. Surely someone is actually using it successfully on Windows. I myself have it working to some extent. This is what I did: Downloaded: http://axiom-wiki.newsynthesis.org/AxiomBinaries axiom-windows-0.1.4.exe http://sourceforge.net/projects/open-axiom/files/ open-axiom-1.3.0-windows-i386.exe http://axiom-wiki.newsynthesis.org/FriCASBinaries Fricas-Rev.263.exe I installed them in the order OpenAxiom, FriCAS, Axiom (not having much information on which of the three to use). They all installed and made desktop shortcuts. The ones for OpenAxiom and Axiom, more or less worked from the shortcuts with the command-line interface. The one for FriCas failed with a socket error (can't open socket listing file). They all put their paths in PATH, which could possibly be a problem. I uninstalled FriCAS. The others I installed and reinstalled as I found one did some things right and the other other things right. Currently they are both installed with Axiom first in the PATH. I got the QT windows version of TeXmacs. http://axiom-wiki.newsynthesis.org/TeXmacs texmacs-installer.exe I got it running. It is apparently set up for Axiom. I cloned the axiom plug-in and made it work for OpenAxiom using snippets of information gleaned via the web. So I can now run both as sessions in TeXmacs. Axiom works better for me. I can, in fact, do a lot of what Axiom as a CAS is supposed to do. The main problem with TeXmacs is that when it is covered by another window, clicking on the title bar causes it to maximize, rather than just coming on top -- very annoying. The main problem I have right now with the CAS is that I cannot get it to read .axiom.input. I would like to do this to, at a minimum, set my working directory to My Documents/Axiom where I expect to keep my .input files. This is what happens (with Axiom in the command-line interface to keep it simple): 1. )cd doesn't work (1) - )cd System error: Cannot get the truename of #p~/. protected-symbol-warn called with (NIL) (1) - Using )system ls, I can see that I am in My Documents, actually c:\Users\evans\Documents. I would guess Axiom didn't do this as it doesn't seem to know it (Axiom) is there. It is probably some kind of windows default. )cd Axiom doesn't work. In fact, nothing I have tried works except: )cd c:/Users/evans/Documents/Axiom Even after that )cd still doesn't work, but )read filename-without-path works. Before doing that )cd Axiom or ./Axiom didn't work. Is there some way to get around this? Note that $HOME is defined as c:\Users\evans\Documents. You would think it might try $HOME if ~ fails. 2. It does not read .axiom.input. I have tried putting it where it should be (c:\Users\evans) in My Documents and in other places. Does anyone know how to make it read .axiom.input. These are some things from the environment that might be applicable: HOME=c:\Users\evans HOMEDRIVE=C: HOMEPATH=\Users\evans LOCALAPPDATA=C:\Users\evans\AppData\Local
[Axiom-developer] Re: [Axiom-mail] Windows: where's the documentation?
Hello, On 10/31/2006 12:10 PM, Martin Rubey wrote: Dear Paul, So let me refrase my initial question: can somebody convert the hypertex documentation to a general purpose format which is readable on all platforms? Candidate formats are: -pdf -html -info I *STRONGLY* advise you to try something different: install Xming and try to get Tim Daly to give you instructions on compiling Axiom with HyperTex on MS-Windows. Possibly Bill Page also can help. If you mangage to get HyperDoc running and you provide some documentation, I'd propose you for a bounty! If neither of them does, please send mail again, and I'll try to do something myself. Alternatively, if you are keen on programming and know some perl, then maybe Ralf Hemmecke would be able to show you how to modify his AllProse to get something similar to HyperDoc. But I guess this is more difficult. I don't think translating the HyperDoc contents into ALLPROSE is not so easy. And ALLPROSE is probably also not the right way to do it. I guess, you mean AldorDoc. Together with Christian Aistleitner I have agreed upon a few (additional) LaTeX commands to tag type names and function names. That lives basically in aldordoc.sty which is distributed with ALLPROSE. What is still missing is a program AldorDoc, that takes library code and transforms it into a nice format from which .dvi, .pdf, .html etc. could be generated. That program is still missing. Anyway as a first start, I'd like to ask, where I should look for the sources of the contents of HyperDoc. Could someone give a rough overview of the process how the content is produced? If I remember correctly there was some format to write hyperdoc pages, but what does that have to do with the API description of functions/domains/categories of Axiom. I guess the latter is generated from the ++ comments in the .spad files, right? Then what is the process from ++ to hyperdoc? The great thing about hyperdoc is that you can enter a category, say, for example, Ring, then press on a button labelled Domains and you will get all Domains known to Axiom that are Rings. I.e., Integer, Polynomial Integer, Fraction Integer, PrimeField, and so on. Right. ALLPROSE cannot do that. There are other tools necessary. Ralf ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer
[Axiom-developer] Re: [Axiom-mail] Windows: where's the documentation?
The point is that the list of domains which are of a certain category is created dynamically. If I start a fresh axiom session, compile a spad file which contains some new Ring, say MyWonderfulPhantasticRing it will be listed by HyperDoc automatically. Lots of software out there feature a built-in web server so that a browser can act as the control. Axiom could do the same for the documentation, system settings and other automation features. The asq function was intended for non-X platforms so we could still deliver the information without running Axiom. I'm not much of a cgi-bin hacker but it seems to me that some simple C hacking and a command line option would enable the output to be placed in html tables which could somehow allow point-and-click for additional lookups. Memory fails me but there is some way of constructing POST or GET around items in tables so that you could click on table entries. I'll have to look at my html reference book for details. Indeed if the constructed html could pass algebra expressions back to the cgi-bin then it could run axiom, capture the output, and send it back. The source is in src/etc/asq.c.pamphlet. There is some documentation but I guess I thought the structure of the databases as random access files was obvious. I'll clearly have to update the documentation :-) I wrote some detailed documentation about the database file format somewhere on this list a couple weeks ago. I'll try to find it and add it to the literate documentation of asq. t ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer
[Axiom-developer] Re: [Axiom-mail] Windows: where's the documentation?
I vaguely remember that somebody managed to have HyperDoc on MS-windows, given that an X-server is installed? Martin ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer
[Axiom-developer] Re: [Axiom-mail] Windows: where's the documentation?
yes, i have hyperdoc running on windows. but it requires the Xming program and i haven't had time to document and package it. t ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer