From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 39115@debbugs.gnu.org, ynyaaa@gmail.com
Subject: bug#39115: 26.3; eww consecutive links look like one link with mouse-over
Date: Thu, 23 Jan 2020 13:22:21 +0100 [thread overview]
Message-ID: <87a76es6pu.fsf@gnus.org> (raw)
In-Reply-To: <87y2tzp6g4.fsf@gmx.net> (Stephen Berman's message of "Wed, 22 Jan 2020 21:44:11 +0100")
Stephen Berman <stephen.berman@gmx.net> writes:
> Why do overlays and text properties differ on this?
Overlays are objects, so even if they have identical properties, it's
easy to see where an overlay starts and stops. For text properties, we
just use ad-hoc strategies like seeing whether the property we're
interested changes or not, and determine the start/stop of the region
based on that.
It's perhaps unfortunate that text property regions don't have more
"identity", but I guess it'd be difficult to change that now.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-01-23 12:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 15:16 bug#39115: 26.3; eww consecutive links look like one link with mouse-over ynyaaa
2020-01-22 15:16 ` Lars Ingebrigtsen
2020-01-22 15:27 ` Robert Pluim
2020-01-22 15:29 ` Lars Ingebrigtsen
2020-01-22 15:40 ` Robert Pluim
2020-01-22 15:45 ` Lars Ingebrigtsen
2020-01-22 16:05 ` Robert Pluim
2020-01-22 16:31 ` Eli Zaretskii
2020-01-22 19:15 ` Stephen Berman
2020-01-22 19:23 ` Eli Zaretskii
2020-01-22 20:44 ` Stephen Berman
2020-01-23 12:22 ` Lars Ingebrigtsen [this message]
2020-01-23 14:47 ` Stephen Berman
2020-01-23 14:39 ` Eli Zaretskii
2020-01-23 12:16 ` Lars Ingebrigtsen
2020-01-23 1:47 ` ynyaaa
2020-01-23 12:18 ` Lars Ingebrigtsen
2020-01-23 14:28 ` Eli Zaretskii
2020-01-24 15:24 ` Lars Ingebrigtsen
2020-01-24 15:41 ` Eli Zaretskii
2020-02-19 13:09 ` 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=87a76es6pu.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=39115@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
--cc=ynyaaa@gmail.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).