-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move config file to ~/.config/didrc #43
Comments
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. |
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 notifications@github.com
|
Sure, then what’s wrong with |
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. :) |
The only real advantage of |
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 |
Actually, |
There are lot of dotfiles in $HOME. But more and more projects moved to using ~/.config ~/.local etc directories instead of creating new ones.
Did should follow.
The text was updated successfully, but these errors were encountered: