I asked for advice in another thread, but I believe this deserves to have its own topic. This way we can also avoid the situation when one thread contains a couple of paralel talk flows and becomes harder to follow.
Back to the subject. Basically we are talking here about a three-way merge: - myLeoSettings - global leoSettings (previous version) - global leoSettings (current version) Questions that arise: - how should the user be notified if the global settings file has changed, unless he will be explicitly watching each commit log, which is time-consuming - assuming the user already knows about the change, what's an easy and lazy way to get the previous version of leoSettings? Perhaps leo could keep track of this itself and issue a notification message in the log pane? The user has his own myLeoSettings in home dir, current leoSettings in leo's source tree. From a developers' perspective one shall grep the commit logs again and get the previous version using bzr voodoo, but doing this manually every day becomes a challenge. Of course a very regular user would download just the stable release and can compare that leoSettings with the one from the previous stable release. But someone (like me) who pulls the trunk more often faces this challenge. -- 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.
