From: Richard Stallman <rms@gnu.org>
Cc: monnier@iro.umontreal.ca, drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: why does occur depropertize matching lines?
Date: Tue, 07 Dec 2004 23:39:50 -0500 [thread overview]
Message-ID: <E1CbtcE-0003pQ-Bt@fencepost.gnu.org> (raw)
In-Reply-To: <87r7m35cmv.fsf@jurta.org> (message from Juri Linkov on Mon, 06 Dec 2004 23:40:24 +0200)
Most faces don't change background color. Only very special faces
(that are very rarely used in buffers on which occur is usually
called) have background different from default.
Yes, most such faces are used for temporary highlighting.
> What we really want is to copy the face info from the source but "dim" it
> a bit so it doesn't overshadow occur's own highlighting.
There is one problem with dimmed faces: they might be not readable,
especially for visually impaired users.
On some terminals, such dimming is not even possible, due to the limited
number of supported colors.
So I think you're right that we can simply change that face.
How about if you define a new face for the purpose, and set it
up in a way you think is good? Please give pay attention to both
the light-background case and the dark-background case.
next prev parent reply other threads:[~2004-12-08 4:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 23:45 why does occur depropertize matching lines? Drew Adams
2004-11-19 16:02 ` Drew Adams
2004-11-21 1:10 ` Richard Stallman
2004-11-21 1:51 ` Drew Adams
2004-11-21 3:22 ` Juri Linkov
2004-11-25 2:19 ` Richard Stallman
2004-11-25 7:27 ` Juri Linkov
2004-11-26 21:03 ` Richard Stallman
2004-12-05 16:43 ` Juri Linkov
2004-12-06 1:40 ` Richard Stallman
2004-12-06 20:10 ` Juri Linkov
2004-12-06 20:33 ` Stefan Monnier
2004-12-06 21:40 ` Juri Linkov
2004-12-08 4:39 ` Richard Stallman [this message]
2004-12-08 19:06 ` Drew Adams
2004-12-08 19:44 ` Josh Varner
2004-12-08 20:08 ` Drew Adams
2004-12-09 4:42 ` Richard Stallman
2004-12-08 4:59 ` Stefan Monnier
2004-12-08 4:39 ` Richard Stallman
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=E1CbtcE-0003pQ-Bt@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 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).