-
Notifications
You must be signed in to change notification settings - Fork 7
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
People are queasy about pathing #6
Comments
I think either works, and I'd be pretty happy with either option. I think what I was expecting when I first tried it out was some sort of "search path" (a la |
agreed about the uneasiness -- that's why i accept fully qualified paths. this is more of a relic from the |
where are you guys on this? i thought it made sense to name it after the tool for simplicity and namespacing. The way I think of |
👍 on your thought process there. My main interest is to keep the checklists in a .-prefixed directory to keep it from polluting my homedir. As an example, vim config is in ~/.vim, and I believe pow and ruby-version also keep things out of the way in .-prefixed dirs. The path thing is interesting but I'm sure the only reason people want to redefine it is to just get it out of homeroot. All that said, I don't believe this was a dealbreaker, or at least I haven't heard any feedback to that effect. |
Spoke with some potential checkcheckit users and there were concerns about having to store checklists in
~/checkcheckit
. What's the more standard way to handle this these days?A few random ideas:
~/.checklists
The text was updated successfully, but these errors were encountered: