From: Eli Zaretskii <eliz@gnu.org>
To: larsi@gnus.org
Cc: monnier@iro.umontreal.ca, 4394@debbugs.gnu.org
Subject: bug#4394: 23.1; flashing when overlapping face and mouse-face properties
Date: Sun, 18 Jul 2021 22:29:28 +0300 [thread overview]
Message-ID: <83eebv7753.fsf@gnu.org> (raw)
In-Reply-To: <83fswb77z2.fsf@gnu.org> (message from Eli Zaretskii on Sun, 18 Jul 2021 22:11:29 +0300)
> Date: Sun, 18 Jul 2021 22:11:29 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: monnier@iro.umontreal.ca, 4394@debbugs.gnu.org
>
> > From: Lars Ingebrigtsen <larsi@gnus.org>
> > Date: Sun, 18 Jul 2021 21:06:57 +0200
> > Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 4394@debbugs.gnu.org
> >
> > The point of the mouse face is to tell the user that they can mouse-2 on
> > the region to expand the abbreviated bits. (This is done in
> > `last-sexp-setup-props'.)
> >
> > However, when the sexp is large, the mouse face is indeed very annoying.
> > Would it make sense to shorten it somehow? For instance, only display
> > it over the "..." to indicate that it's the abbreviation that the mouse
> > face is trying to draw attention to? Or... something else?
> >
> > Like... er... adding underlines or something to the dots and not using
> > a mouse face at all? Or underlines and a mouse face, but just for the
> > dots...
> >
> > Anybody got an opinion?
>
> My opinion is that we should leave this alone.
Btw, here the highlight stops at the right parentheses, it doesn't go
to the right edge of the window.
next prev parent reply other threads:[~2021-07-18 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 23:38 bug#4394: 23.1; flashing when overlapping face and mouse-face properties Drew Adams
2011-07-12 22:48 ` Lars Magne Ingebrigtsen
2021-07-18 19:06 ` Lars Ingebrigtsen
2021-07-18 19:11 ` Eli Zaretskii
2021-07-18 19:29 ` Eli Zaretskii [this message]
2021-08-16 12:13 ` Lars Ingebrigtsen
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=83eebv7753.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=4394@debbugs.gnu.org \
--cc=larsi@gnus.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).