On Friday, February 6, 2015 at 9:55:40 AM UTC-6, Kent Tenney wrote: > Will @nosent be able to offer 'Refresh from disk' ?
Yes. And thanks for the reminder. I'll make sure this works asap. It should not be a big deal: all the necessary data is in the outline. Refresh from disk will probably just call at.readOneAtNosentNode. As of rev 0533a97, the import-file command now imports to @nosent rather than @file. This is much safer: only "real" changes will appear in (say), the git diff when you save the file to disk. Furthermore, the recursive import script, that is, calls to c.recursiveImport, now treats @nosent pretty much identically to @file. So setting the keyword argument use_at_nosent = True works properly. This is all very exciting. I can now use @nosent files to patch code in the Python library. I can change the library either from Leo or from an external editor and everything will just work. I track the site-packages folder in git for safety. Now the git diff won't get overwhelmed with added Leo sentinels, so real changes stand out better. Edward -- 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.
