From: Stephen Berman <stephen.berman@gmx.net>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 63271@debbugs.gnu.org, juri@linkov.net
Subject: bug#63271: 29.0.90; broken mouse-face
Date: Tue, 09 May 2023 15:12:06 +0200 [thread overview]
Message-ID: <877cthvec9.fsf@gmx.net> (raw)
In-Reply-To: <87sfc5hdkn.fsf@yahoo.com> (Po Lu's message of "Tue, 09 May 2023 20:52:24 +0800")
On Tue, 09 May 2023 20:52:24 +0800 Po Lu <luangruo@yahoo.com> wrote:
> Stephen Berman <stephen.berman@gmx.net> writes:
[...]
>> Aside from the difference in highlighting, another difference I failed
>> to notice before is that in fundamental-mode the string "TODO" is
>> displayed with DejaVu Sans but in lisp-interaction-mode with DejaVu Sans
>> Mono, although I used the same Lisp code with the face property
>> (:inherit variable-pitch) to enter the string in both buffers. I guess
>> lisp-interaction-mode inhibits variable-pitch face and that's the reason
>> the mouse-highlighting appears on the problematic characters in that
>> mode, in contrast to fundamental-mode.
>>
>> Steve Berman
>
> What if you change the font driver in use to something else, like X?
> i.e.
>
> (set-frame-parameter (selected-frame) 'font-backend "x")
With that the highlighting problem in fundamental-mode vanishes: all
problematic strings show mouse-highlighting. (FTR, with the "x"
font-backend, the default face here is displayed with adobe-courier and
variable-pitch face is displayed with adobe-helvetica.)
Steve Berman
next prev parent reply other threads:[~2023-05-09 13:12 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 15:11 bug#63271: 29.0.90; broken mouse-face Juri Linkov
2023-05-04 16:01 ` Eli Zaretskii
2023-05-05 17:38 ` Juri Linkov
2023-05-05 18:31 ` Eli Zaretskii
2023-05-06 11:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-07 18:00 ` Juri Linkov
2023-05-07 18:35 ` Eli Zaretskii
2023-05-08 15:56 ` Juri Linkov
2023-05-08 16:14 ` Eli Zaretskii
2023-05-08 18:20 ` Stephen Berman
2023-05-08 18:27 ` Eli Zaretskii
2023-05-08 18:47 ` Stephen Berman
2023-05-08 19:09 ` Juri Linkov
2023-05-08 20:46 ` Stephen Berman
2023-05-09 6:47 ` Juri Linkov
2023-05-09 19:06 ` Juri Linkov
2023-05-09 19:21 ` Eli Zaretskii
2023-05-09 23:19 ` Gregory Heytings
2023-05-10 9:38 ` Stephen Berman
2023-05-10 10:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-10 11:01 ` Stephen Berman
2023-05-10 12:05 ` Eli Zaretskii
2023-05-10 11:00 ` Eli Zaretskii
2023-05-11 0:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-11 6:00 ` Eli Zaretskii
2023-05-11 6:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-12 3:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-12 10:43 ` Eli Zaretskii
2023-05-12 12:49 ` Gregory Heytings
2023-05-12 17:20 ` Juri Linkov
2023-05-12 19:21 ` Eli Zaretskii
2023-05-10 0:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-09 6:45 ` Juri Linkov
2023-05-09 8:36 ` Eli Zaretskii
2023-05-09 9:49 ` Stephen Berman
2023-05-09 10:07 ` Stephen Berman
2023-05-09 10:21 ` Eli Zaretskii
2023-05-09 10:35 ` Stephen Berman
2023-05-09 11:50 ` Eli Zaretskii
2023-05-09 12:43 ` Stephen Berman
2023-05-09 12:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-09 13:12 ` Stephen Berman [this message]
2023-05-09 13:35 ` Eli Zaretskii
2023-05-09 14:34 ` Stephen Berman
2023-05-10 0:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-10 9:39 ` Stephen Berman
2023-05-09 13:32 ` Eli Zaretskii
2023-05-09 14:34 ` Stephen Berman
2023-05-10 0:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-09 10:14 ` Eli Zaretskii
2023-05-09 1:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-09 6:43 ` Juri Linkov
2023-05-09 8:43 ` Eli Zaretskii
2023-05-09 11:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=877cthvec9.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=63271@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=luangruo@yahoo.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 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.