Everyone needs a dotfiles repo these days.
This now uses
stow to help manage dotfiles in
bash/ is a my bash config scripts:
.bash_profileis usually loaded first for most interactive shells.
.bashrcis initially loaded, and loads other config files.
.bashrc.aliasis a set of aliases that I care about.
.bashrc.localis for local system config, and is omitted.
.bashrc.promptexists purely to set up the bash prompt.
.bashrc.completionis loaded last and sets up all bash completion features.
Config in the
I launch emacs with a convenient little script called
e. Install it with:
ln -s $PWD/emacs/e ~/bin/e chmod +x ~/bin/e
The script checks if there is an emacs server running. If there isn't, it starts one up. Then it connects an
emacsclient to it with the requested file.
Tip: Update emacs packages by blowing them away
Frequently packages in emacs will get out of date or will not be able to be updated from MELPA anymore because the installed version is no longer available. In this case, it should be safe to blow away the directories in
~/.emacs.d/elpa. The only thing I haven't confirmed is that doing this does not lose
The important file in
git/ is the
.gitconfig-aliases file which prepares some of my git aliases.
To have it be sourced, add this to
[include] path = ~/.gitconfig-aliases
stow git in this directory. (Likely,
~/.dotfiles) Local setup of git user, email, etc., is likely done by initial setup.
.tmux.conf file that sets up tmux. Very basic config at this point.
vim/ you'll find files to set up vim, naturally:
.vimrcis the main vim config file. I am using Vundle, so all of the vim bundles that I depend on are listed in the 'Vundle' section in
.vimrc.localis for local vim config and is omitted.
- If you are not running the whole
stowing the vim config into place, check out the commands to install vim-plug and plugins with it in the
- MacOS window mgmt: Raycast built in functionality.
- install/upgrade: vim, emacs, git, tmux, htop, s-tui, tlp
I don't suggest you go using these files without understanding what they do. But if you must, the files get symlinked into position in your home directory from this directory. Their filenames should remain the same. I highly suggest that if you're going to use pieces of this, that you fork this repo into your own GitHub account, at the very least. Then remove what you don't want.
I can't guarantee this will work for you. These are my own config files and highly personalized. As noted below in the license, there is no warranty.
Copyright (c) 2022 Matt Gauger
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.