Not sure if you've tried it out, but here's why the new way is better than inserting a new cell. (By new way, I mean branch spacer-focus.)
If the user wants to execute the current cell, then start typing code in a new cell after the current one, both ways are the same. Shift+Enter, then start typing. If the user wants to execute the current cell, but not create a new cell after the current one: -- New way: Shift+Enter (no cell is created, the "spacer" is just focused) -- Insert cell way: Shift+Enter, then delete the new cell I hope this clears it up. Too bad about the installer. Sam On Mon, Aug 8, 2011 at 11:37 PM, Aaron Meurer <[email protected]> wrote: > On Mon, Aug 8, 2011 at 4:44 PM, Sam Magura <[email protected]> wrote: > > Thanks for the merge. > > Check out the branch spacer-focus on sympy-notebook. I've set it to focus > > the next spacer rather leave the focus in the input cell when a cell is > > executed. I think it makes it much more clear how to create a new cell. > > I think automatically inserting a new cell would be annoying in many > > situations. > > I don't see how. To me, *not* automatically inserting a new cell is > annoying. > > Oh, and by the way, that installer you linked to just installs pygtk, > not gtk (and of course, installing pygtk from source once you have gtk > is trivial). > > Aaron Meurer > > > Anyway, this way doesn't require any more keystrokes. > > Sam Magura > > > > On Mon, Aug 8, 2011 at 4:22 AM, Aaron Meurer <[email protected]> wrote: > >> > >> OK, I've merged your pull request, and I now have working LaTeX output. > >> > >> By the way, I wasn't very clear when I said "the interaction is a > >> little awkward". I think the main thing (aside from the Shift-Enter > >> vs. Enter deal) is that executing a statement does not create a new > >> cell. Indeed, it's not very clear at all how to create a new cell. > >> > >> Aaron Meurer > >> > >> On Sun, Aug 7, 2011 at 7:54 PM, Aaron Meurer <[email protected]> > wrote: > >> > On Sun, Aug 7, 2011 at 7:50 PM, Sam Magura <[email protected]> > wrote: > >> >> > >> >> On Sunday, August 7, 2011 9:09:57 PM UTC-4, Aaron Meurer wrote: > >> >>> > >> >>> Ah, no. I didn't know about this. Assumedly it is some branch at > >> >>> your GitHub fork? > >> >>> > >> >>> What did you have to change in your fork to make it work? > >> >> > >> >> Yes, it's the master branch of my sympy fork. Here's the pull > >> >> request: https://github.com/sympy/sympy/pull/500 > >> > > >> > Oh. Sorry that that got forgotten due to the unrelated bug. I'll go > >> > and review it right now. > >> > > >> > Aaron Meurer > >> > > >> >>> > >> >>> Yes it does: > >> >>> > >> >>> In [33]: a > >> >>> > >> >>> > >> >>> > --------------------------------------------------------------------------- > >> >>> NameError Traceback (most recent > call > >> >>> last) > >> >>> > >> >>> > >> >>> > /Users/aaronmeurer/Documents/python/sympy/sympy/<ipython-input-33-60b725f10c9c> > >> >>> in <module>() > >> >>> ----> 1 a > >> >>> > >> >>> NameError: name 'a' is not defined > >> >>> > >> >>> In [34]: sympify("a") > >> >>> a > >> >>> > >> >>> In [35]: type(sympify("a")) > >> >>> <class 'sympy.core.symbol.Symbol'> > >> >> > >> >> Ah, I see what you are saying. I thought you were saying that > >> >>>>> sympify("a = b**2") > >> >> would define b as a symbol. But rather, what I can do is something > like > >> >>>>> #Return raw Python code > >> >> .... my_parser("a = b**2") > >> >> "sympify('b', locals=locals()) > >> >> a = b **2 " > >> >>> > >> >>> By the way, your parser has a bug where it prints the output of > >> >>> variable assignments, i.e., > >> >>> > >> >>> : a = 1 > >> >>> > >> >>> should be silent. > >> >> > >> >> Not a bug, but OK, (having it silent) would be more in line with the > >> >> Python > >> >> console. Added to future feature list. > >> >> I've just gotten back to school, so probably won't be doing much work > >> >> over > >> >> the next week. I'll notify you when I add new major features. > >> >> Sam > >> >> > >> >> -- > >> >> You received this message because you are subscribed to the Google > >> >> Groups > >> >> "sympy" group. > >> >> To view this discussion on the web visit > >> >> https://groups.google.com/d/msg/sympy/-/KTO7Sl6-mnoJ. > >> >> 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/sympy?hl=en. > >> >> > >> > > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "sympy" group. > >> 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/sympy?hl=en. > >> > > > > -- > > You received this message because you are subscribed to the Google Groups > > "sympy" group. > > 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/sympy?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > 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/sympy?hl=en. > > -- You received this message because you are subscribed to the Google Groups "sympy" group. 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/sympy?hl=en.
