Re: [fossil-users] undo option unavailable even when nothing changed

2014-04-19 Thread Stephan Beal
On Sat, Apr 19, 2014 at 7:53 PM, wrote: > Fine, but I don’t think this would require a multi-level undo stack. A > simple flag to indicate at the > No, it wouldn't require much actual effort, it just requires that revert check for changes before trying to revert. completion of any command if

Re: [fossil-users] undo option unavailable even when nothing changed

2014-04-19 Thread tonyp
is. No time-consuming checks would be needed, IMO, if setting of the flag is placed in the correct places. From: Stephan Beal Sent: Saturday, April 19, 2014 6:35 PM To: Fossil SCM user's discussion Subject: Re: [fossil-users] undo option unavailable even when nothing changed On Sat, A

Re: [fossil-users] undo option unavailable even when nothing changed

2014-04-19 Thread Stephan Beal
On Sat, Apr 19, 2014 at 4:18 PM, wrote: > This does not seem to be right. Because if by mistake you type “f rev” > twice (not being sure if you’ve already done it) you lose the ability to > undo. > A multi-level undo stack has been on the wish-list for a while but has never been implemented.