From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: Document that a,c,m glob qualifiers can handle time in seconds
Date: Sat, 5 Jun 1999 08:31:54 +0000 [thread overview]
Message-ID: <990605083154.ZM6305@candle.brasslantern.com> (raw)
In-Reply-To: <199906040948.LAA03209@beta.informatik.hu-berlin.de>
On Jun 4, 11:48am, Sven Wischnowsky wrote:
} Subject: Re: MAIL, MAILPATH and maildir support
}
} > --- maybe (ms???) should work too, but it doesn't at the moment);
}
} Now that's a weird omission. Why didn't I... (computers were slower at
} that time, but...)
Here's documentation for that change.
Index: Doc/Zsh/expn.yo
===================================================================
@@ -1380,21 +1380,21 @@
item(tt(g)var(id))(
like tt(u)var(id) but with group IDs or names
)
-item(tt(a)[tt(Mwhm)][tt(-)|tt(PLUS())]var(n))(
-files accessed exactly var(n) days ago. Files accessed within the
-last var(n) days are selected using a negative value for var(n)
-(tt(-)var(n)). Files accessed more than var(n) days ago are selected by a
-positive var(n) value (tt(PLUS())var(n)). Optional unit specifiers `tt(M)',
-`tt(w)', `tt(h)' or `tt(m)' (e.g. `tt(ah5)') cause the check to be
-performed with months (of 30 days), weeks, hours, or minutes instead of
-days, respectively. For instance, `tt(echo *(ah-5))' would echo files
-accessed within the last five hours.
+item(tt(a)[tt(Mwhms)][tt(-)|tt(PLUS())]var(n))(
+files accessed exactly var(n) days ago. Files accessed within the last
+var(n) days are selected using a negative value for var(n) (tt(-)var(n)).
+Files accessed more than var(n) days ago are selected by a positive var(n)
+value (tt(PLUS())var(n)). Optional unit specifiers `tt(M)', `tt(w)',
+`tt(h)', `tt(m)' or `tt(s)' (e.g. `tt(ah5)') cause the check to be
+performed with months (of 30 days), weeks, hours, minutes or seconds
+instead of days, respectively. For instance, `tt(echo *(ah-5))' would
+echo files accessed within the last five hours.
)
-item(tt(m)[tt(Mwhm)][tt(-)|tt(PLUS())]var(n))(
+item(tt(m)[tt(Mwhms)][tt(-)|tt(PLUS())]var(n))(
like the file access qualifier, except that it uses the file modification
time.
)
-item(tt(c)[tt(Mwhm)][tt(-)|tt(PLUS())]var(n))(
+item(tt(c)[tt(Mwhms)][tt(-)|tt(PLUS())]var(n))(
like the file access qualifier, except that it uses the file inode change
time.
)
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
prev parent reply other threads:[~1999-06-05 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-04 9:48 MAIL, MAILPATH and maildir support Sven Wischnowsky
1999-06-05 8:31 ` Bart Schaefer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=990605083154.ZM6305@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).