Possibly related. My interest in LeoFS started with the desire for a list of nodes sorted by when I last created, edited and viewed them. (I tend to be working on several things at once, want to retrieve my prior train of thought effortlessly)
I like the idea of an sqlite file which has a row for each node, changing a node creates a new row. This will provide timelining and versioning. I use lots of @auto nodes, which require some additional fuss, but I think I can see how to work with them: when one is loaded, walk it and check the generated nodes against the database. This should lead to node-level undo, and function/class/method level undo of source files. Thanks, Kent On Mon, Oct 3, 2011 at 7:46 PM, Edward K. Ream <[email protected]> wrote: > On Mon, Oct 3, 2011 at 6:17 PM, Matt Wilkie <[email protected]> wrote: >> Since Leo is enjoying a spring of sorts, with fresh ideas growing and >> renewed life on old ones, I thought I'd share something which has long >> bugged me but I've never seen anyone talk about, at least clearly and >> eloquently, until today. >> >> QQQ >> A Modern Undo - Making undo usable beyond the last few changes >> http://e-texteditor.com/blog/2006/making-undo-usable > > Thanks for this. I've put it on the list of things to consider. > Surely, a better undo would help us all. > > Edward > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" 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/leo-editor?hl=en. > > -- You received this message because you are subscribed to the Google Groups "leo-editor" 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/leo-editor?hl=en.
