Sorry to be opaque - it's a question and maybe a feature request.  The more 
I use Leo the more I want it open 'everywhere' - the more of a pain 
creating multiple copies of saved files is.  I'm sure there are other ways 
of achieving sync but I thought a node based solution might be easy to use 
and not too difficult to implement?



On Saturday, 3 February 2018 15:53:01 UTC, Edward K. Ream wrote:
> On Fri, Feb 2, 2018 at 3:08 AM, Israel Hands < 
> <javascript:>> wrote:
> I often find myself working on a file in dropbox that is open somewhere 
>> else. The result being that when I save I get a 'copy of the file'.  And 
>> using file compare I can generally work out what changes need to be merged 
>> to get everything back in sync.  I'm sure there is a Git solution but I 
>> wondered if a node based option would be handy.
>> So I'm working on a node - Agenda for next meeting -  and let us assume 
>> this is the only node that has been changed, then when I hit save then Leo 
>> saves the file but makes a duplicate node at exactly the same level with 
>> the name 'CUSTOM TEXT Agenda for the next meeting' 
>> This keeps all the available options together and makes the changes easy 
>> to find?
> ‚ÄčIs this a question, comment or tip?
> 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 post to this group, send email to
Visit this group at
For more options, visit

Reply via email to