[PATCH 2/2] Updated doc

[Aurélien Gâteau]

---
 README.markdown |   21 ++++++++++++++++++---
 1 files changed, 18 insertions(+), 3 deletions(-)

diff --git a/README.markdown b/README.markdown
index cc1eb7a..1a6862e 100644
--- a/README.markdown
+++ b/README.markdown
@@ -127,7 +127,21 @@ detailed documentation of a command with `help <command>`.
 
 # Advanced stuff
 
-You can define due date for your tasks with `t_due`. This can be done with a relative or absolute date:
+## Quick access to last task
+
+When you execute multiple commands on the same task, you can use `_` as a shortcut to the last task id. Assuming you created a task like this:
+
+    yokadi> t_add home Buy chocolate
+    Added task 'Buy chocolate' (id=1069)
+
+Then the following commands are equivalents (until you work on another task):
+
+    yokadi> t_edit 1069
+    yokadi> t_edit _
+
+## Due dates
+
+You can define due dates for your tasks with `t_due`. This can be done with a relative or absolute date:
 
     yokadi> t_due 21 +3d
     Due date for task 'Buy chocolate' set to Sat Jul 11 17:16:20 2009
@@ -135,9 +149,11 @@ You can define due date for your tasks with `t_due`. This can be done with a rel
     yokadi> t_due 21 23/07 10:30
     Due date for task 'Buy chocolate' set to Thu Jul 23 10:30:00 2009
 
-Due dates are show by `t_list`. Due date is colored according to time left. If you want to be reminded when a task
+Due dates are shown by `t_list`. Due date is colored according to time left. If you want to be reminded when a task
 is due, you can use the Yokadi Daemon for that. See below for details.
 
+## Periodic tasks
+
 If you have periodic tasks, you can tell it to yokadi with `t_recurs`:
 
     yokadi>t_recurs 1 weekly monday 21:30
@@ -147,7 +163,6 @@ If you have periodic tasks, you can tell it to yokadi with `t_recurs`:
 
 Type `help t_recurs` to see all possible syntax
 
-
 # Integration
 
 ## Database location
-- 
1.6.3.3


--------------000900090400070006070805--