Hi folks,
Not sure how feasible this is, but I've noticed that when sharing
development and using @thin nodes, Leo detects that a file has changed
before overwriting it. Specifically, here's the use model I see:
* Have all critical files either @auto or @thin nodes, with a
master.leo file loading structure
* All these files are under version control
* If another developer updates the @thin file in version control,
and you do an update while leo is running, the existing @thin node
is now dirty
Would it be potentially possible to refresh an unchanged @thin or @auto
node when a background change is detected? After asking the user if we
should?
Mike
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
