From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: hackernews & gnus-summary-browse-url
Date: Wed, 09 Mar 2022 11:50:45 -0800 [thread overview]
Message-ID: <87k0d2nbvu.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <lzilsmoqwg.fsf@3c22fb11fdab.ant.amazon.com>
Sam Steingold <sds@gnu.org> writes:
>> * Lars Ingebrigtsen <ynefv@tahf.bet> [2022-03-09 13:04:29 +0100]:
>>
>> Sam Steingold <sds@gnu.org> writes:
>>
>>> If you use it yourself, would you mind if I apply this patch?
>>
>> [...]
>>
>>> + "v" #'gnus-summary-browse-all-urls
>>
>> I'm not sure that's generally useful enough to have as its own
>> command -- people will want to open different subsets of URLs in these
>> cases, and you kinda have to write some code for that.
>
> Right, but sometimes you want to open _all_ URLs, and this is a simple
> way.
> I can add bells and whistles (e.g., open _matching_ URLs), but that's an
> overkill for now.
It's so easy to write a wrapper around `gnus-collect-urls' I can't help
thinking this would be better off as a personal function that behaves
just the way you (personally) want it to...
next prev parent reply other threads:[~2022-03-09 19:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 21:44 Sam Steingold
2022-03-07 23:40 ` Eric Abrahamsen
2022-03-08 15:05 ` Sam Steingold
2022-03-08 15:23 ` Lars Ingebrigtsen
2022-03-08 15:56 ` Eric Abrahamsen
2022-03-08 15:58 ` Lars Ingebrigtsen
2022-03-08 20:50 ` Sam Steingold
2022-03-09 12:04 ` Lars Ingebrigtsen
2022-03-09 19:41 ` Sam Steingold
2022-03-09 19:50 ` Eric Abrahamsen [this message]
2022-03-09 21:20 ` Sam Steingold
2022-03-12 17:38 ` Lars Ingebrigtsen
2022-03-08 16:35 ` dick
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=87k0d2nbvu.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.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).