On Sat, Jan 31, 2009 at 8:17 AM, mabshoff wrote:
>
>
>
> On Jan 30, 9:55 pm, john_perry_usm wrote:
>> Hey, it turns out that you hit it on the money. While looking through
>> it again, I noticed that when examining the source through sage
>> (using ??) the source file was listed in the directory
On Jan 30, 9:55 pm, john_perry_usm wrote:
> Hey, it turns out that you hit it on the money. While looking through
> it again, I noticed that when examining the source through sage
> (using ??) the source file was listed in the directory
> /atlas/home/perry/nethome/sage-3.2.1/...
> inste
Hey, it turns out that you hit it on the money. While looking through
it again, I noticed that when examining the source through sage
(using ??) the source file was listed in the directory
/atlas/home/perry/nethome/sage-3.2.1/...
instead of
/home/software/sage-3.2.1/...
"nethome" i
Thanks.
"which sage" gives /usr/local/bin/sage, but the working directory is /
home/software/sage-3.2.1/devel/sage and I'm calling "../../sage -b"
from the command line. That seems (to me) to rule out that
possibility.
john
On Jan 30, 7:00 pm, Jason Grout wrote:
> john_perry_usm wrote:
> > Hi
john_perry_usm wrote:
> Hi all,
>
> I'm trying to make some changes to my sage installation. I change the
> file in the $SAGE_ROOT/devel tree, then call $SAGE_ROOT/sage -b
>
> Now this works on my laptop, but not on my desktop. If I run
> $SAGE_ROOT/sage, it's as if I made no changes at all.
>
