Thank you sensei!
On May 24, 5:21 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> I've attached the hg patch that fixes the notebook problem you've
> been reporting. You can apply it with
>hg_sage.apply('4585.patch')
> followed by "sage -br" (which will take 10 minutes)..
> Or, just wait f
I've attached the hg patch that fixes the notebook problem you've
been reporting. You can apply it with
hg_sage.apply('4585.patch')
followed by "sage -br" (which will take 10 minutes)..
Or, just wait for sage-2.5.4.
On 5/24/07, William Stein <[EMAIL PROTECTED]> wrote:
> On 5/24/07, Marshall H
On 5/24/07, Marshall Hampton <[EMAIL PROTECTED]> wrote:
> Help! I was hoping to collaborate with someone using SAGE this week
> via a notebook, and I can't unless I get this fixed.
>
> Because I was getting errors as described above, where the leading /
> was missing on the path, I used a double /
Help! I was hoping to collaborate with someone using SAGE this week
via a notebook, and I can't unless I get this fixed.
Because I was getting errors as described above, where the leading /
was missing on the path, I used a double // in my path for the
notebook, i.e. a command starting out as:
n
Argh! This happened to me again, this time on a fresh 2.5.3 install.
I thought that starting from scratch might fix things.
I have the problem using a notebook with an IP address - i.e. it
hasn't happened yet on this installation on the default settings -
notebook(). Nothing will display using s
On 5/23/07, Marshall Hampton <[EMAIL PROTECTED]> wrote:
>
> Stupid question: How do you directly load a .sobj file?
Use the load command. E.g., if foo.sobj is an obj, do
sage: foo = load('foo.sobj')
--~--~-~--~~~---~--~~
To post to this group, send email to sa
Here are two more diagnostic data points: the problem persists even if
I run sage as a different user, but things seem OK if I just use the
basic notebook() command with no arguments. Since I had done that
before having these problems, I wonder if something goes wrong when a
brand-new nb.sobj is
Here are two more diagnostic data points: the problem persists even if
I run sage as a different user, but things seem OK if I just use the
basic notebook() command with no arguments. Since I had done that
before having these problems, I wonder if something goes wrong when a
brand-new nb.sobj is
Here are two more diagnostic data points: the problem persists even if
I run sage as a different user, but things seem OK if I just use the
basic notebook() command with no arguments. Since I had done that
before having these problems, I wonder if something goes wrong when a
brand-new nb.sobj is
Here are two more diagnostic data points: the problem persists even if
I run sage as a different user, but things seem OK if I just use the
basic notebook() command with no arguments. Since I had done that
before having these problems, I wonder if something goes wrong when a
brand-new nb.sobj is
Stupid question: How do you directly load a .sobj file?
This display problem seems to have actually gotten worse; now when I
start up a brand-new notebook the problem appears right away.
Upgrading to 2.5.3 didn't seem to help.
In case it helps at all, I have created a record of my entire noteboo
On 5/18/07, Marshall Hampton <[EMAIL PROTECTED]> wrote:
> Thanks. Several of my .sws files gave me errors when I tried to
> upload them - is there any compatability requirements for that - e.g.
> having the same version of sage or sage directory? Its also possible
No -- all versions should work
Thanks. Several of my .sws files gave me errors when I tried to
upload them - is there any compatability requirements for that - e.g.
having the same version of sage or sage directory? Its also possible
that I saved those worksheets on a Windows machine and then moved them
over to my OS X laptop
On 5/18/07, Marshall Hampton <[EMAIL PROTECTED]> wrote:
>
> Well, yeah, I'm sure it was dumb - my first guess was that the units
> were pixels - but I think the interesting thing is the subsequent
> effect on the worksheet.
>
> I haven't found a simple reproducible version of my more serious,
> pr
Well, yeah, I'm sure it was dumb - my first guess was that the units
were pixels - but I think the interesting thing is the subsequent
effect on the worksheet.
I haven't found a simple reproducible version of my more serious,
previous problem which corrupts the entire notebook. I have several
wo
On 5/17/07, Marshall Hampton <[EMAIL PROTECTED]> wrote:
> I have a more reproducible version of this bug. If you execute the
> following three commands in seperate cells, you should see the sort of
> problem I am having:
>
> show(line(((0,0),(1,1
>
> show(line(((0,0),(1,1))),figsize=[1280,800]
I have a more reproducible version of this bug. If you execute the
following three commands in seperate cells, you should see the sort of
problem I am having:
show(line(((0,0),(1,1
show(line(((0,0),(1,1))),figsize=[1280,800])
show(line(((0,0),(1,1
The middle command generates an error
I copied/pasted it from the notebook, so its not a typo.
I opened it by navigating manually through the filesystem, but the
address is correct (with the leading /).
I haven't had a problem of this type before, and I have done some very
similar things. The trouble began when I was writing some f
On May 16, 2007, at 1:35 PM, Marshall Hampton wrote:
> I am having trouble getting the show() command to work in the
> notebook. After the following commands:
>
> sage: a = [[[0.0, -1.0], [0.0, 1.0]], [[0.0, 1.0], [0.0, -1.0]]]
> sage: pts3=[point((pt[0],pt[1])) for w1 in a for pt in w1]
> sage
19 matches
Mail list logo
