From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@IRO.UMontreal.CA>, <10148@debbugs.gnu.org>
Subject: bug#10148: 24.0.91; "pending" regexp Isearch
Date: Wed, 30 Nov 2011 06:47:18 -0800 [thread overview]
Message-ID: <8DC0B561F4F94ADF917DC2CB29B32D92@us.oracle.com> (raw)
In-Reply-To: <jwvd3c97lkx.fsf-monnier+emacs@gnu.org>
> Another option is to not say anything at all. I don't have a strong
> opinion on this, but I never found "pending" useful and I don't think
> I'd have felt differently if it had said "adjusted" instead.
+1
Or use some text that says what it means? You say it moves to another search
hit ("adjusts its position to another match").
Is that other search hit always the next/previous one (depending on direction)?
Or is it at least some simple, consistent movement that is easy to name?
If so, maybe just say that you are moving to the "[next]" match or some such.
Dunno - it's not clear to me what is involved. But it's also not clear to me
from either "pending" or "adjusted". And if you say nothing at all but move to
another search hit, that too might be confusing. HTH.
next prev parent reply other threads:[~2011-11-30 14:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-27 12:52 bug#10148: 24.0.91; "pending" regexp Isearch Dani Moncayo
2011-11-29 0:39 ` Juri Linkov
2011-11-29 10:26 ` Dani Moncayo
2011-11-30 9:51 ` Juri Linkov
2011-11-30 10:26 ` Dani Moncayo
2011-11-30 10:38 ` Juri Linkov
2011-11-30 10:55 ` Dani Moncayo
2011-11-30 11:04 ` Dani Moncayo
2011-11-30 14:08 ` Stefan Monnier
2011-11-30 14:21 ` Dani Moncayo
2011-11-30 14:47 ` Drew Adams [this message]
2011-11-30 15:35 ` Juri Linkov
2011-11-30 19:13 ` Stefan Monnier
2011-12-01 7:37 ` Juri Linkov
2011-12-01 11:34 ` Eli Zaretskii
2011-12-01 15:22 ` Drew Adams
2011-12-01 16:06 ` Stefan Monnier
2022-04-17 12:27 ` Lars Ingebrigtsen
2022-04-17 17:12 ` Drew Adams
2022-04-18 19:09 ` Juri Linkov
2022-04-18 19:20 ` Drew Adams
2022-04-18 19:07 ` Juri Linkov
2022-04-18 19:19 ` Lars Ingebrigtsen
2022-04-20 7:34 ` Juri Linkov
2022-04-20 10:52 ` Lars Ingebrigtsen
2022-04-20 17:13 ` Juri Linkov
2022-04-21 11:34 ` Lars Ingebrigtsen
2022-04-21 12:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=8DC0B561F4F94ADF917DC2CB29B32D92@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=10148@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).