d

---

A dotfile manager.

Features

• NOT "SUCKLESS" (IF YOU HAVE TO CONVINCE ME THAT YOUR SOFTWARE "SUCKS LESS", THEN IT ACTUALLY SUCKS!)
• NO "CONFIGURATION FILES" (THE CONCEPT OF "CONFIGURATION FILES" SHOULD NOT EXIST!)
• NO "DOCUMENTATION" (WHAT IS THAT?)
• NOT WRITTEN IN RUST (NO, I'M NOT INSANE!)

Summary

On a more serious note, d is your standard dotfile manager, with the twist that it can be configured using C, hopefully leveraging the cursed amazing C preprocessor.

Usage

git clone [email protected]:hyperupcall-experiments-incubating/d
cd ./d
./bake build "$HOME/.dotfiles/config"
ln -s "$PWD/d" "$HOME/.local/bin/d"

Your CONFIG_FILE (see Bakefile.sh) should have a file dotfiles.c that looks something like:

struct Entry {
	char const *category;
	char const *source;
	char const *destination;
};
#define Done { \
	.category = NULL, .source = NULL, .destination = NULL \
}

static struct Entry bash[] = {
	{
		.category = "bash"
		.source = "/home/edwin/.dotfiles/.bashrc",
		.destination = "/home/edwin/.bashrc"
	},
	Done
};

struct Entry *configuration[] = {
	bash,
	NULL
};

Note the configuration object; d will manage all entries contained within it.

The really cool part about this, is that you can use macros. If you don't like macros, then maybe this software isn't for you. For an example, see my own dotfiles.c. Later I'll probably support some sort of get_configuration() to allow the use of runtime shenanigans.

Now, you can use d like any other dotfile manager:

$ d deploy
$ d undeploy
$ d print