From: Tim Landscheidt <tim@tim-landscheidt.de>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: info-gnus-english@gnu.org
Subject: Re: How to access HTML DOM/source of MIME part?
Date: Tue, 16 Jun 2020 15:34:28 +0000 [thread overview]
Message-ID: <87d05zhvnf.fsf@passepartout.tim-landscheidt.de> (raw)
In-Reply-To: <87bllprvy1.fsf@passepartout.tim-landscheidt.de> (Tim Landscheidt's message of "Fri, 12 Jun 2020 00:04:22 +0000")
I wrote:
> […]
> *But* your pointer gave me the idea that I could iterate
> over shr's buttons like gnus-collect-urls does, test if
> their URLs match Item_x_Link_B's typical pattern and then
> offer to browse them. This would require that
> Item_x_Link_B's pattern is (relatively) stable; I have to
> check whether that will work reasonably well. Thanks!
It's not that simple :-(. For starters, some of my newslet-
ters shorten all URLs, putting them into the same format.
But more importantly, with Emacs 26.3, (forward-button 1) in
an HTML mail will always move point to the beginning of the
*Article* buffer because (button-start button) returns
(point-min) for some reason. (In my use case, I can proba-
bly work around that by calling next-button directly.)
Is this a bug? What is the best way to create a minimal re-
producible example?
Tim
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2020-06-16 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 22:36 Tim Landscheidt
2020-06-11 23:21 ` Eric Abrahamsen
2020-06-12 0:04 ` Tim Landscheidt
2020-06-16 15:34 ` Tim Landscheidt [this message]
2020-06-16 18:39 ` Eric Abrahamsen
2020-06-16 19:31 ` Lars Ingebrigtsen
2020-06-16 19:43 ` Eric Abrahamsen
2020-06-18 2:50 ` Tim Landscheidt
2020-06-26 9:30 ` 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=87d05zhvnf.fsf@passepartout.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--cc=eric@ericabrahamsen.net \
--cc=info-gnus-english@gnu.org \
/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.
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 NNTP newsgroup(s).