csquared
People are queasy about pathing
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- Some sort of config/env var that specifies the path, defaulting to the above
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 PYTHONPATH or CLASSPATH or whatever); symlinking in felt non-obvious to me for some reason. But I think that's bikeshedding; ~/checklists seems super easy and a lot less invasive than ~/checkcheckit.
agreed about the uneasiness -- that's why i accept fully qualified paths. this is more of a relic from the check list command, which i'm not even sure is super useful.
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 .checklists is it would be having vim look in .editorconfig instead of .vimrc. Better question - have you worked around this or was this a deal-breaker and let to people not using it?
:+1: 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.