Although I would have preferred it just be a fixable glitch with my personal setup, it's good to know I'm not crazy. If others haven't noticed this before, obviously not a high-priority issue, but it brings up a couple of points that might be of more general interest.
As a workaround I'm considering keybinding the delete-node command (suggested keystrokes welcome), but of course that would be dangerous. Is there a way to make it work safely - on nodes which have at least one clone remaining? Not only to prevent data-loss from old-fuddy-brainfarts, but accidental wrong-key-presses. . . I'm **not** asking anyone to write a custom script for me please (just in case someone was going to 8-), but suggesting that if it isn't possible now, perhaps a delete-safely command would be a useful wishlist? -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/QLkE1z9_6p8J. 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.
