diff options
Diffstat (limited to '')
| -rw-r--r-- | README.md | 15 |
1 files changed, 11 insertions, 4 deletions
@@ -26,14 +26,16 @@ irssi > nixers irc theme mc > midnight commander ui colors mpd > music player daemon setup + mutt > minimal mutt setup ncmpcpp > ncurses mpc++ ui/color settings pacman > pacman colors and progress bar animations + previews > unixporn screenshots ranger > file manager with image previews and z3bra theme ryu-login > ryu ansi art for /etc/issue tty login ssh > remote ssh server keep alive - sys > system automation scripts stalonetray > stand alone tray for daemons sublime > sublime text 2 with greybeard, monokai, and gohu + sys > system automation scripts themes > mod of the cathexis dark theme for gtk/qt/xfce tmux > terminal multiplexer with custom status bar urxvt > sourcerer terminal colors and keyboard settings @@ -43,23 +45,28 @@ ``` #managing -it's been said of every console user: _"you are your dotfiles"_. +in the unix world programs are configured in two different ways, via shell arguments or text based configuration files. programs with have 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 (see [ricers](http://unixporn.net) and [beaners](http://nixers.net)) 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](http://www.gnu.org/software/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. #installing -stow is available for all gnu/linux and most other unix like distributions via your package manager. +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` +or clone it [from source](https://savannah.gnu.org/git/?group=stow) and [build it](http://git.savannah.gnu.org/cgit/stow.git/tree/INSTALL) yourself. #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 **herbstluft** theme use the command: +to install my **herbstluft** theme _greybeard_ use the command: `stow herbstluftwm` |