On Thu, Apr 2, 2009 at 3:49 PM, Edward K. Ream <[email protected]> wrote:
>> a) .leoSettings.leo_db >> b) .leoDocs.leo_db >> c) .leo_shadow >> d) .leoPluginsRef.leo_db > > Thanks for this report. I think it is important, and needs a good solution. > > I dislike all these files being sprayed around the file system. I'd like to > see these files placed somewhere the ~/.leo directory. Is there a reason > why this would be a bad idea? People may want to manage these files in their version control-system, for example. They are not "temporary" files. I don't see why this is a problem, really. Uninstall can't remove files that it installed - but do we really care? > In both cases, I think we want to create files that indicate their > location. Either that, or mirror their location in (subdirectories) > ~/.leo. In other words, this is a general problem, and it would be good to > have a robust, general solution. > > Ville, do you have any comments or suggestions? I initially thought of adding these under .leo, but I was suggested to put them next to the real file. I think this is quite good solution. The fact that if you choose to open .leo files from leo distribution itself suggests that "uninstallation" is a dangerous operation. For one, it discards all the changes you may have done to those files. One problem I need to solve is that often the directory is read-only (owned by root), e.g. when leo is installed from deb. There, trying to write to c.db needs to fail gracefully. -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
