unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: dired-move-to-filename-regexp
Date: Mon, 20 Sep 2004 16:28:44 -0700	[thread overview]
Message-ID: <7wekkw5xlf.fsf@sic.twinsun.com> (raw)
In-Reply-To: <414E7485.3080103@math.ku.dk> (Lars Hansen's message of "Mon, 20 Sep 2004 08:11:17 +0200")

Lars Hansen <larsh@math.ku.dk> writes:

> Yes, I now see it is documented with an example in a comment in
> dired-move-to-filename-regexp.
> But doesn't the ".*" make the "[0-9][kKMGTPEZY]?" superfluous?

No, because the "[0-9][kKMGTPEZY]?" forces the date to be preceded by
something that looks like a size.  Without it, there would be more
false matches of dates within file names, e.g., the file name
"foo bar 1 2000 baz" would contain a "date" that looks like "bar 1 2000".

      reply	other threads:[~2004-09-20 23:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-19  7:44 dired-move-to-filename-regexp Lars Hansen
2004-09-19  8:20 ` dired-move-to-filename-regexp Paul Eggert
2004-09-20  0:05   ` dired-move-to-filename-regexp Richard Stallman
2004-09-20  4:49     ` dired-move-to-filename-regexp Paul Eggert
2004-09-20  5:00       ` dired-move-to-filename-regexp Miles Bader
2004-09-21 18:30         ` dired-move-to-filename-regexp Richard Stallman
2004-09-22  6:09           ` dired-move-to-filename-regexp Paul Eggert
2004-09-23 16:45             ` dired-move-to-filename-regexp Richard Stallman
2004-09-23 17:57               ` dired-move-to-filename-regexp Stefan Monnier
2004-09-24 23:40                 ` dired-move-to-filename-regexp Richard Stallman
2004-09-25  5:20                   ` dired-move-to-filename-regexp Stefan
2004-09-25 15:36                     ` dired-move-to-filename-regexp Richard Stallman
2004-09-25 19:08                       ` dired-move-to-filename-regexp Stefan
2004-09-26 18:19                         ` dired-move-to-filename-regexp Richard Stallman
2004-09-29  3:17                           ` dired-move-to-filename-regexp Stefan
2004-09-23 18:27               ` dired-move-to-filename-regexp Paul Eggert
2004-09-24 23:40                 ` dired-move-to-filename-regexp Richard Stallman
2004-09-23 23:27               ` dired-move-to-filename-regexp Miles Bader
2004-09-24 23:41                 ` dired-move-to-filename-regexp Richard Stallman
2004-09-27  3:34                   ` dired-move-to-filename-regexp Miles Bader
2004-09-24  5:51               ` dired-move-to-filename-regexp Jim Meyering
2004-09-25  7:08                 ` dired-move-to-filename-regexp Richard Stallman
2004-09-21 18:30       ` dired-move-to-filename-regexp Richard Stallman
2004-09-23 18:59     ` dired-move-to-filename-regexp Lars Hansen
2004-09-24 23:40       ` dired-move-to-filename-regexp Richard Stallman
2004-09-20  6:11   ` dired-move-to-filename-regexp Lars Hansen
2004-09-20 23:28     ` Paul Eggert [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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7wekkw5xlf.fsf@sic.twinsun.com \
    --to=eggert@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).