On Thu, Mar 01, 2007 at 11:14:14PM -0800, William Stein wrote:
>
> On Thursday 01 March 2007 11:01 pm, Nick Alexander wrote:
> > On Mar 1, 3:25 pm, Martin Albrecht <[EMAIL PROTECTED]>
> >
> > wrote:
> > > > > I'm also wondering what are the most common usage methods of SAGE:
> > > > > 1) notebook
> > > > > 2) command line sage prompt
> > > > > 3) file.sage or file.py scripts
> > >
> > > I actually use the notebook quite often now, especially when
> > > debugging/timing code. The reason is that my inputs are still there (even
> > > without going up and down the history) if SAGE crashes etc. I also love
> > > the %sagex feature.
> >
> > Hmm... perhaps we should be thinking about moving that feature into
> > the CLI then? What is it that's so useful?
>
> If you put "%sagex" at the top of an input cell, then the rest
> of the cell is compiled by sagex. In the CLI, one can do
>
> sage: sagex("""
> a bunch of code
> """)
>
> This obviously sucks, since editing multi-line chunks of code
> is not the strong point of a CLI.
Yes, that's correct, but ipython thought about that too and provided the %edit
magic command -- very nice. Of course, I say "very nice", but it's not nice
enough which is why I almost always put these chunks in file.py and run them
with "sage file.py".
--
Joel
>
> 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-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
