I used to have some really details configs for vim and zsh. Then I started using fish, spacemacs and magit and really don't have a very customized environment anymore. And I'm happier with this. So, find what thou wilt.
Items of Interest
The beauty of my dot-spacemacs file isn't anything in the file, rather what's not in the file and rather is a part of spacemacs itself, through the power of spacemacs's config-layer system.
After years of using zsh with a cargo-culted configuration, I gave up on it and switched to the Friendly Interactive Shell, aka fish. It has a simplified scripting language, has sane defaults, and straightforward auto-complete features. There's not much to see in the config file, because fish doesn't believe in configurability.
Before I started using Magit, I got to know the git command line pretty well, and got really into creating custom aliases. Here are a few:
commit --amendafter an accidental
commit -amendand instead of
--amendthat took an hour to undo, I started this list.
log -S<term>searches your git history for term
cleanup: removes all local branches merged into HEAD
cleanup-remotes: removes all remote branches merged into HEAD.
delete <remotename> <branchname>: Deletes branch from remote
merge --no-fftakes some branches and merges them in, keeping their full branch and commit history.
reset --hard <refspec>hard resets to the given refspec
tag -acreates an annotated tag, for versioning or such
diff --cacheddisplays the contents of the index
tag-release: Creates an unannotated tag named
release/YYYY/MM/DD/HHMM. Preferably, your build tools do this instead.
track <remote refspec>:
checkout -t <remote refspec>checks out a remote branch as a local branch and sets tracking.
reset --soft HEAD^Revert a commit, but leave its contents as staged.
reset HEAD -- <path>removes
pathfrom the index
remote update --prunefor each remote, fetches and prunes.
I am in the process of migrating the automated install of this to bork and their configurations are in the install directory. Eventually there will be a compiled borkfile when I get around to writing that feature of Bork, and then a command to copy & paste and run, letting the computer work while you get coffee.