From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 12078@debbugs.gnu.org
Subject: bug#12078: 24.1; Improve the I-search prompt
Date: Fri, 18 Sep 2020 17:05:51 +0200 [thread overview]
Message-ID: <87wo0rdt0w.fsf@gnus.org> (raw)
In-Reply-To: <CAH8Pv0iYtVu7pxC-=5m-ZH=ojoPWrfUrTQNF-yLM37vd_i+TVg@mail.gmail.com> (Dani Moncayo's message of "Sat, 28 Jul 2012 19:56:48 +0200")
Dani Moncayo <dmoncayo@gmail.com> writes:
> As discussed in bug #9918
> (http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9918#50), I propose to
> change the format of the I-search prompt, so that instead of (e.g.):
>
> Failing I-search: foobar
> Overwrapped I-search: foobar
> Failing overwrapped I-search: foobar
> Failing I-search: foobar [initial node]
>
> would be
>
> I-search: foobar [failing]
> I-search: foobar [overwrapped]
> I-search: foobar [failing, overwrapped]
> I-search: foobar [failing, initial node]
>
> That is: present all the I-search "flags" at the right side of the
> search string, using that common pattern.
There didn't seem to be much enthusiasm for this, and I agree --
changing the prompt here just seems more intuitive and easier to
understand than something that looks like a feature set after the search
string.
So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2020-09-18 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 17:56 bug#12078: 24.1; Improve the I-search prompt Dani Moncayo
2012-07-29 0:35 ` Juri Linkov
2012-07-29 18:04 ` Juri Linkov
2012-07-30 0:45 ` Dani Moncayo
2012-07-30 9:25 ` Stefan Monnier
2012-07-30 9:30 ` Dani Moncayo
2012-07-30 23:03 ` Stefan Monnier
2012-07-30 23:50 ` Dani Moncayo
2012-08-01 23:29 ` Stefan Monnier
2012-08-08 8:06 ` Juri Linkov
2012-08-08 8:30 ` Dani Moncayo
2020-09-18 15:05 ` Lars Ingebrigtsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wo0rdt0w.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=12078@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.