unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@jurta.org>
Cc: 10148@debbugs.gnu.org, Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: bug#10148: 24.0.91; "pending" regexp Isearch
Date: Sun, 17 Apr 2022 14:27:49 +0200	[thread overview]
Message-ID: <87bkwzao8q.fsf@gnus.org> (raw)
In-Reply-To: <87zkfcspxd.fsf@mail.jurta.org> (Juri Linkov's message of "Thu, 01 Dec 2011 09:37:34 +0200")

Juri Linkov <juri@jurta.org> writes:

>> In this context "pending" makes sense, yes.  So the problem is that
>> "pending" is also used for the other case where it does not make sense.
>
> This is still doubtful because when using an incomplete regexp like
> `C-M-s i s \ |', "pending" still makes sense since Isearch is waiting
> for the user to type an alternative search string.
>
> Actually this situation is already described in (info "(emacs) Regexp Search"):
>
>      In some cases, adding characters to the regexp in an incremental
>   regexp search can make the cursor move back and start again.  For
>   example, if you have searched for `foo' and you add `\|bar', the cursor
>   backs up in case the first `bar' precedes the first `foo'.
>
> So it seems that Dani just wants to add a phrase like
>
>   and `Pending' appears in the search prompt
>
> to the end of the first sentence cited above in the Info manual.

This was ten years ago, and "pending" is still somewhat confusing, but
I've now added the text to the manual in Emacs 29.

I agree that "pending" isn't very informative here, but I don't really
have a suggestion for a clearer wording.  In the "is*" case, we want to
say "we've recalculated (and possibly added more) matches", which is
unusual when isearching, so it's probably nice that we get a message for
that.  But something like "Recalculated" instead of "Pending" might be
nice?

In the \| case, we're probably waiting for more data, so "Pending" is
fine there, but I don't think we really can separate between the two
cases, can we?  "foo\|" is a valid regexp; it's just very odd.

So I dunno.  Perhaps just leaving it as is is the best solution.  Any
opinions?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2022-04-17 12:27 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
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 [this message]
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=87bkwzao8q.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=10148@debbugs.gnu.org \
    --cc=juri@jurta.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).