From 9f4b26c0c569e7db69b7e27a9d92c7c26a548aaa Mon Sep 17 00:00:00 2001 From: Travis Tilley Date: Mon, 31 Dec 2012 18:26:35 -0500 Subject: [PATCH] Update README.rdoc correct a few things --- README.rdoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/README.rdoc b/README.rdoc index 7724680..2938075 100644 --- a/README.rdoc +++ b/README.rdoc @@ -7,9 +7,8 @@ Very simple & usable Mac OSX FSEvents API - RubyCocoa not required! - Signals are working (really) -- Tested on MRI 1.8.7 & 1.9.2, JRuby 1.6.3 +- Tested on MRI 1.8.7 & 1.9.3, RBX 2.0.0dev, JRuby - Tested on 10.6 & 10.7 (though 10.5 should work just as well) -- Tested with XCode 3.2.6, 4.0.2, 4.1, 4.2b5 == Install @@ -125,7 +124,7 @@ WARNING: passing in 0 as the parameter to :since_when will return events for eve == Debugging output -If the gem is installed with the environment variable FWDEBUG set to the string "true", then fsevent_watch will be built with its various DEBUG sections defined, and the output to STDERR is truly verbose (and hopefully helpful in debugging your application and not just fsevent_watch itself). If enough people find this to be directly useful when developing code that makes use of rb-fsevent, then it wouldn't be hard to clean this up and make it a feature enabled by a commandline argument instead. Until somebody files an issue, however, I will assume otherwise. +If the gem is re-compiled with the environment variable FWDEBUG set, then fsevent_watch will be built with its various DEBUG sections defined, and the output to STDERR is truly verbose (and hopefully helpful in debugging your application and not just fsevent_watch itself). If enough people find this to be directly useful when developing code that makes use of rb-fsevent, then it wouldn't be hard to clean this up and make it a feature enabled by a commandline argument instead. Until somebody files an issue, however, I will assume otherwise. append_path called for: /tmp/moo/cow/ resolved path to: /private/tmp/moo/cow