Better list

1 files changed, 16 insertions, 2 deletions

diff --git a/README.org b/README.org
index 446ff02..c03a093 100644
--- a/README.org
+++ b/README.org
@@ -112,6 +112,7 @@ Example usage:
   $ ck list tree
   $ ck list paths -t lisp
   $ ck list programs -t python
+  $ ck list -p emacs
 
   # search the configs
   $ ck search search-term
@@ -200,7 +201,12 @@ Usage:
 *** list
 or ls or l or -l
 
-List can show the *paths* or the *programs* that ck keeps track of.
+List stuff ck knows about.
+
+You can use the keywords:
+- *paths*: to print all the paths ck tracks
+- *programs*: to print all the programs ck tracks
+- *-p progName*: (without the "<>") to print the paths of a specific program
 
 With the flag *-t* and then one of the follwing types one can change
 the way the list is printed:
@@ -209,11 +215,13 @@ the way the list is printed:
 - *lisp*: print like a lisp list
 
 Using the keyword *tree* ck can list the configurations under their
-corresponding program.
+corresponding program, in a treelike structure.
 
 Passing the *-a* flag will enable the listing of config attributes (secret or primary). 
 It is best used with tree or plain paths.
 
+With the keyword *ckconf* ck will list it's own configuration values (in ckrc).
+
 Usage:
 #+BEGIN_SRC sh
   # list tree structure, with attributes
@@ -222,6 +230,12 @@ Usage:
   $ ck l paths -t python
   # list programs in lisp
   $ ck ls programs -t lisp
+  # list emacs' configurations [with attributes]
+  $ ck ls -p emacs [-a]
+  # list bash configurations in lisp
+  $ ck ls -p bash -t lisp
+  # list ck configuration
+  $ ck -l ckconf
 #+END_SRC
 
 *** search