From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15668@debbugs.gnu.org, Darren Hoo <darren.hoo@gmail.com>
Subject: bug#15668: 24.3.50; No font lock on active region
Date: Mon, 21 Oct 2013 20:47:25 +0200 [thread overview]
Message-ID: <C30E13CB-347C-4972-9DC3-2FDC03703FB8@swipnet.se> (raw)
In-Reply-To: <83zjq2k2nf.fsf@gnu.org>
Hello.
21 okt 2013 kl. 18:30 skrev Eli Zaretskii <eliz@gnu.org>:
>> Date: Mon, 21 Oct 2013 13:56:24 +0800
>> From: Darren Hoo <darren.hoo@gmail.com>
>>
>> Open any elisp file and mark a function, and the active region is
>> not font-lockfied.
>>
>> This only occurs in GUI mode, it's ok with text-mode.
>
> Can't reproduce this with today's trunk. Unless the recipe is not as
> simple as it sounds, this could be NS specific.
Both Gtk+ and NS does this. The reason is that we use the system defined selection colors, and the background may be ill-matched to Emacs foreground colors.
For example, many Gnome settings use an almost black color for selection background, so Emacs black for text color is almost unreadable. These settings use white(ish) for text color which is much better. But by setting foreground selection color, you loose font-lock. OSX uses a light blue for background, which is very near to blue used by font-lock-constant-face and also near font-lock-function-name-face.
It would be nice if one could define a face with a foreground color to be used when foreground and background otherwise are to similar.
Jan D.
next prev parent reply other threads:[~2013-10-21 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 5:56 bug#15668: 24.3.50; No font lock on active region Darren Hoo
2013-10-21 16:30 ` Eli Zaretskii
2013-10-21 18:47 ` Jan Djärv [this message]
2013-10-21 19:06 ` Eli Zaretskii
2013-10-21 19:20 ` Eli Zaretskii
2013-10-22 16:14 ` Jan Djärv
2013-10-22 16:28 ` Eli Zaretskii
2013-11-01 15:54 ` Jan Djärv
2013-10-21 21:36 ` Darren Hoo
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=C30E13CB-347C-4972-9DC3-2FDC03703FB8@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=15668@debbugs.gnu.org \
--cc=darren.hoo@gmail.com \
--cc=eliz@gnu.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.