The prospect of being able to work concurrently on a single file in Leo and something else is very exciting! I'm often going back and forth between Leo (for node organization) and PyScripter (for interactive prompts, docstring display, and run time variable inspection). I've messed myself up a few times forgetting to close the other session down first.
Question: what happens to undo history when a @nosent file is changed externally changed and reloaded? An approach I've seen elsewhere is to throw it away. I understand why they do that. It can quickly get impossibly complicated to do the right thing if the external change is in the undo action area. It's annoying when the only change to the file is a touch though. Matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
