Re-write readme, rename files

README.md

@@ -1,16 +1,23 @@
-# Tmux Proper Pipe Pane
+# Tmux Logging
 
-Tmux enables easy command logging with `pipe-pane`.
+Features:
+1. Logging of all output in the current pane<br/>
+   After you start logging, everything that's typed and all the output will be
+   saved to a file.
+2. Enables "screen capture" of the current pane<br/>
+   All the text visible in the current pane is saved to a file. Like a
+   screenshot, but textual.
+3. Enables saving a complete history of the current pane<br/>
+   All that has been typed and all the output since the creation of the current
+   pane is saved to a file.
 
-Using "raw" `pipe-pane` has some downsides. This plugin improves the vanilla
-Tmux `pipe-pane` functionality.
+### 1. Logging
 
-### About
+Key binding: `prefix + shift + p`<br/>
+Toggles (start/stop) logging in the current pane.
 
-This plugin brings the following improvements to the Tmux logging
-functionality:
-
-**1. removes ANSI codes from the log**
+Logging improves the default `pipe-pane` logging mechanism by stripping ANSI
+codes.
 
 This is how the plain `pipe-pane` log output looks like if you're using
 terminal with coloring:
@@ -21,56 +28,63 @@ Garbled characters are called ANSI codes. They enable colors in terminal, but
 are just making 'noise' in the textual log output.
 
 A user will probably want to filter ANSI codes out of the log. Here's the same
-log as above when using `tmux_ppp`:
+log as above when using this plugin:
 
-![tmux_ppp log output](/screenshots/tmux_ppp_log_output.png)
+![proper log output](/screenshots/proper_log_output.png)
 
-**2. single key binding toggles logging start/stop**
+### 2. "Screen capture"
 
-[This post on stackexchange](http://unix.stackexchange.com/a/10259) describes
-how to setup key bindings for logging with `pipe-pane`. There are 2 options:
-- setup a single key binding that toggles logging.<br/>
-  Downside: a user doesn't know if the toggle key started or stopped logging.
-  There's just the message `Logging is toggled`.
-- in order to properly setup messages for `Starting` and `Ending` logging, 2
-  key bindings have to be used.<br/>
-  Downside: with so many Tmux key bindings, it is easily forgotten which key
-  starts and which one ends logging.
+Key binding: `prefix + alt + p`<br/>
+Visible text in the current pane is saved to a file. Equivalent of a "texual
+screenshot".
 
-`tmux_ppp` solves above inconveniences by enabling:
-- a single key binding that toggles `pipe-pane` logging.
-- proper notifications, so it's clear whether the logging was started or
-  stopped when a key was pressed.
+File path: `$HOME`<br/>
+File name: `$HOME`<br/>
+
+### 3. Capture complete pane history
+
+Key binding: `prefix + alt + shift + p`<br/>
+Saves complete pane scrollback to a file. Convenient if you remember you need
+the log of all the work retroactively.
+
+NOTE: this functionality depends on the value of `history-limit` - it
+determines the number of lines Tmux keeps in the scrollback buffer. Everything
+that Tmux kept will also be saved to a file.
+
+With modern computers it is safe to set this option to a high number:
+
+    # in .tmux.conf
+    set -g history-limit 50000
 
 ### Installation with [Tmux Plugin Manager](https://github.com/bruno-/tpm) (recommended)
 
 Add plugin to the list of TPM plugins in `.tmux.conf`:
 
-    set -g @tpm_plugins "   \
-      bruno-/tpm            \
-      bruno-/tmux_ppp       \
+    set -g @tpm_plugins "       \
+      bruno-/tpm                \
+      bruno-/tmux_logging       \
     "
 
 Hit `prefix + I` to fetch the plugin and source it.
 
-You should now have `tmux_ppp` key binding defined.
+You should now have all `tmux_logging` key bindings defined.
 
 ### Manual Installation
 
 Clone the repo:
 
-    $ git clone https://github.com/bruno-/tmux_ppp ~/clone/path
+    $ git clone https://github.com/bruno-/tmux_logging ~/clone/path
 
 Add this line to the bottom of `.tmux.conf`:
 
-    run-shell ~/clone/path/proper_pipe_pane.tmux
+    run-shell ~/clone/path/logging.tmux
 
 Reload TMUX environment:
 
     # type this in terminal
     $ tmux source-file ~/.tmux.conf
 
-You should now have `tmux_ppp` key binding defined.
+You should now have all `tmux_logging` key bindings defined.
 
 ### Installing `ansifilter` (recommended for OSX users)
 
@@ -80,39 +94,14 @@ is a program specialized for removing (or working with) ANSI codes.
 If you're on OSX, it is recommened to install `ansifilter`:
 `$ brew install ansifilter`
 
-If you're on Linux (or don't have `ansifilter` installed), `tmux_ppp` removes
-ANSI codes with `sed` regexes. That should work fine, but please
-[open an issue](https://github.com/bruno-/tmux_ppp/issues) if you find a
-problem.
-
-### Usage
-
-This plugin defines `prefix + P` key binding (note, that is uppercase `P`).
-
-Press `prefix + P` to start logging. Message is show with the path to log file:
-
-    Started logging to /Users/bruno/tmux-ppp-0-1-20140526T141437.log
-
-To end logging, also press `prefix + P`. You'll get a notification:
-
-    Ended logging to /Users/bruno/tmux-ppp-0-1-20140526T141608.log
-
-### Log file name
-
-New logs are created in `$HOME` directory by default.
-
-Log file name tries hard to be 'unique'. A user can log all panes in all
-sessions in tmux simultaneously without having log file conflicts.
-
-For better understanding, here's the file name "template":
-
-    "tmux-#{session_name}-#{window_index}-#{pane_index}-%Y%m%dT%H%M%S.log"
+It helps with removing ANSI codes from the log. If `ansifilter` is not present,
+ANSI codes are removed with `sed`.
 
 ### Credits
 
 Thanks to Chris Johnsen for providing
 [this answer on stackexchange](http://unix.stackexchange.com/a/10259).
-`tmux_ppp` is based on insights from that post.
+This plugin started as an improvement of bindings from that answer.
 
 ### License