βββββββ ββββββ βββββββββ βββββββββ βββ ββββββ ββββββ
ββββ βββββββ ββββ βββ βββββ βββββββββ ββ β βββ β
βββ ββββββ ββββ ββββ βββββββ βββββββββ ββββ β ββββ
ββββ ββββ ββββ ββββ β ββββ βββββββββ βββ β β βββ
βββββββ β βββββββ ββββ β ββββ ββββββββββββββββββββββββββββ
βββ β β ββββββ β ββ β β ββ β βββ βββ ββ ββ βββ β β
β β β β β ββ β β β ββ β β β β β ββ ββ β β
β β β β β β β β β β β β β β β β β β
β β β β β β β β β
β
β¨ Dorian's Dotfiles β¨
Thanks for dropping by!
This is my personal collection of configuration files.
Here are some details about my setup:
- OS: Pop!_OS / macOS
- DE: Gnome
- WM: Mutter
- Shell: zsh
- Editor: Neovim
- utilizes the built-in lsp β€οΈ
- nvim-cmp β autocompletion
- tree-sitter
- tokyonight β color theme
- telescope β fuzzy finder
- lualine.nvim β status line
- bufferline
- Browser: Firefox
- Terminal: Alacritty
- Term Prompt: Powerlevel10k
- Terminal Multiplexer: Tmux
Feel free to "steal" anything you want, and if you have a question please open an issue.
Dependencies
The goal is to have all dependencies for the config automatically installed with the setup script. More details can be found by reading the following files:
- setup.sh
- For mac: Brewfile
- For linux: debian-setup.sh
- installer.rb
Gotchas for NeoVim setup:
- requires fd >= 8.4 (install from brew)
- Tools such as formatters, LSPs, linters are automatically installed via
:Mason
, if one of the deps is not installing make sure to open:Mason
to see the full error message. - Make sure to run
:checkhealth
to know if you are missing anything
Installation
Easy..
git clone [email protected]:dkarter/dotfiles.git
Cd into the dotfiles dir: cd dotfiles
./setup.sh
I don't recommend using other people's dotfiles, at least not when you're just starting with Vim.. these are customized to my personal taste and preferences, and are subject to change at any time. Instead consider forking kickstart.nvim, which is modern and very minimal, and using it as your base to build upon.
Ended up cloning anyway?
My dotfiles are now automatically versioned and contain a Changelog! The main branch will be continuously updated, and you can use git tags to check out specific versions.
β οΈ notice how I said automatically version and not semantically versioned. While I do try to keep a good git hygiene, and the versioning script follows conventional commits to determine the semantic version, I may still introduce a breaking change without a warning (these are my personal dotfiles after all :). The best course of action might be to have an independent fork and follow the changelog.
Releases and versioning is done using Release Please, GitHub Actions, and Conventional Commits
Development
- This repo now uses conventional commits. To install the git hooks simply run
yarn
in the project directory - To start development use airmux (alias
mux
) inside the project directory