unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: kg6mar@gmail.com
Subject: Dired confused by filenames starting with date-like strings
Date: 23 Aug 2006 11:15:34 -0700	[thread overview]
Message-ID: <1156356934.469929.210320@i3g2000cwc.googlegroups.com> (raw)

Dired gets confused by certain filenames in which the beginning
resembles a date and there is an embedded space (my photograph naming
convention).  It fails to assemble the entire filename.

Example:

-rw-rw-rw-   1 John     root  1113559 Oct 12  2005 04 Project - Front
caulking.JPG
-r--r--r--   1 John     root  1924322 Sep  5  2005 2005-09-05 002.JPG

Dired correctly interprets the first filename as "04 Project - Front
caulking.JPG" but incorrectly thinks that the second file is named
"002.JPG" instead of "2005-09-05 002.JPG"

The behavior manifests itself in operations like Copy and Rename.

I googled my way to looking at dired-move-to-filename-regexp, but its
value is very complex relative to my regexp skill, and anything I do to
it will likely have unintended consequences.  (Adding the -b flag to
dired-listing-switches did nothing.)

I'm going to dig into it the best I can, but I also want to put it out
here and see if someone else has been here before.

Emacs-version's value is "21.3.1"  Operating system is Windows XP.

I'd rather not rename all my photographs (well, actually, I do, and
that's how I discovered this).

Thanks, and hail Emacs

-- John

             reply	other threads:[~2006-08-23 18:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23 18:15 kg6mar [this message]
2006-08-23 22:17 ` Dired confused by filenames starting with date-like strings Miles Bader
2006-08-24 11:56   ` Peter Dyballa
2006-08-24 14:27     ` Kevin Rodgers
     [not found]   ` <mailman.5544.1156420601.9609.help-gnu-emacs@gnu.org>
2006-08-24 14:35     ` Miles Bader
2006-08-24 15:05       ` Peter Dyballa
2006-08-24 16:12         ` Dired doesn't decode UTF-8 file names (was: Dired confused by filenames starting with date-like strings) Kevin Rodgers
2006-08-24 19:48           ` Peter Dyballa
2006-08-28 15:02             ` Dired doesn't decode UTF-8 file names Kevin Rodgers
2006-08-28 15:44               ` Peter Dyballa
2006-08-28 20:52                 ` Kevin Rodgers
2006-08-28 21:29                   ` Peter Dyballa
     [not found]                   ` <mailman.5855.1156800592.9609.help-gnu-emacs@gnu.org>
2006-08-28 21:36                     ` David Kastrup
     [not found] ` <mailman.5520.1156371436.9609.help-gnu-emacs@gnu.org>
2006-08-24 17:43   ` Dired confused by filenames starting with date-like strings kg6mar
2006-08-24 23:35     ` Eli Zaretskii
2006-08-25  0:41     ` Miles Bader
     [not found]     ` <mailman.5588.1156462534.9609.help-gnu-emacs@gnu.org>
2006-08-25 23:28       ` B. T. Raven
2006-08-26 12:09         ` Eli Zaretskii
     [not found]         ` <mailman.5676.1156594178.9609.help-gnu-emacs@gnu.org>
2006-08-27  0:58           ` B. T. Raven
2006-08-27  1:41             ` Miles Bader
     [not found]             ` <mailman.5698.1156642923.9609.help-gnu-emacs@gnu.org>
2006-09-07  3:08               ` kg6mar
2006-09-07 13:44                 ` Miles Bader
2006-11-02 17:59               ` John Olson
2006-08-24 21:48   ` Jesse Alama

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=1156356934.469929.210320@i3g2000cwc.googlegroups.com \
    --to=kg6mar@gmail.com \
    /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.
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).