On Saturday, June 9, 2012 2:06:20 AM UTC-6, Simon King wrote: > > For me, the "usual" interface is the command line interface. I hardly ever > use the notebook (except for teaching). Note that apparently one can > also use Sage in emacs (there is sage-mode), but I have never tried. >
The command line is great when I have a few quick commands, but I find it painful for developing multi-line methods (i.e. 'coding'). I never caught onto emacs, so alas that approach isn't useful to me. If I were to develop something, I would do it with something like Eclipse. It's cross-platform and meant for building coding GUI's. It also appears stable and solid. > I don't know why you need to refresh a worksheet or restart the notebook > server or even Sage, if you just change a .py or .pyx attachment. Anyway, > if you attach code to a command line session then it is automatically > updated (i.e., recompiled if we talk about a .pyx attachment). No need > to restart anything. > The attach command is the key thing I was not aware of. In a typical cycle I can touch several .py and .pyx files, so this will save me a lot of agony. Thanks! Conclusion: If it is really the case that the notebook ignores changes > in an *attached* file (note the difference between a loaded and an > attached file), then I'd say it is a bug. It does work in the "usual" > command line interface. > In a quick experiment the notebook behaved as I would expect, so I think this is a great solution. Best, Chris -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
