From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-users@sunsite.auc.dk
Subject: Re: Files modified after a given date
Date: Mon, 23 Aug 1999 10:09:33 +0200 (MET DST) [thread overview]
Message-ID: <199908230809.KAA02317@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Bruce Stephens's message of 22 Aug 1999 19:55:27 +0100
Bruce Stephens wrote:
> Vincent Lefevre <vincent@vinc17.org> writes:
>
> > On Sun, Aug 22, 1999 at 17:44:45 +0100, Bruce Stephens wrote:
> > > Assuming I'm understanding the question correctly, no. You can (in
> > > 3.1.6, anyway), get files modified since some time relative to the
> > > current time:
> > >
> > > *.c(ms-30)
> > >
> > > expands to C files modified in the last 30 seconds, for example.
> >
> > But I don't want it to be relative to the current time.
>
> In which case, I don't think there's a builtin glob way of doing it.
> You could write a function using the stat module, but I don't think we
> have user-defined glob patterns yet?
>
> zmodload stat; builtin stat -H foo .zshrc; echo $foo[mtime]
>
> prints 934038501, for me.
I've been wishing for this since I added the granularity modifiers for
the a/m/c glob qualifiers. The problem is that we would need to be
able to parse date/time strings, of course, which isn't trivial...
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-08-23 8:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-23 8:09 Sven Wischnowsky [this message]
1999-08-27 21:51 ` Gabor
1999-08-27 22:09 ` Bruce Stephens
1999-08-27 22:43 ` Bart Schaefer
1999-08-27 23:44 ` Gabor
1999-08-28 5:00 ` PATCH: ksharrays and assoc array assignments (was Re: Files modified after a given date) Bart Schaefer
1999-08-28 17:14 ` Gabor
-- strict thread matches above, loose matches on Subject: below --
1999-08-22 16:31 Files modified after a given date Vincent Lefevre
1999-08-22 16:44 ` Bruce Stephens
1999-08-22 17:17 ` Vincent Lefevre
1999-08-22 18:55 ` Bruce Stephens
1999-08-22 19:26 ` Vincent Lefevre
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=199908230809.KAA02317@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-users@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).