On Wed, Nov 11, 2009 at 2:19 PM, [email protected] <[email protected]> wrote: > > Dear sage-support > > When changing the code, running ./sage -b and testing the things in > notebook in Firefox I tried to keep ./sage -notebok running, I changed > some code in another window and compiled with ./sage -b. Switching > back to notebook, something hang and notebook did not work as > expected. So I had to repeat these steps > > * close notebook > * shutdown sage session with notebook > * change code > * ./sage -b > * ./sage -notebook > * login > * go to my worksheet > * test if things works, not? go to the first step ..... > > I worked on something related to maxima and calculus, so it has > nothing to do with code for notebook. > > Is it really necessary allways to repeat all these steps when > debugging some code? Maybe I missed something ....
No. Just click "Action --> Restart worksheet" (possibly twice) and you'll get the new version of Sage. There is no need to ever restart the notebook server unless you're doing development on the notebook server itself. -- william --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
