From: Tomas Nordin <tomasn@posteo.net>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>,
Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: killing the result of isearch
Date: Wed, 08 Nov 2017 23:24:58 +0100 [thread overview]
Message-ID: <87k1z02yth.fsf@fliptop> (raw)
In-Reply-To: <29AEE45F-D0CA-442F-8F46-E290C40782B4@gmail.com>
Jean-Christophe Helary <jean.christophe.helary@gmail.com> writes:
> No, I am actually talking about expectations from using emacs where regions are highlighted, like what isearch seems like doing. What I am seeing is what looks like a region (and except for the active match, all the others are highlighted exactly as a region would be), but it doesn't act like a region. So there is a UI promise that's broken.
Does this imply that in a read-only buffer, there must be no
highlighting of the match for you not to say the UI is broken? You
cannot act on the text there.
Or, in a read-only buffer, is it good that the match(es) are
highlighted? Why?
>
>
> Jean-Christophe Helary
> -----------------------------------------------
> @brandelune http://mac4translators.blogspot.com
next prev parent reply other threads:[~2017-11-08 22:24 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 2:41 killing the result of isearch Jean-Christophe Helary
2017-11-07 5:34 ` Drew Adams
2017-11-07 6:01 ` Jean-Christophe Helary
2017-11-07 6:25 ` Søren Pilgård
[not found] ` <mailman.3103.1510035932.27995.help-gnu-emacs@gnu.org>
2017-11-07 7:07 ` Loris Bennett
2017-11-07 7:49 ` Jean-Christophe Helary
2017-11-07 8:43 ` Jean-Christophe Helary
[not found] ` <mailman.3106.1510044223.27995.help-gnu-emacs@gnu.org>
2017-11-07 10:49 ` Loris Bennett
2017-11-07 12:45 ` Jean-Christophe Helary
2017-11-07 15:26 ` Drew Adams
2017-11-07 15:51 ` Jean-Christophe Helary
2017-11-07 16:46 ` Drew Adams
2017-11-07 22:38 ` Jean-Christophe Helary
2017-11-07 16:53 ` Eric Abrahamsen
2017-11-07 17:24 ` Drew Adams
2017-11-07 17:45 ` Eric Abrahamsen
2017-11-08 8:21 ` Thien-Thi Nguyen
2017-11-08 13:47 ` Emanuel Berg
2017-11-11 15:36 ` Charles A. Roelli
[not found] ` <mailman.3114.1510058721.27995.help-gnu-emacs@gnu.org>
2017-11-07 15:08 ` Loris Bennett
2017-11-07 15:28 ` Jean-Christophe Helary
2017-11-07 16:24 ` Drew Adams
2017-11-07 22:34 ` Jean-Christophe Helary
2017-11-07 22:54 ` Drew Adams
2017-11-08 22:24 ` Tomas Nordin [this message]
2017-11-08 22:44 ` Jean-Christophe Helary
2017-11-08 23:07 ` Emanuel Berg
2017-11-09 21:38 ` Tomas Nordin
2017-11-10 13:11 ` Jean-Christophe Helary
2017-11-10 16:54 ` Drew Adams
2017-11-07 8:31 ` Marcin Borkowski
2017-11-07 15:26 ` Drew Adams
2017-11-07 20:59 ` Bob Proulx
2017-11-07 22:10 ` Drew Adams
2017-11-07 22:53 ` Bob Proulx
2017-11-07 23:15 ` Jean-Christophe Helary
2017-11-08 4:27 ` Bob Proulx
2017-11-08 5:29 ` Jean-Christophe Helary
2017-11-08 18:50 ` Bob Proulx
2017-11-07 17:53 ` Stefan Monnier
2017-11-07 22:59 ` Jean-Christophe Helary
2017-11-12 20:02 ` Tomas Nordin
2017-11-12 22:13 ` Emanuel Berg
2017-11-13 21:17 ` Tomas Nordin
2017-11-13 22:13 ` Emanuel Berg
2017-11-20 3:24 ` Emanuel Berg
2017-11-15 14:48 ` Emanuel Berg
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=87k1z02yth.fsf@fliptop \
--to=tomasn@posteo.net \
--cc=help-gnu-emacs@gnu.org \
--cc=jean.christophe.helary@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.
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).