Replies: 3 comments
-
Nice initiative! More related resources: |
Beta Was this translation helpful? Give feedback.
0 replies
-
woah i'm famous! 🕺🪩 PS I wasn't "convinced" I settled for it 😂 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Love this!! I threw together a silly package to let me (sorta) use a config dir a while back, it just lets you create/destroy symlinks for stuff, but it's something ig: https://github.com/nicolehollant/move-stuff 😅 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Note
Here is a collection of inspirations collected from different sources.
See
.config
dir support tracker for a list of tools and config loaders that support.config/
dir or might do.How it started
A few months ago, I was inspired by seeing tweet by @danawoodman about this problem a few months ago and while he was
convincedsettled to use file nesting, the real problem still exists with actual files not being organized. Finally, when I was dealing with this problem again when building a minimal documentation tool, I decided to push it again!Relavant
Media
XDG Spec
XDG uses
~/.config
as a standard dir (while it allows to be overridden, it may not be feasible for this proposal: discussion).dot-config
(thanks @webpro for reference)
dot-config is a previous effort to push the
.config/
idea by @ssbarnea.proload
(thanks @webpro for reference)
preload by @natemoo-re is another configuration loader that supports
config/
dir. (see alternative directory names discussion.)There is an open issue proposing to also support
.config
directory.Discussions in
nodejs/tooling
(thanks @webpro for reference)
Deno
(thanks to @t3dotgg for reference)
@lambtron in an Article mentioned about all the pain about current configuration files and the value of having best defaults that work out of the box.
Beta Was this translation helpful? Give feedback.
All reactions