From: David Kastrup <dak@gnu.org>
To: rms@gnu.org
Cc: David Hansen <david.hansen@gmx.net>, emacs-devel@gnu.org
Subject: Re: Fwd: Re: Easy way to rename files sequentially?
Date: Mon, 03 Dec 2007 11:38:10 +0100 [thread overview]
Message-ID: <85prxogj1p.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1Iz4WD-0007ns-E0@fencepost.gnu.org> (Richard Stallman's message of "Mon, 03 Dec 2007 01:11:01 -0500")
Richard Stallman <rms@gnu.org> writes:
> Has anyone looked at this?
>
> From: Eli Zaretskii <eliz@gnu.org>
> Subject: Re: Easy way to rename files sequentially?
> Newsgroups: gmane.emacs.help
> To: help-gnu-emacs@gnu.org
> Date: Mon, 26 Nov 2007 22:40:47 +0200
>
>> From: David Hansen <david.hansen@gmx.net>
>> Date: Mon, 26 Nov 2007 18:26:02 +0000
>>
>> \# isn't working in `dired-do-rename-regexp'
>
> That sounds like a bug (or missing feature) to me:
> dired-do-rename-regexp is supposed to be 100% compatible with
> query-replace-regexp, as far as regexp replacement goes.
The regexp magic from query-replace-regexp is implemented in a two-step
process: first the interactive form translates such elements into a
replacement list of a specific form rather than a replacement string,
and then perform-replace works using this list.
The generated list (and the code processing it) heavily relies on
working in a buffer whereas dired-do-rename-regexp basically works on a
string. Making the additional magic available generally instead of just
to query-replace-regexp itself would require some amount of work, not
least of all because one would need to design a reasonable interface for
this functionality which is, at the current point of time, more or less
a hack inside of replace.el.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-12-03 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 21:27 Fwd: Re: Easy way to rename files sequentially? David Hansen
2007-12-03 6:11 ` Richard Stallman
2007-12-03 10:38 ` David Kastrup [this message]
2007-12-03 18:42 ` Richard Stallman
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=85prxogj1p.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=david.hansen@gmx.net \
--cc=emacs-devel@gnu.org \
--cc=rms@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).