Add export action, fix util_is_link bug

1 files changed, 15 insertions, 4 deletions

diff --git a/README.org b/README.org
index 756ed3a..fb15d30 100644
--- a/README.org
+++ b/README.org
@@ -5,16 +5,16 @@
 
 Have you ever wondered:
 #+BEGIN_QUOTE
- "Jeez Luiz, how can I manage all my configs across my desktop and server?"
+ "Jeez Luise, how can I manage all my configs across my desktop and server?"
 
- -- You
+                -- You
 #+END_QUOTE
 
 or maybe:
 #+BEGIN_QUOTE
  "How can I possibly keep all my configs in sync across computers?"
 
- -- You again
+                -- You again
 #+END_QUOTE
 
 *ck* is the solution you've been looking for all your life.
@@ -33,6 +33,9 @@ and instruct it to save them in a different folder, so they won't be in the
 same place with the normal ones (in the event you want to share your configs
 with the rest of us).
 
+You can even export all *ck* data with the =export= action. This will create a
+=.tar.gz= file.
+
 ** Technicalities
 Upon adding a config to *ck*, it moves it to the specified folder and adds a symbolic link
 back where it came from (=ln -s=).
@@ -126,6 +129,12 @@ go to the build directory and type:
 #+BEGIN_SRC sh
 $ ./test-ck
 #+END_SRC
+Or if you want to run a particular regression test use the filter option
+#+BEGIN_SRC sh
+$ ./test-ck -f add
+#+END_SRC
+This will match any test scrits with =add= in their name.
+
 
 *** test suite
 #+BEGIN_SRC sh
@@ -136,8 +145,10 @@ use without flags to run all tests
 flags:
   -u, --unit            run only the unit tests
   -r, --regression      run only the regression tests
+  -f, --filter  run regression test matching the argument
   -c, --clear           remove test files
-             		 use if the tests crush unexpectedly
+                         use if the tests crush unexpectedly
+  -v, --verbose         verbose test output
   -h, --help, *         print this
 #+END_SRC
 * ck configuration