On Saturday 19 January 2008, Ondrej Certik wrote:
On Jan 19, 2008 7:38 AM, Ondrej Certik [EMAIL PROTECTED] wrote:
On Jan 18, 2008 10:00 PM, Georg Grafendorfer
[EMAIL PROTECTED] wrote:
Michael,
OK, i'm already a bit confused, and i don't know any more what your
requesting exactly,
On Jan 19, 2008 2:25 AM, bill purvis [EMAIL PROTECTED] wrote:
On Saturday 19 January 2008, Ondrej Certik wrote:
On Jan 19, 2008 7:38 AM, Ondrej Certik [EMAIL PROTECTED] wrote:
On Jan 18, 2008 10:00 PM, Georg Grafendorfer
[EMAIL PROTECTED] wrote:
Michael,
OK, i'm already a bit
On 19 Jan., 14:57, William Stein [EMAIL PROTECTED] wrote:
I think the upshot of the entire discussion above is (or should be) to use
#!/usr/bin/env sage
instead of
#!/usr/bin/env sage -python
This assumes sage is in your path -- and indeed it should be if you want
to write
On Jan 18, 9:09 pm, Georg Grafendorfer
[EMAIL PROTECTED] wrote:
Hi Robert, excuse me for the response delay, i did not notice your question,
Does
#!/path/to/sage_root/local/bin/sage-python
work?
no, the output is in both cases (sage -python as well as sage-python):
bash:
Hi again,
in my previous posting i had the lines
#!/path/to/sage_root/local/bin sage-python
#!/path/to/sage_root/local/bin sage- python
instead of your request:
#!/path/to/sage_root/local/bin/sage-python
this gives me the same strange mouse effect as described in the original
posting, whereas
Hi Robert, excuse me for the response delay, i did not notice your question,
Does
#!/path/to/sage_root/local/bin/sage-python
work?
no, the output is in both cases (sage -python as well as sage-python):
bash: ./exp1.sage: /home/georg/Daten/.System/bin/sage/local/bin: bad
interpreter: Keine
On Jan 19, 2008 7:38 AM, Ondrej Certik [EMAIL PROTECTED] wrote:
On Jan 18, 2008 10:00 PM, Georg Grafendorfer
[EMAIL PROTECTED] wrote:
Michael,
OK, i'm already a bit confused, and i don't know any more what your
requesting exactly, so i will repeat some things:
The file with the name
On Jan 18, 2008 10:00 PM, Georg Grafendorfer
[EMAIL PROTECTED] wrote:
Michael,
OK, i'm already a bit confused, and i don't know any more what your
requesting exactly, so i will repeat some things:
The file with the name ./example.sage
#!/home/georg/Daten/.System/bin/sage/sage -python
On Jan 19, 2008 7:38 AM, Ondrej Certik [EMAIL PROTECTED] wrote:
On Jan 18, 2008 10:00 PM, Georg Grafendorfer
[EMAIL PROTECTED] wrote:
Michael,
OK, i'm already a bit confused, and i don't know any more what your
requesting exactly, so i will repeat some things:
The file with the name
Georg,
#!/path/to/sage_root/sage-python
does not work, but maybe that's not important,
Does
#!/path/to/sage_root/local/bin/sage-python
work?
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this
Georg,
1. Is this a clean, from-source build of sage-2.9.3?
2. What is the output of /usr/bin/env for you? Mine (Intel OS X
10.5.1) doesn't mention sage at all, although mysteriously things are
working for me.
#!/usr/bin/env sage -python
import sys
For me, I get
$ ./BMV.sage
$
Also, if I
Hi Robert,
1. Is this a clean, from-source build of sage-2.9.3?
Yes, i tried it out on two different systems now, Athlon XP, and Core Duo,
both running on Debian Etch, and both show the same behaviour
2. What is the output of /usr/bin/env for you? Mine (Intel OS X
10.5.1) doesn't mention sage
On Jan 15, 2008 3:00 PM, Georg Grafendorfer
[EMAIL PROTECTED] wrote:
Hi Robert,
1. Is this a clean, from-source build of sage-2.9.3?
Yes, i tried it out on two different systems now, Athlon XP, and Core Duo,
both running on Debian Etch, and both show the same behaviour
2. What is the
On Jan 16, 12:40 am, William Stein [EMAIL PROTECTED] wrote:
On Jan 15, 2008 3:00 PM, Georg Grafendorfer
[EMAIL PROTECTED] wrote:
Hi Robert,
1. Is this a clean, from-source build of sage-2.9.3?
Yes, i tried it out on two different systems now, Athlon XP, and Core Duo,
both
14 matches
Mail list logo
