* bug#73577: Hint this is the final occur match
@ 2024-10-01 1:23 Dan Jacobson
2024-10-01 1:43 ` Stefan Kangas
2024-10-01 3:12 ` Dan Jacobson
0 siblings, 2 replies; 5+ messages in thread
From: Dan Jacobson @ 2024-10-01 1:23 UTC (permalink / raw)
To: 73577
Allow us to examine the messages from M-x occur and next-error:
You can run the command ‘occur’ with M-s o
Next locus from *Occur* [4 times]
occur-find-match: No more matches
Better would be:
You can run the command ‘occur’ with M-s o
Next locus from *Occur* [3 times]
Final locus from *Occur*
That's right. Alerting the user that they are now looking at the final
match would help them avoid asking for another match when there are none!
emacs-version "29.4"
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#73577: Hint this is the final occur match
2024-10-01 1:23 bug#73577: Hint this is the final occur match Dan Jacobson
@ 2024-10-01 1:43 ` Stefan Kangas
2024-10-01 15:56 ` Eli Zaretskii
2024-10-01 3:12 ` Dan Jacobson
1 sibling, 1 reply; 5+ messages in thread
From: Stefan Kangas @ 2024-10-01 1:43 UTC (permalink / raw)
To: Dan Jacobson, 73577
Dan Jacobson <jidanni@jidanni.org> writes:
> Allow us to examine the messages from M-x occur and next-error:
>
> You can run the command ‘occur’ with M-s o
> Next locus from *Occur* [4 times]
> occur-find-match: No more matches
>
> Better would be:
>
> You can run the command ‘occur’ with M-s o
> Next locus from *Occur* [3 times]
> Final locus from *Occur*
>
> That's right. Alerting the user that they are now looking at the final
> match would help them avoid asking for another match when there are none!
>
> emacs-version "29.4"
IMO, "No more matches" is already clear.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#73577: Hint this is the final occur match
2024-10-01 1:43 ` Stefan Kangas
@ 2024-10-01 15:56 ` Eli Zaretskii
2024-10-01 18:07 ` Stefan Kangas
0 siblings, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2024-10-01 15:56 UTC (permalink / raw)
To: Stefan Kangas; +Cc: 73577, jidanni
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Mon, 30 Sep 2024 18:43:45 -0700
>
> Dan Jacobson <jidanni@jidanni.org> writes:
>
> > Allow us to examine the messages from M-x occur and next-error:
> >
> > You can run the command ‘occur’ with M-s o
> > Next locus from *Occur* [4 times]
> > occur-find-match: No more matches
> >
> > Better would be:
> >
> > You can run the command ‘occur’ with M-s o
> > Next locus from *Occur* [3 times]
> > Final locus from *Occur*
> >
> > That's right. Alerting the user that they are now looking at the final
> > match would help them avoid asking for another match when there are none!
> >
> > emacs-version "29.4"
>
> IMO, "No more matches" is already clear.
Agreed. Moreover, we say that in many other cases, so it is a
"de-facto standard".
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#73577: Hint this is the final occur match
2024-10-01 1:23 bug#73577: Hint this is the final occur match Dan Jacobson
2024-10-01 1:43 ` Stefan Kangas
@ 2024-10-01 3:12 ` Dan Jacobson
1 sibling, 0 replies; 5+ messages in thread
From: Dan Jacobson @ 2024-10-01 3:12 UTC (permalink / raw)
To: Stefan Kangas; +Cc: 73577
Yes but with my method the user would know they are already getting the
last bagel, so can avoid another useless trip to the bagel shop, only to
be told there are no more bagels. P.S.,
<73577@debbugs.gnu.org>: host debbugs.gnu.org[209.51.188.43] refused to talk to
me: 421 Downstream server error
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2024-10-01 18:07 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-10-01 1:23 bug#73577: Hint this is the final occur match Dan Jacobson
2024-10-01 1:43 ` Stefan Kangas
2024-10-01 15:56 ` Eli Zaretskii
2024-10-01 18:07 ` Stefan Kangas
2024-10-01 3:12 ` Dan Jacobson
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).