unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mike Kupfer <kupfer@rawbw.com>
Cc: 60423@debbugs.gnu.org, monnier@iro.umontreal.ca, stefankangas@gmail.com
Subject: bug#60423: 29.0.60; goto-address and shr/textsec don't play nicely together
Date: Sun, 27 Oct 2024 12:35:49 +0200	[thread overview]
Message-ID: <86ed41al4q.fsf@gnu.org> (raw)
In-Reply-To: <66867.1729115569@alto.camomileplus.org> (message from Mike Kupfer on Wed, 16 Oct 2024 14:52:49 -0700)

> From: Mike Kupfer <kupfer@rawbw.com>
> cc: Eli Zaretskii <eliz@gnu.org>, 60423@debbugs.gnu.org,
>         stefankangas@gmail.com
> Comments: In-reply-to Stefan Monnier <monnier@iro.umontreal.ca>
>    message dated "Sat, 12 Oct 2024 19:13:49 -0400."
> Date: Wed, 16 Oct 2024 14:52:49 -0700
> 
> Stefan Monnier wrote:
> 
> > In this case the problem is that two packages compete for the same URL.
> > I think it makes sense for goto-address to "leave text alone" in this
> > case, but the question remains of how to detect *this* situation.
> > 
> > The underlying text having a `face` property doesn't seem sufficient
> > (especially since multiple `face` properties get merged, so the
> > conflict is less severe).
> > Maybe it should check for the presence of `help-echo and (follow-link
> > or keymap)`?  And make sure the those properties cover exactly the same
> > chunk of text?
> 
> As far as covering the same chunk of text, I'll need to play with this
> some more to see what works.  shr-tag-a inserts a warning emoji with a
> help-echo property, which goto-address somehow manages to clobber.  That
> warning emoji is not something goto-address would normally be looking
> for.

Ping!  How can we make some progress with this bug report?





  reply	other threads:[~2024-10-27 10:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30  3:59 bug#60423: 29.0.60; goto-address and shr/textsec don't play nicely together Mike Kupfer
2022-12-30 14:52 ` Eli Zaretskii
2023-09-05 23:31   ` Stefan Kangas
2023-09-06  4:27     ` Mike Kupfer
2024-10-09  0:09     ` Mike Kupfer
2024-10-09 12:24       ` Eli Zaretskii
2024-10-10 23:46         ` Mike Kupfer
2024-10-11  5:46           ` Eli Zaretskii
2024-10-16 21:45             ` Mike Kupfer
2024-10-12 23:13         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-16 21:52           ` Mike Kupfer
2024-10-27 10:35             ` Eli Zaretskii [this message]
2024-10-27 19:24               ` Mike Kupfer
2024-11-02 11:10                 ` Eli Zaretskii

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=86ed41al4q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60423@debbugs.gnu.org \
    --cc=kupfer@rawbw.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefankangas@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).