Revision history [back]
 | 1 | initial version |
You need to do the reset from the Sage command line. So first start Sage in the command line, and then do
$ /path/to/sage
<sage startup sequence begins>
sage: notebook(reset=True)
The path to sage will depend; if you put it in Applications then it might be something like
/Applications/Sage.app/Contents/Resources/sage/sage
| | 2 | No.2 Revision |
You need to do the reset from the Sage command line. So first start Sage in the command line, and then do
$ /path/to/sage
<sage startup sequence begins>
sage: notebook(reset=True)
The path to sage will depend; if you put it in Applications then it might be something like
/Applications/Sage.app/Contents/Resources/sage/sage
Edit: I am not sure where it went but I saw some update about two notebooks running ... this would happen if you accidentally ended up opening two while doing this. In which case you'll have to use commands like ps aux or top to identify which process IDs are the problem, and then use kill -9 pid, where pid is the process id, to stop them. Sorry about all this command line stuff :(d
