Move config file to ~/.config/didrc about did HOT 7 CLOSED

I see the point. But I'm a little bit hesitant to do this change as the plan is to include more data in that directory: Plugins subdirectory to allow custom user plugins, data for the local log plugin and possibly others. They do not fit all under the config umbrella. Plus it makes sense to keep them nicely together as they are closely related.

from did.

I also don't see a strong reason to move to ~/.config or ~/.local

On Wed, Sep 23, 2015 at 12:21 PM, Petr Šplíchal [email protected]
wrote:

I see the point. But I'm a little bit hesitant to do this change as the
plan is to include more data in that directory: Plugins subdirectory to
allow custom user plugins, data for the local log plugin and possibly
others. They do not fit all under the config umbrella. Plus it makes sense
to keep them nicely together as they are closely related.

—
Reply to this email directly or view it on GitHub
#43 (comment).

from did.

I see the point. But I'm a little bit hesitant to do this change as the plan is to include more data in that directory: Plugins subdirectory to allow custom user plugins, data for the local log plugin and possibly others. They do not fit all under the config umbrella. Plus it makes sense to keep them nicely together as they are closely related.

Sure, then what’s wrong with ~/.config/did/ directory? I think putting non-config file there is not that big heresy (of course, they should go in the ideal world to ~/.local/share/did/). Ideal is to use pyxdg, but yes that's additional dependency.

from did.

although, the more I think about it... i also don't have strong feelings against it either. It would seem to keep things more organized.

Splitting config to ~/.config/did and non-config stuff to ~/.local/share/did/ seems to add a level of complication that we'd want to avoid; seems more effort than it is a bother to just use ~/.did/

Do we want to ever maintain support for non-linux environments? Seems like path decision might impact this... just food for thought though, I haven't had time to chew it. :)

from did.

Do we want to ever maintain support for non-linux environments? Seems like path decision might impact this... just food for thought though, I haven't had time to chew it. :)

The only real advantage of pyxdg package is availability of XDG paths on Windows (or Mac OS X, I don’t know what's the situation there). You really don’t want to deal with those crazy paths on Windows! However, if we don't care about compatibility than just strings ~/.config/did/, ~/.cache/did/ (if we have any cache files), and ~/.local/share/did/ should be enough.

from did.

I don't think it's worth separating the files into two or more directories, I like short paths and I don't find hidden files in home directory in any way obstructing. For those who prefer to keep the home directory clean the DID_CONFIG variable represents an easy way how to use a different location. I've adjusted docs to make this even more straightforward.

from did.

Actually, DID_CONFIG is pretty good for fix, I guess. So, you have really not WONTFIXed it? ;) Thank you

from did.