summaryrefslogtreecommitdiff
path: root/calendars.mdwn
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2012-03-31 14:28:17 +0100
committerLars Wirzenius <liw@liw.fi>2012-03-31 14:28:17 +0100
commitf85947dd77b01f76cc4bcfee39a102e455d57d18 (patch)
tree519bbc62cc6ad6d8e97a6ba7b825a6fcdd8bd991 /calendars.mdwn
parentdbc1dca1d3311d2c6169c1b082b72c0b010af570 (diff)
downloadgtdfh.liw.fi-f85947dd77b01f76cc4bcfee39a102e455d57d18.tar.gz
Wording tweaks
Diffstat (limited to 'calendars.mdwn')
-rw-r--r--calendars.mdwn6
1 files changed, 4 insertions, 2 deletions
diff --git a/calendars.mdwn b/calendars.mdwn
index bb7253b..df4f600 100644
--- a/calendars.mdwn
+++ b/calendars.mdwn
@@ -26,7 +26,9 @@ Automatic nagging systems
Another kind of thing is stuff that needs to happen regularly. For
some of these, digital calendars are still the tool of choice: you
could add a bi-monthly reminder to get a haircut to your calendar,
-for example.
+for example. If you get the timing right, your calendar will remind
+you just before your partner does, and you'll both be saved an
+unnecessary discussion.
Calendar reminders may also be replaced or augmented by cron jobs,
which run, for example, on the Monday before the second Thursday
@@ -54,7 +56,7 @@ with you. (This is not a hypothetical example.)
A better solution would remind you twelve days after
the previous time you actually cut the nails, not after the previous
-reminder. Lars has a program called "nagger" which does exactly that,
+reminder. I have a program called "nagger" which does exactly that,
but it is not suitable for others to use (unless you dig editing
`procmailrc` files, and probably not even then). The nagger remembers
when you last did something, and after the specified time, it