On 10/4/07, Fernando Perez <[EMAIL PROTECTED]> wrote: > Minor note (I haven't been following in detail): the underlying > ipython below sage already has an %edit command (type %edit? for > details) than includes hooks for declaring custom editors, handling > the fact that there are editors whose commands exit immediately on > starting and others that block, etc. Just an FYI.
The behavior of %edit is a lot different than the edit command we're discussing. %edit? ... This command allows you to conveniently edit multi-line code right in your IPython session. --- The command we're discussing in Sage is different: edit(foo) for foo a function defined in the Sage library (right now, at least), finds the original source file that defines foo, and puts you in an editor to edit that file. Doing "sage -br", would then build and install the resulting file. So they are two fairly different things, with the same name. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
