URI: 
       tFixed typos in README - wendy - watch files/directories and run commands on any event
  HTML git clone git://z3bra.org/wendy
   DIR Log
   DIR Files
   DIR Refs
   DIR README
   DIR LICENSE
       ---
   DIR commit 0f99856c19427d5aa8f401fed50873926acfe643
   DIR parent 010a50e899c96c995df263439caad4c3001a0f0b
  HTML Author: z3bra <willy@mailoo.org>
       Date:   Mon, 10 Mar 2014 08:45:09 +0100
       
       Fixed typos in README
       
       Diffstat:
         M README                              |      15 ++++++++-------
       
       1 file changed, 8 insertions(+), 7 deletions(-)
       ---
   DIR diff --git a/README b/README
       t@@ -79,8 +79,8 @@ But you could do something like:
            >    wendy -C -q -f $d -e echo file created in $d &
            > done
        
       -That will spawn one instance of wendy per directory. You could
       -then kill them all using job control or with
       +That will spawn one instance of wendy per directory. You could then kill them
       +all using job control or with
        
            killall wendy
        
       t@@ -89,7 +89,7 @@ then kill them all using job control or with
        > Can you explain why this exists? Doesn't inotifywait (from inotify-tools) do
        > this exact same thing?
        
       -I first started wendy, I was not aware of inotifywait. wendy was just a good
       +When I first started wendy, I was not aware of inotifywait. It was just a good
        programming exercise.
        
        With the time, I found wendy more and more useful, and added a few options to
       t@@ -110,12 +110,12 @@ still prefer using wendy because of this:
            * I like the name 'wendy' better
        
        [1] I'm aware of the '--monitor' flag, but the only way to exec a command with
       -    this is a pain that implies read, a while loop and so on.
       +this is a pain that implies read, a while loop and so on.
        
        [2] In fact, you can, by doing "inotifywait -e <event> && command", and
       -    wrapping it in a while loop. Well, don't forget to add a test to see if
       -    your file still exists, to avoid infinite buggy loops. You'll end up with
       -    something like:
       +wrapping it in a while loop. Well, don't forget to add a test to see if your
       +file still exists, to avoid infinite buggy loops. You'll end up with something
       +like:
        
            while test -e ~/path/to/my/file; do
                inotifywait -e <event> ~/path/to/my/file && command
       t@@ -128,6 +128,7 @@ Good luck with this, I prefer "wendy -m <mask> -e command"
            inotifywait -e access -e create -e delete -e modify -e attrib /path/to/file
        
        I prefer
       +
                wendy -m 774 ~/path/to/my/file
        
        ---