From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: larsi@gnus.org, 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 16:39:46 +0200 [thread overview]
Message-ID: <83eevqtex9.fsf@gnu.org> (raw)
In-Reply-To: <87y2tzp6g4.fsf@gmx.net> (message from Stephen Berman on Wed, 22 Jan 2020 21:44:11 +0100)
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: larsi@gnus.org, ynyaaa@gmail.com, 39115@debbugs.gnu.org
> Date: Wed, 22 Jan 2020 21:44:11 +0100
>
> Why do overlays and text properties differ on this?
That's a side effect of different implementations. Text properties
are kept as intervals, and so two adjacent intervals with the same
value of the property are indistinguishable from a single interval
covering both stretches of text (and AFAIR we actually convert them
into a single interval when we see fit). By contrast, overlays are
kept in a list, and you can have any number of them at the same
position with the same property (which is why you can have, e.g., two
or more after-strings at EOB, and they will both be displayed).
next prev parent reply other threads:[~2020-01-23 14:39 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
2020-01-23 14:47 ` Stephen Berman
2020-01-23 14:39 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83eevqtex9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39115@debbugs.gnu.org \
--cc=larsi@gnus.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 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.