Gnus development mailing list
 help / color / mirror / Atom feed
From: Haider Rizvi <harizvi@gmail.com>
To: ding@gnus.org
Subject: Re: Command for browsing article URLs?
Date: Thu, 10 Jan 2019 11:47:37 -0700	[thread overview]
Message-ID: <whyigy37s5oza.fsf@hrizvi-wsm4.internal.salesforce.com> (raw)
In-Reply-To: <87r2dmub03.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Haider Rizvi <harizvi@gmail.com> writes:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> I'd like to have a command, call it `gnus-article-browse-url', which
>>> collects all the links/URLs in the article body, and then offers to
>>> browse one of them (choosing with completion). Bound to "K l",
>>> naturally.
>>
>> I use two functions along these lines but not exactly what you asked
>> for.
>>
>> 1. ace-link-gnus: I've it bound to M-o for some historical reason. In
>> typical ace-fashion, it highlights all urls in the article and you use
>> a key to browse the url in your browser.
>
> That's handy, thank you! I'm glad someone else has done the boring work
> for me :)
>
>> 2. my-gnus-browse function: Based on the newsgroup name, it calls
>> various functions to find parent url for this article from the article
>> headers. For example, gwene/gmane add a Archived-at header to point to
>> the original article. I had various mailing lists that I found it useful for. 
>>
>> Let me know if you want to see the latter. 
>
> Yes please; I think this is also useful, and on more than one occasion
> I've wanted to easily follow permalinks from Archived-At headers. Maybe
> there's a way to let users distinguish between links in the article
> headers and links in the article body.

Eric,

Sorry, got busy elsewhere. I've posted snippet of my code at:
https://gist.github.com/harizvi/97ee5564047206d6014301c3911d8fbb

Pl take a look.
-- 




  reply	other threads:[~2019-01-10 18:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 18:03 Eric Abrahamsen
2019-01-07 20:15 ` Eric S Fraga
2019-01-07 21:53   ` Eric Abrahamsen
2019-01-08 17:07 ` Haider Rizvi
2019-01-08 20:53   ` Eric Abrahamsen
2019-01-10 18:47     ` Haider Rizvi [this message]
2019-01-10 22:27       ` Eric Abrahamsen
2019-01-10 17:53   ` Eric Abrahamsen
2019-01-10 22:46     ` Eric Abrahamsen
2019-01-11 10:17     ` Eric S Fraga
2019-01-11 20:38       ` Eric Abrahamsen
2019-01-18  9:24         ` Eric S Fraga
2019-01-18  9:32         ` Eric S Fraga
2019-01-18 18:04           ` Eric Abrahamsen
2019-01-19 11:08             ` Eric S Fraga
2019-01-21 18:03               ` Eric Abrahamsen
2019-01-22 23:45                 ` Eric Abrahamsen
2019-01-30  8:13                   ` Eric S Fraga
2019-01-30 19:23                     ` Eric Abrahamsen
2019-01-31  8:38                       ` Eric S Fraga
2019-01-31 17:18                         ` Eric Abrahamsen
2019-01-31 17:25                           ` Eric S Fraga
2019-01-31 17:49                             ` Eric Abrahamsen
2019-01-31 18:31                               ` Eric S Fraga
2019-06-22 10:30         ` Lars Ingebrigtsen
2019-01-22 20:50 ` Clemens Schüller
2019-01-22 20:59   ` Eric Abrahamsen
2019-02-10  8:55     ` Clemens Schüller

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=whyigy37s5oza.fsf@hrizvi-wsm4.internal.salesforce.com \
    --to=harizvi@gmail.com \
    --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).