On Thu, Dec 23, 2010 at 5:49 PM, Stephan Beal <[email protected]> wrote:
> Again, i don't consider this to be a fossil problem, but stupid user error. > Another point: this "problem" was a side-effect of my own personal workflow, using an operation which has obvious risks of making unwanted changes (e.g. i didn't properly use \b in the perl expression to ensure unwanted expansions on other matching tokens). e.g. if i was fossiling Java code and had used a modern IDE to refactor the code, this would never have come up. (But i know no better C refactoring tools than perl and emacs.) i guess what i'm saying is: don't change fossil for this. i just thought the recovery was enlighteningly simple, and wanted to share it. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
