From: Ian Zimmerman <itz@buug.org>
To: help-gnu-emacs@gnu.org
Subject: Re: query replace -- error with prompt instead of insert
Date: Tue, 13 Sep 2011 14:55:32 -0700 [thread overview]
Message-ID: <87litsrtt7.fsf@foolinux.dyndns.org> (raw)
In-Reply-To: <loom.20110913T185546-557@post.gmane.org> (fork's message of "Tue, 13 Sep 2011 17:00:29 +0000 (UTC)")
fork> So if there are two instances of 'foo' and I replace 'foo' with
fork> 'bar' but hit 'y' 10 times, I don't want to insert 8 'y'
fork> characters, but flash and error instead.
Your desires are contradictory.
The very purpose of prompts is to get input from a thinking human before
committing to each action. If you know in advance you want to always
answer `y', you should use the promptless replace-string.
--
Ian Zimmerman
gpg public key: 1024D/C6FF61AD
fingerprint: 66DC D68F 5C1B 4D71 2EE5 BD03 8A00 786C C6FF 61AD
Rule 420: All persons more than eight miles high to leave the court.
next prev parent reply other threads:[~2011-09-13 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 17:00 query replace -- error with prompt instead of insert fork
2011-09-13 21:55 ` Ian Zimmerman [this message]
2011-09-14 8:06 ` suvayu ali
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=87litsrtt7.fsf@foolinux.dyndns.org \
--to=itz@buug.org \
--cc=help-gnu-emacs@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.
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).