back

by gurjeet·3y ago·view on hn ↗
Here's a proposal I have developed to solve the same problem: https://www.toolsconfig.org/

The onus is on the tools developers to adopt this change. And the proposal allows for the gradual, graceful migration from current status to a place where all such files are stored in a central location.

The directory name `.toolsconfig`, or `.tc` is the best I could recommend, since `config` or `.config` can be safely assumed to be already in use. Using 'tools' in the directory name also makes it explicit as to whose config files are stored in there; tools developers use, not the config of the projecct itself.

Edit: The Git repo of the proposal is hosted on Github. Feel free to propose any changes or improvements to the proposal or the algorithm.

https://github.com/DrPostgres/ToolsConfig/ https://www.toolsconfig.org/

2 comments
I don't like "tc" because it is not self-explanatory and somewhat cryptic to me. The argument on name collisions is valid, although even "toolsconfig" is not 100 % safe.
Great proposal!