From: Drew Adams <drew.adams@oracle.com>
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: Tue, 7 Nov 2017 14:54:40 -0800 (PST) [thread overview]
Message-ID: <3d8cb47d-ca09-4302-9d70-de64006fcb5f@default> (raw)
In-Reply-To: <97361DF0-A104-4FC4-B16B-5ADCBDD0E35C@gmail.com>
> >> 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.
> >
> > That's not what I see in vanilla Emacs: `emacs -Q'.
>
> Interesting. When I do that on one of my local files (with an emacs I built
> a few days ago) I do get the current match highlighted in purple and the
> other matches highlighted in blue (after testing a region is highlighted in
> a slightly different color). The cursor is blinking at the end of the first
> match.
>
> So it looks as I wrote: this looks like a region, with a cursor blinking
> where point it, but it does not act as one.
>
> What matters here is not the color, but the fact that point has moved and
> something that looks like a region is formed. Hence the expectation. And
> really, if that "object" exists on screen, I'd love to be able to capture
> it somehow.
OK, so you feel that any highlighting that shows a different
background from the default background, and where the cursor
is at one end of a stretch of such highlighting, "looks like
a region". To you it looks as if that text has been selected,
available to act on (e.g. cut, copy, replace).
Emacs uses background highlighting for lots of different things,
and sometimes the cursor is at the end of such a highlighted
stretch of text. If you use your interpretation then you are
likely to be disappointed from time to time - such highlighting
does not, in general, indicate "the" Emacs region.
Fortunately, you can customize Emacs faces, so you could, in
order not to be confused, customize all faces that by default
highlight the background, so that they no longer do so. You
can easily change them to highlight the foreground instead,
for example. There are not that many, and changing them all
is easily done. Use `M-x list-faces-display' to see which
faces you use have that problem.
The ones I see, by default (`emacs -Q') are:
cursor
fringe
header-line
header-line-highlight
isearch
isearch-fail
lazy-highlight
match
menu
mode-line
mode-line-highlight
mode-line-inactive
next-error
query-replace
secondary-selection
show-paren-match
show-paren-match-expression
show-paren-mismatch
tool-bar
tooltip
trailing-whitespace
tty-menu-disabled-face
tty-enabled-face
tty-menu-selected-face
Some of those (e.g., fringe, the mode-line ones) are used
in non-buffer-position places, where you cannot place the
cursor anyway, so you need not change them - no possible
confusion with region highlighting there.
next prev parent reply other threads:[~2017-11-07 22:54 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 [this message]
2017-11-08 22:24 ` Tomas Nordin
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=3d8cb47d-ca09-4302-9d70-de64006fcb5f@default \
--to=drew.adams@oracle.com \
--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).