#8776: notebook: sage notebook undo doesn't really work, due to not enough (=no)
automatic snapshots, or other bugs
------------------------+---------------------------------------------------
Reporter: was | Owner: jason, was
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.7.2
Component: notebook | Keywords:
Work_issues: | Upstream: Reported upstream. Little or no
feedback.
Reviewer: | Author:
Merged: | Dependencies:
------------------------+---------------------------------------------------
Changes (by kcrisman):
* status: new => needs_review
Comment:
Replying to [comment:10 schymans]:
> I already rebuilt it using ./sage -b (as suggested in the devel
instructions), but I tried again using ./sage -br. No change, all
snapshots are still identical.
Okay, good to know. I assume that you are referring to snapshots
"created" ''after'' the time you applied the patch; obviously, previous
snapshots wouldn't magically change!
> Is it normal that sage-0.0.0-py2.6.egg-info is re-built every time, or
does it imply that the patch was not fully applied and lingers somewhere
in the queue? Is there a way to check from within sage that the new code
is actually used? E.g. by typing "sagenb-undo??" or something along these
lines?
No, this is actually what is supposed to happen. I wouldn't worry about
whether the code is used; that's the job of those writing patches :)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8776#comment:11>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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/sage-trac?hl=en.
