Re: undoing unmarks nodes

On Thu, Oct 8, 2020 at 1:42 PM gar wrote: > a concept known as "node history". > > where can I get familiar with it? I'd love to have node-scoped undo. > See the history_tracer.py plugin. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group.

Re: undoing unmarks nodes

> > a concept known as "node history". where can I get familiar with it? I'd love to have node-scoped undo. I use leo generally as a code editor, and I still deal with nodes as with files in any other code editor, but smaller size. -- You received this message because you are subscribed to the

Re: undoing unmarks nodes

On Thu, Oct 8, 2020 at 6:58 AM gar wrote: Actually let my say a word about undo. > I feel very uncomfortable when undo unmarked nodes and remove clones. > Actually when I started to use Leo I expected that there would be several > undoes: for tree operations, for editors, for marks/clones etc. >

Re: undoing unmarks nodes

Undos are ok being simply "one operation undone in same order" and not different undo stacks for each kinds or operations. About the marked node being unmarked: it feels like after marking a node, an undo 'step' was not created after this operation, and therefore, after undoing some other

Re: undoing unmarks nodes

I figured it must be VIM or emacs! On Thursday, October 8, 2020 at 8:43:55 AM UTC-4, gar wrote: > > I am VIMer, so I cannot imagine too complicated actions :-) I can see only > different levels of simplicity > > чт, 8 окт. 2020 г. в 15:35, Thomas Passin > >: > >> @gar: "Actually when I started

Re: undoing unmarks nodes

I am VIMer, so I cannot imagine too complicated actions :-) I can see only different levels of simplicity чт, 8 окт. 2020 г. в 15:35, Thomas Passin : > @gar: "Actually when I started to use Leo I expected that there would be > several undoes: for tree operations, for editors, for marks/clones

Re: undoing unmarks nodes

@gar: "Actually when I started to use Leo I expected that there would be several undoes: for tree operations, for editors, for marks/clones etc." That sounds too complicated to me. I would expect undo actions to happen in the (reverse) order that I did them in the first place, whether they

Re: undoing unmarks nodes

Actually let my say a word about undo. I feel very uncomfortable when undo unmarked nodes and remove clones. Actually when I started to use Leo I expected that there would be several undoes: for tree operations, for editors, for marks/clones etc. Can anybody explain me why all the sorts of undoes

Re: undoing unmarks nodes

On Mon, Oct 5, 2020 at 3:40 AM gar wrote: > I reported that long time ago. Actually I do observe that marks > disappear even w/o undo, sort of suddenly. The new #1694 suggests a thorough review of the marked bits logic. Edward -- You

Re: undoing unmarks nodes

I reported that long time ago. Actually I do observe that marks disappear even w/o undo, sort of suddenly. Since I didnt use clones for my @auto code files - I used marks intensively to quickly switch btw various code-in-work nodes and was totally upset with how they do behave. Again, just

Re: undoing unmarks nodes

I can confirm that a marked node gets unmarked by an undo operation for a change later than the change that marked the node. I don't think that should happen. I think that marking nodes should be undoable - if only because the marks get saved when the outline is saved, so they are a real

undoing unmarks nodes

using leo on latest devel branch: Marked nodes get unmarked when performing an undo operation in them... is this a real (known) bug someone else can reproduce, or i'm doing something silly that i'm not aware of? -- Félix -- You received this message because you are subscribed to the Google