▗▖ ▄▄ █ ▗▄▖ ▐▌ ▐▌ ▐▛▀ ▀ ▝▜▌ ▟█▟▌ ▟█▙ ▐███ ▐███ ██ ▐▌ ▟█▙ ▗▟██▖ ▐▛ ▜▌▐▛ ▜▌ ▐▌ ▐▌ █ ▐▌ ▐▙▄▟▌▐▙▄▖▘ ▐▌ ▐▌▐▌ ▐▌ ▐▌ ▐▌ █ ▐▌ ▐▛▀▀▘ ▀▀█▖ ▝█▄█▌▝█▄█▘ ▐▙▄ ▐▌ ▗▄█▄▖ ▐▙▄ ▝█▄▄▌▐▄▄▟▌ ▝▀▝▘ ▝▀▘ ▀▀ ▝▘ ▝▀▀▀▘ ▀▀ ▝▀▀ ▀▀▀ i3-gaps > Advanced Tiling Windows Manager bin > System Automation Scripts compton > minimal composite config for opacity figlet > custom 3d font fonts > configs for gohu and other bitmap fonts fun > term color, sys info, and other misc scripts git > global git config and aliases interrobang > a lightweight application launcher irssi > neon gold irc theme mpd > music player daemon setup mutt > minimal mutt setup ncmpcpp > ncurses mpc++ ui/color settings pacman > pacman colors and progress bar animations pygments > add syntax highlighting to cat and less commands ranger > file manager with image previews and z3bra theme ssh > remote ssh server keep alive themes > mod of the cathexis dark theme for gtk/qt/xfce polybar > Advanced lightweight bar with system tray support tmux > terminal multiplexer with custom status bar urxvt > Lightweight terminal with colors and keyboard settings vim > wizard status bar wallpaper > the cool desktop background images I use zsh > zshell settings, aliases, and custom prompts etc > some customized settings for ssh, X11 and more
table of contents
in the unix world programs are commonly configured in two different ways, via shell arguments or text based configuration files. programs with many options like window managers or text editors are configured on a per-user basis with files in your home directory
~. in unix like operating systems any file or directory name that starts with a period or full stop character is considered hidden, and in a default view will not be displayed. thus the name dotfiles.
it's been said of every console user:
"you are your dotfiles".
since they dictate how your system will look and function. to many users these files are very important, and need to be backed up and shared. people who create custom themes have the added challenge of managing multiple versions of them. I have tried many organization techniques. and just take my word for it when I say, keeping a git repo in the root of your home directory is a bad idea. i've written custom shell scripts for moving or symlinking files into place. there are even a few dotfile managers, but they all seem to have lots of dependencies. I knew there had to be a simple tool to help me.
I manage mine with gnu stow, a free, portable, lightweight symlink farm manager. this allows me to keep a versioned directory of all my config files that are virtually linked into place via a single command. this makes sharing these files among many users (root) and computers super simple. and does not clutter your home directory with version control files.
stow is available for all linux and most other unix like distributions via your package manager.
sudo pacman -S stow
sudo apt-get install stow
brew install stow
how it works
by default the stow command will create symlinks for files in the parent directory of where you execute the command. so my dotfiles setup assumes this repo is located in the root of your home directory
~/dotfiles. and all stow commands should be executed in that directory. otherwise you'll need to use the
-d flag with the repo directory location.
to install most of my configs you execute the stow command with the folder name as the only argument.
to install my i3 files, use the command:
this will symlink files to
~/.config/i3 and various other places.
but you can override the default behavior and symlink files to another location with the
-t (target) argument flag.
note: stow can only create a symlink if a config file does not already exist. if a default file was created upon program installation you must delete it first before you can install a new one with stow. this does not apply to directories, only files.
navigate to your home directory
clone the repo:
git clone https://github.com/SyfiMalik/cfg.git .cfg
enter the dotfiles directory
install the zsh settings
install zsh settings for the root user
sudo stow zsh -t /root
install etc files for X11 (libinput) and ssh
sudo stow etc -t /etc
etc, etc, etc...
I prefer a minimal setup, and choose to interact with my operating system via the so-called "terminal" or "command line", (read that quoting sarcastically) over a gui interface 2 times out of 3. with the web browser and video player among the noted outliers. in my opinion, using your computer should be a very personal experience. your colors, aliases, key-bindings, etc meticulously crafted to your exacting specifications. so for me, the unix shell is the most important part of my environment.
my terminal emulator of choice is the lightweight, unicode, 256 color urxvt. I use zsh as my interactive shell. it's an extensible, bash like shell with awesome completion and correction engines. I manage multiple shell sessions with tmux. it's a feature packed terminal multiplexer with support for buffers, split windows, detached local and remote sessions, etc. i'm a member of the cult of vim. sing phrases to the third reincarnation of the glorious ed! lel. mpd is my music server and I use ncmpcpp as it's frontend.
with it's tight integration to the unix shell, vim has quickly become my editor of choice. once you start to master the movements and operators you quickly begin manipulating, not just editing source code files.
when you learn vim it's best to use a more vanilla config. it helps you focus on learning the editor and not the plugins. vim's vast and powerful plugin system can add many great features. I try to keep my editor slim and fast, but I find myself loving these plugins:
- vundle - to manage other plugins
- vim completes me - super lightweight completion system
- colorizer - display color codes as their colors inline
- syntastic - syntax linting
- git gutter - git diff in the gutter
- match it - extended word and regex matching
- lightline - custom status line (for much rice)
- fugitive - fast git integration