From 96b8abf1cb7ff006b3f63d50ad19c89ad4193dcc Mon Sep 17 00:00:00 2001 From: Jim Myhrberg Date: Wed, 25 Apr 2012 00:59:57 +0100 Subject: [PATCH] Update readme --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 012b0ac..3c58aa4 100644 --- a/README.md +++ b/README.md @@ -101,15 +101,15 @@ export TMUXIFIER_NO_COMPLETE=1 ## Tmuxifier vs. Tmuxinator Though Tmuxifier is largely inspired by the excellent [Tmuxinator][] project, -it does set itself apart in a number of ways: +but does set itself apart in a number of ways: - Uses shell scripts to define Tmux sessions and windows instead of YAML files. The benefit is total control over Tmux, but the definition files are more complicated to work with. - Instead of using a "project" concept, Tmuxifier uses a concept of "sessions" - and "windows". This allows you to load a whole session with multiple - pre-defined window configurations, or just load a single window - configuration into your existing session. + and "windows" just like Tmux itself. This allows you to load a whole session + with multiple pre-defined window configurations, or just load a single + window configuration into your existing session. - Tmuxifier is a set of shell scripts, meaning it doesn't require Ruby to be installed on the machine.