From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dave Aspinall <daveaspin@googlemail.com>
Cc: 4911@debbugs.gnu.org
Subject: bug#4911: mouse-face property should merge face attributes, not replace
Date: Tue, 01 Oct 2019 16:08:02 +0200 [thread overview]
Message-ID: <87h84s5zjx.fsf@gnus.org> (raw)
In-Reply-To: <4AFC026C.4060701@googlemail.com> (Dave Aspinall's message of "Thu, 12 Nov 2009 12:41:16 +0000")
Dave Aspinall <daveaspin@googlemail.com> writes:
> Perhaps this has been noted already: the low-level behaviour of the
> mouse-face property seems ugly: it simply overwrites the face property
> for characters under the mouse. For example in Info, blue underlined
> links turn black without the underline when the mouse is hovered over
> them to give the green background from the highlight face. This feels
> unnatural.
>
> In Proof General (http://proofgeneral.inf.ed.ac.uk) we use the
> mouse-face property on programming language text which is heavily
> decorated with font-lock. Users complain that when the mouse is over
> a region the normal fontification is obliterated.
To reproduce:
(insert (propertize "hello" 'face 'underline 'mouse-face 'highlight))
and put the mouse pointer over the "hello": The underline goes away.
I think it might make sense to merge the properties... but, on the
other hand, this may make the text illegible.
For instance, this
(insert (propertize "hello" 'face '(:foreground "blue") 'mouse-face 'highlight))
would become a blank, blue box if the highlight face didn't define both a
foreground colour.
So I'm not sure this would work. Any opinions?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-01 14:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 12:41 bug#4911: mouse-face property should merge face attributes, not replace Dave Aspinall
2019-10-01 14:08 ` Lars Ingebrigtsen [this message]
2019-10-01 14:36 ` Basil L. Contovounesios
2019-10-01 15:00 ` Eli Zaretskii
2019-10-01 15:14 ` Lars Ingebrigtsen
2019-10-01 16:46 ` Drew Adams
2020-04-10 16:26 ` Clément Pit-Claudel
2020-04-25 21:22 ` Clément Pit-Claudel
2020-04-25 22:13 ` Drew Adams
2020-04-26 3:10 ` Clément Pit-Claudel
2020-04-26 13:34 ` Eli Zaretskii
2020-05-04 15:16 ` Clément Pit-Claudel
2020-05-08 14:39 ` Eli Zaretskii
2020-05-08 15:01 ` Clément Pit-Claudel
2020-05-08 15:20 ` Eli Zaretskii
2020-05-08 15:58 ` Clément Pit-Claudel
2020-04-26 17:22 ` Drew Adams
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=87h84s5zjx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=4911@debbugs.gnu.org \
--cc=daveaspin@googlemail.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.
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).