summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormg <>2008-11-07 11:57:46 +0000
committermg <>2008-11-07 11:57:46 +0000
commit2c5a5e969f26e37d0b3555eedbb874f1ad85a1a6 (patch)
tree6871151947663f3637663c18f02480f730f8679e
parent828c32de3d1f3f6a66426b703b5c5f0a0da1aea5 (diff)
Documentation for the time/offset feature.
Appied patch from Chris Beaven.
-rw-r--r--README.txt27
1 files changed, 16 insertions, 11 deletions
diff --git a/README.txt b/README.txt
index 9c56f01..e2ef8dc 100644
--- a/README.txt
+++ b/README.txt
@@ -47,17 +47,22 @@ Report. A mail program (Mutt in a terminal, unless you have changed it in
~/.gtimelog/gtimelogrc) will be started with all the activities listed in it.
My Mutt configuration lets me edit the report before sending it.
-If you make a mistake and type in the wrong activity name, or just forget to
-enter an activity, don't worry. GTimeLog stores the time log in a simple plain
-text file ~/.gtimelog/timelog.txt. Every line contains a timestamp and the
-name of the activity that was finished at the time. All other lines are
-ignored, so you can add comments if you want to -- just make sure no comment
-begins with a timestamp. You do not have to worry about GTimeLog overwriting
-your changes -- GTimeLog always appends entries at the end of the file, and
-does not keep the log file open all the time. You do have to worry about
-overwriting changes made by GTimeLog with your editor -- make sure you do not
-enter any activities in GTimeLog while you have timelog.txt open in a text
-editor.
+If you forget to enter an activity, you can start your activity with a 24h
+time ("09:30 morning meeting") or a minute-offset ("-10 morning meeting").
+Note that the new activity must still be after the last entered event. The
+time/offset will be removed from the description of the activity before it's
+entered.
+
+If you make a mistake and type in the wrong activity name, don't worry.
+GTimeLog stores the time log in a simple plain text file
+~/.gtimelog/timelog.txt. Every line contains a timestamp and the name of the
+activity that was finished at the time. All other lines are ignored, so you
+can add comments if you want to -- just make sure no comment begins with a
+timestamp. You do not have to worry about GTimeLog overwriting your changes
+-- GTimeLog always appends entries at the end of the file, and does not keep
+the log file open all the time. You do have to worry about overwriting
+changes made by GTimeLog with your editor -- make sure you do not enter any
+activities in GTimeLog while you have timelog.txt open in a text editor.
If you want a more visual idea of how you spend your time you can export the
"Work/Slacking stats" to a spreadsheet and graph them. You get 4 values per