aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorxero <x@xero.nu>2015-05-22 22:26:31 -0400
committerxero <x@xero.nu>2015-05-22 22:26:31 -0400
commit453134c30f147e21e2d1e507782ef7dc2087b8ef (patch)
tree211fbdc0eb91ffd99c48297da8fc1e4098cae12c
parent2fe74b1ca61a8f7f667bb46369303a22bf872ea4 (diff)
downloaddotfiles_ascii-453134c30f147e21e2d1e507782ef7dc2087b8ef.tar.xz
dotfiles_ascii-453134c30f147e21e2d1e507782ef7dc2087b8ef.zip
update README
Diffstat (limited to '')
-rw-r--r--README.md8
1 files changed, 5 insertions, 3 deletions
diff --git a/README.md b/README.md
index fb0be21..625ddc0 100644
--- a/README.md
+++ b/README.md
@@ -44,13 +44,14 @@
zsh > zshell settings, aliases, and custom prompts
```
-#managing
-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.
+#dotfiles
+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"_.
+> _"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.
+#managing
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
@@ -59,6 +60,7 @@ stow is available for all linux and most other unix like distributions via your
- `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