From: Juri Linkov <juri@jurta.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: teirllm@dms.auburn.edu, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: `Q' in Dired - be able to skip the rest of one file and move onto the next
Date: Wed, 09 Jan 2008 02:48:08 +0200 [thread overview]
Message-ID: <873at74yev.fsf@jurta.org> (raw)
In-Reply-To: <BNELLINCGFJLDJIKDGACMEIGCGAA.drew.adams@oracle.com> (Drew Adams's message of "Mon, 7 Jan 2008 16:33:49 -0800")
>> I think this is too weird trick to quit the query-replace
>> operation with M-> and resume it with tags-loop-continue M-,.
>> Maybe instead of this we should try implementing native
>> (i.e. without using etags) multi-file query-replace
>> similar to recently implemented multi-file isearch?
>
> What was wrong with your first suggestion (and Miles's):
>
>>> Maybe, when started by `Q', query-replace should apply `!' to all
>>> marked files, and a new key `Y' should replace all remaining
>>> occurrences in the current file, and a new key `N' should skip
>>> the current file as Miles has already proposed.
That's exactly what I meant in the latest proposal: to implement
multi-file query-replace with additional keys: a key to replace
remaining occurrences in the current file, and a key to skip to
the next file.
How else this is possible to do given that query-replace doesn't
depend on etags?
> But I'd keep the single-file meaning of all keys, including `!', and use a
> different key to replace all remaining occurrences in this file and the
> other files. It's not good for a key (e.g. `!') to change meaning, depending
> on whether one file or several are searched.
`!' in single-file context means to replace all remaining occurrences
that would be fine to apply the same meaning in multi-file context.
Any other keys could be applied only to the current file since
this is an additional separation in search-replace space.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2008-01-09 0:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 7:34 `Q' in Dired - be able to skip the rest of one file and move on to the next Drew Adams
2008-01-03 9:50 ` Richard Stallman
2008-01-03 10:11 ` Andreas Schwab
2008-01-03 10:27 ` Miles Bader
2008-01-03 16:17 ` Drew Adams
2008-01-03 15:56 ` Luc Teirlinck
2008-01-03 16:18 ` `Q' in Dired - be able to skip the rest of one file and move onto " Drew Adams
2008-01-03 21:32 ` Juri Linkov
2008-01-04 2:11 ` Bastien
2008-07-15 0:27 ` Juri Linkov
2008-07-15 7:38 ` Lennart Borgman (gmail)
2008-07-20 0:33 ` Juri Linkov
2008-01-05 5:54 ` Richard Stallman
2008-01-08 0:21 ` Juri Linkov
2008-01-08 0:33 ` Drew Adams
2008-01-08 19:08 ` Richard Stallman
2008-01-09 0:48 ` Juri Linkov [this message]
2008-01-09 1:47 ` Drew Adams
2008-01-08 2:12 ` Luc Teirlinck
2008-01-09 0:54 ` Juri Linkov
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=873at74yev.fsf@jurta.org \
--to=juri@jurta.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=teirllm@dms.auburn.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.