Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: How to capture URL in messages like this one
Date: Fri, 25 Sep 2020 19:51:49 +0200	[thread overview]
Message-ID: <875z81218q.fsf@gnu.org> (raw)
In-Reply-To: <878scxu84g.fsf@local.lan> (Harry Putnam's message of "Fri, 25 Sep 2020 12:35:43 -0400")

Harry Putnam <reader@newsguy.com> writes:

> That is not the behavior I see and far as I know I have no trick
> changes in cmd sequences.
>
> What I see when I press `w' on that message is summary buffer is that
> it actually activates the URL and calls the web page.

Yes, as the docs state (see the last paragraph):

--8<---------------cut here---------------start------------->8---
w runs the command gnus-summary-browse-url (found in gnus-summary-mode-map),
which is an interactive compiled Lisp function in ‘gnus-sum.el’.

It is bound to w, A w.

(gnus-summary-browse-url &optional EXTERNAL)

  Probably introduced at or before Emacs version 27.1.

Scan the current article body for links, and offer to browse them.

Links are opened using ‘browse-url’ unless a prefix argument is
given: Then ‘browse-url-secondary-browser-function’ is used instead.

If only one link is found, browse that directly, otherwise use
completion to select a link.  The first link marked in the
article text with ‘gnus-collect-urls-primary-text’ is the
default.
--8<---------------cut here---------------end--------------->8---

Bye,
Tassilo


  reply	other threads:[~2020-09-25 17:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25  0:11 Harry Putnam
2020-09-25  1:24 ` Eric Abrahamsen
2020-09-25  7:52   ` Robert Pluim
2020-09-25  8:19     ` Eric S Fraga
2020-09-25  9:02       ` Robert Pluim
2020-09-25  9:15         ` Eric S Fraga
2020-09-25 16:12     ` Eric Abrahamsen
2020-09-25 16:35       ` Harry Putnam
2020-09-25 17:51         ` Tassilo Horn [this message]
2020-09-26 14:13         ` Robert Pluim
2020-09-25 16:28   ` Harry Putnam

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=875z81218q.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=ding@gnus.org \
    --cc=reader@newsguy.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.
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).