> Having the .leo file in version control hurts no one ... But what is the reason to have it in version control? In my mind, it's just an extension of the local code viewer/editor (Leo) and therefore not something that would normally be under version control. And if you get multiple people using Leo to edit versioned files, wouldn't they all have individual local .leo files suited to the way they like to view and edit content? Especially if you are committing @thin files, it just seems to be an unnecessary complication with potentially unintended consequences to commit the .leo file.
Steve --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
