about summary refs log tree commit diff
path: root/Doc
diff options
context:
space:
mode:
authorPeter Stephenson <pws@users.sourceforge.net>2006-12-04 10:59:10 +0000
committerPeter Stephenson <pws@users.sourceforge.net>2006-12-04 10:59:10 +0000
commit7960ae5d4c057d28f67263dc547d84e3ea8e06fc (patch)
tree1252b6aedbdb39c30ae225b1141744ff45d1c1d9 /Doc
parent34381548da094d1be0b06f802d131f960b061ffe (diff)
downloadzsh-7960ae5d4c057d28f67263dc547d84e3ea8e06fc.tar.gz
zsh-7960ae5d4c057d28f67263dc547d84e3ea8e06fc.tar.xz
zsh-7960ae5d4c057d28f67263dc547d84e3ea8e06fc.zip
Vin Shelton: 23027: typo in calsys.yo
unposted: missing autoload in calendar_add, improve age date shortcuts
Diffstat (limited to 'Doc')
-rw-r--r--Doc/Zsh/calsys.yo35
1 files changed, 31 insertions, 4 deletions
diff --git a/Doc/Zsh/calsys.yo b/Doc/Zsh/calsys.yo
index 543bf0935..b2196e448 100644
--- a/Doc/Zsh/calsys.yo
+++ b/Doc/Zsh/calsys.yo
@@ -172,8 +172,17 @@ in the list above.  Otherwise, a time is only recognised as being
 associated with a date if there is only whitespace in between, or if the
 time was embedded in the date.
 
-Days of the week are not scanned, but will be ignored if they occur
-at the start of the date pattern only.
+Days of the week are not normally scanned, but will be ignored if they
+occur at the start of the date pattern only.  However, in contexts where it
+is useful to specify dates relative to today, days of the week with no
+other date specification may be given.  The day is assumed to be either
+today or within the past week.  Likewise, the words tt(yesterday),
+tt(today) and tt(tomorrow) are handled.  All matches are case-insensitive.
+Hence if today is Monday, then tt(Sunday) is equivalent to tt(yesterday),
+tt(Monday) is equivalent to tt(today), but tt(Tuesday) gives a date six
+days ago.  This is not generally useful within the calendar file.
+Dates in this format may be combined with a time specification; for
+example tt(Tomorrow, 8 p.m.).
 
 For example, the standard date format:
 
@@ -379,7 +388,20 @@ directly as command or arguments, or separately as shell parameters.
 example(print *+LPAR()e:age 2006/10/04 2006/10/09:+RPAR())
 
 The example above matches all files modified between the start of those
-dates.
+dates.  The second argument may alternatively be a relative time
+introduced by a tt(PLUS()):
+
+example(print *+LPAR()e:age 2006/10/04 +5d:+RPAR())
+
+The example above is equivalent to the previous example.
+
+In addition to the special use of days of the week, tt(today) and
+tt(yesterday), times with no date may be specified; these apply to today.
+Obviously such uses become problematic around midnight.
+
+example(print *+LPAR()e-age 12:00 13:30-+RPAR())
+
+The example above shows files modified between 12:00 and 13:00 today.
 
 example(print *+LPAR()e:age 2006/10/04:+RPAR())
 
@@ -508,6 +530,11 @@ In addition to setting tt(REPLY), set tt(REPLY2) to the remainder of
 the argument after the date and time have been stripped.  This is
 empty if the option tt(-A) was given.
 )
+item(tt(-t))(
+Allow a time with no date specification.  The date is assumed to be
+today.  The behaviour is unspecified if the iron tongue of midnight
+is tolling twelve.
+)
 enditem()
 )
 )
@@ -526,7 +553,7 @@ command tt(xmessage) to display a window with the event details.
 )
 enditem()
 
-texinode(Calendar Bugs)(Calendar Utility Functions)()(Calendar Function System)
+texinode(Calendar Bugs)()(Calendar Utility Functions)(Calendar Function System)
 sect(Bugs)
 
 There is no tt(calendar_delete) function.