From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60423@debbugs.gnu.org, Mike Kupfer <kupfer@rawbw.com>
Subject: bug#60423: 29.0.60; goto-address and shr/textsec don't play nicely together
Date: Tue, 5 Sep 2023 16:31:18 -0700 [thread overview]
Message-ID: <CADwFkmnPmKGSWoj5pt6XROWkWF0bu4dcO021yZ9QCP7LiSqxKQ@mail.gmail.com> (raw)
In-Reply-To: <831qoh6j0i.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 30 Dec 2022 16:52:45 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Mike Kupfer <kupfer@rawbw.com>
>> Date: Thu, 29 Dec 2022 19:59:05 -0800
>>
>> In MH-E, if you mouse over the link or emoji, you get text in the echo
>> area that tells you how to follow the link. There's no explanation
>> given for the red text or the caution emoji, which is a bug IMO.
>>
>> I tracked this down to MH-E's use of goto-address when displaying a
>> message (mh-display-msg > mh-show-addr > goto-address).
>>
>> I can think of a couple ways to deal with this, but I'm not sure what
>> the right way forward is. The simplest approach would be for
>> mh-display-msg to stop using goto-address. I'm not happy with that
>> approach because it removes functionality that MH-E has had for awhile.
>>
>> A slightly more sophisticated approach would be to not use goto-address
>> when using shr to render the message. That loses some functionality
>> (like the auto-linkification of email addresses), and it seems kind of
>> kludgey, but I suppose it's not too terrible.
>>
>> Another possibility would be to make goto-address smarter, so that it
>> doesn't stomp on whatever it was that shr did to get the mouse-over
>> text.
>>
>> I'm happy to take a stab at a fix, but I could use some guidance on the
>> right direction to go in.
>
> I guess the latter, but it will have to be on master, since I'm quite
> sure the changes will not be safe enough for the release branch.
>
> Thanks.
Mike, did you make any progress here? Thanks in advance.
next prev parent reply other threads:[~2023-09-05 23:31 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 [this message]
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
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=CADwFkmnPmKGSWoj5pt6XROWkWF0bu4dcO021yZ9QCP7LiSqxKQ@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=60423@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kupfer@rawbw.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).