> We need a name for this concept.
It looks like it's a `sequence', isn't it?
--
Matthias
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.c
> Now I agree. The difficult part is having three latex processes with
> three sentinels.
That's it!
I shifted to the version shipped with sage-mode-0.5.2 this morning. I'll
be away for a couple of days, so you'll hopefully get the multiple
outputs stuff in the middle of next week.
Regards,
> Would that were true! There are plenty of bugs left, maybe you will
> help me fix them :)
I am currently working on `the multiple output bug'. More precisely,
in case we run the following code, three overlays should be inserted
in the sage buffer:
m = Matrix(QQ, 5)
m.randomize()
for i in ra
Hi Pierre,
> I've installed the latest package for emacs, now with sage-view. Wow !
> very very cool, all the bugs are gone.
Thanks to Nick Alexander's great work!
> could i combine this behavior with the nice formulae of sage-view ?
> this would be the definite death of the notebook for me (no
> (...) but it didn't reset the cached gap workspace.
I see. I was not aware of this. After removing $HOME/.sage/gap it works!!
Thanks a lot!
--
Matthias
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from t
> Could you try changing line (...)
I've added the -r option to gap_cmd, and run sage with -br options; The
problem is still there.
To get rid of the problem I have to remove the file .gaprc, then rebuild
the GAP spkg. Finaly I can get my .gaprc back, everything will work
fine:
- Sage won't b
> GAP will look for .gaprc in the home directory. I don't know how to
> change this (or if it can be changed) but Steve Linton does.
There's a command line option for this; From GAP man page:
-r disable/enable reading of the '.gaprc' file
> I also don't quite understand the original poster's
Hi,
I successfully compiled Sage 3.1.2 from source. But I had troubles
with many commands... I finaly realized that all functions using a GAP
subprocess where buggy, which was related to a corrupted prompt; see:
sage: gap._eval_line('1+3;')
'4\n\x1b[1m\x1b[34mgap> \x1b[0m'
Removing $HOME/.gaprc
