The initial version of this repository was both an exercise in shell scripting and an attempt to unify my dotfiles and configs, which were a mess of copypasta and fickle preferences strewn across work/home and a mix of OS. It has since been converted to use ansible for the installation (for better or worse). The actual configurations and settings are still a work-in-progress...

Yes, there are nice things like geerlingguy/mac-dev-playbook and others that already handle most or even a lot of the required functionality. Aside from an unhealthy dose of NIH need-to-see-under-the-hood, I find that re-implementing things for which I have an actual use to be very instructive.

I don't really expect anyone else to use this directly. Perhaps it's interesting or at least good for a laugh. Definitely assume it will be in flux and possibly destructive.

• The "topic" approach seen in other dotfile collections seems useful, so most things that get symlinked into $HOME live in the packages dir.
• Anything file ending with .symlink is linked as $HOME/.<filename> (this is somewhat a remnant of the original shell scripts).
• All the actual "work" is done within ansible roles/xxxx. This is, admittedly, somewhat less than ideal since it means tracking things in two places.

cd ~
git clone [email protected]:patrickdowling/dotfoibles.git .dotfiles
cd .dotfiles
./system/bootstrap.sh

This is the theory at least. There's some kinks to work out in this process because the brew install isn't active until later.

(optional: setup user.config.yml)

ansible-playbook main.yml -K

My main projects directory has ended up as ~/dev. Perhaps not the best choice but oh well :)

• This is basically a placeholder for aliases.
• The zsh completions are now installed by roles/zsh.
• Eventually this might just be merged with other things (or, use an existing zsh plugin).
• For "work" scenarios replace docker with containerd/nerdctl and/or colima

• aliases are defined by packages in a packages/package/package-aliases.zsh file.

• Creates some local config files
• $HOME/.gitconfig.local with user.name and user.email is created if the variables are set (e.g. in user.config.yml)

• neovim configuration has been ported to lua; .vimrc is in limbo (see below).

• Needs work ;)
• Installed in .local/share/themes ($DOT_THEMES environment variable)
• There's a zsh function dot_themes_update that updates the repositories (or, just use the playbook again).

• There's still a lot of interdependency between packages, so zsh startup requires themes, the directory structure has to match, etc. This might be templatized.
• So while it's theoretically possible to use tags to install a subset of things, that's not currently recommened.

• Use homebrew? Remember to update .zshenv.local with eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"

• zsh: Key bindings
• zsh: Local aliases file
• .clang-format, .clang-tidyet al templates
• .editorconfig
• makefile et al templates
• shellcheck
• Generate local config files automatically similarly to .gitconfig.local

• Convert init.vim to Lua
• Lua style/formatting -> should be convered with neodev
• Completions -> preliminary config seems to work
• clang-format, clang-tidy templates (possible duplicate from above)
• Basic .vimrc as fallback?
• Snippets. luasnip is currently configured as a plugin and works, but not many snippets (yet?).

• Fonts & things?
• python, pip etc.
• asdf or similar
• https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html