From: Dani Moncayo <dmoncayo@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: 12078@debbugs.gnu.org
Subject: bug#12078: 24.1; Improve the I-search prompt
Date: Mon, 30 Jul 2012 02:45:42 +0200 [thread overview]
Message-ID: <CAH8Pv0gc_z-aQY2xKKkQcaetH=NBvVL+df7uefgSfbH6GEhdgw@mail.gmail.com> (raw)
In-Reply-To: <87d33esat8.fsf@mail.jurta.org>
> I don't propose to install this change immediately.
> Please try this out for a while.
Thanks Juri. I've tried your patch and I think that is a step forward.
However, on second thought, I think that the "failing" message is
actually unnecessary. Looking at the echo area, it is obvious whether
the current search is failing or not (if it's failing, the unmatched
text will be on a different face).
Regarding the "search states" (wrapped, overwrapped, ...), I see that
we disagree :). These states are currently inserted at the left side
of the search string, and I definitely would prefer to have them at
the right side, for the reason exposed in a previous post: avoid the
horizontal movement of the search string, which makes harder to
concentrate on the search string. This is an important factor, IMO.
In the left part of the search string, I would put only the info that
does _not_ depend on the state of the search, i.e., the "I-search"
text and (when necessary) the type of search (word and/or regexp).
All other messages (i.e. those that _do_ depend on the state of the
search) would go to the right side of the search string (as "[flag1
flag2 ...]"), for the reason already explained.
Just my opinion...
Thanks.
--
Dani Moncayo
next prev parent reply other threads:[~2012-07-30 0:45 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 [this message]
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
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='CAH8Pv0gc_z-aQY2xKKkQcaetH=NBvVL+df7uefgSfbH6GEhdgw@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=12078@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 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.