From: Vincent Lefevre <vincent@vinc17.org>
To: zsh-workers@sunsite.dk, 185228-forwarded@bugs.debian.org
Subject: Re: [vincent@vinc17.org: Bug#185228: zsh: Incorrect filename generation with glob qualifier mh+]
Date: Mon, 11 Jul 2005 14:17:00 +0200 [thread overview]
Message-ID: <20050711121700.GA16217@dixsept.loria.fr> (raw)
In-Reply-To: <1030318162510.ZM28121@candle.brasslantern.com>
On 2003-03-18 16:25:10 +0000, Bart Schaefer wrote:
> On Mar 17, 10:16pm, Clint Adams wrote:
> } Subject: [vincent@vinc17.org: Bug#185228: zsh: Incorrect filename generati
> }
> } ----- Forwarded message from Vincent Lefevre <vincent@vinc17.org> -----
> }
> } Using the glob qualifier mh+n selects files modified more than
> } n+1 hours instead of more than n hours ago.
> }
> } If this is a feature to make a partition with mh-n, mhn and mh+n,
> } then the wording in the manual should be changed
>
> Unless I'm mistaken, this is all for compatibility with the way that
> "find" defines +n, -n and n. If you ask me, it's always silly to
> define any meaning for "exactly <number> <timeunits> ago"; it always
> means "during the <timeunit> that began <number> <timeunits> before
> the current <timeunit> began" (but then for any significantly large
> unit you can get into arguments about what "began" means). But zsh
> did not invent the nomenclature.
BTW, could zsh define <n and >n, that would have the intuitive
meaning? e.g. echo *(ah>5) would display the files accessed more
that 5 hours (= 18000 seconds) ago.
--
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA
next prev parent reply other threads:[~2005-07-11 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 3:16 Clint Adams
2003-03-18 16:25 ` Bart Schaefer
2005-07-11 12:17 ` Vincent Lefevre [this message]
2007-12-13 18:25 ` Clint Adams
2007-12-13 22:35 ` Peter Stephenson
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=20050711121700.GA16217@dixsept.loria.fr \
--to=vincent@vinc17.org \
--cc=185228-forwarded@bugs.debian.org \
--cc=zsh-workers@sunsite.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).