From: Dani Moncayo <dmoncayo@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: 10148@debbugs.gnu.org
Subject: bug#10148: 24.0.91; "pending" regexp Isearch
Date: Tue, 29 Nov 2011 11:26:25 +0100 [thread overview]
Message-ID: <CAH8Pv0jgFkacRFis2sMEy9Qc2Fq3wvotFS64E-dE73OAyTVCDA@mail.gmail.com> (raw)
In-Reply-To: <87ipm3yd6n.fsf@mail.jurta.org>
> It helps to understand what does this mean after putting a single letter "i"
> in front of the word "is", e.g. by putting this first line
> in the *scratch* buffer:
>
> ;; i This buffer is for notes you don't want to save, and for Lisp evaluation.
>
> and typing the same key sequence `C-< C-M-s i s *'.
>
> "Pending" is necessary for Isearch to go back to the first shorter match.
So, correct me if I'm wrong: "pending" here means "this match has been
found by re-starting the search from the original position".
If that is so, I don't understand the "pending" adjective here.
According to [1], "pending" = "about to happen or waiting to happen",
which is misleading here, no?.
What about changing "pending" for something like "restarted"?
In any case, please describe this flag in chapter 15 of the manual.
--- Footnotes ---
[1] http://dictionary.cambridge.org/dictionary/british/pending_1?q=pending
--
Dani Moncayo
next prev parent reply other threads:[~2011-11-29 10:26 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 [this message]
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
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=CAH8Pv0jgFkacRFis2sMEy9Qc2Fq3wvotFS64E-dE73OAyTVCDA@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=10148@debbugs.gnu.org \
--cc=juri@jurta.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).