From: Robert Pluim <rpluim@gmail.com>
To: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: How to capture URL in messages like this one
Date: Sat, 26 Sep 2020 16:13:58 +0200 [thread overview]
Message-ID: <m2pn681v89.fsf@gmail.com> (raw)
In-Reply-To: <878scxu84g.fsf@local.lan> (Harry Putnam's message of "Fri, 25 Sep 2020 12:35:43 -0400")
>>>>> On Fri, 25 Sep 2020 12:35:43 -0400, Harry Putnam <reader@newsguy.com> said:
Harry> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> Robert Pluim <rpluim@gmail.com> writes:
>>
>>>>>>>> On Thu, 24 Sep 2020 18:24:58 -0700, Eric Abrahamsen <eric@ericabrahamsen.net> said:
>>>
Eric> Harry Putnam <reader@newsguy.com> writes:
>>> >> How to capture the url in message such as this:
>>> >> Mousing over the link shows the URL in echo area but there seems no
>>> >> way to copy it. It just disappears if you try to mouse to it.
>>>
Eric> <TAB> to get to the url, and "w" to copy it.
>>>
Eric> That sure looks like spam!
>>>
>>> From the summary mode you donʼt need to TAB, 'w' will pop up a buffer
>>> containing the links it finds in the selected article.
Harry> Harry Responds:
Harry> That is not the behavior I see and far as I know I have no trick
Harry> changes in cmd sequences.
Harry> What I see when I press `w' on that message is summary buffer is that
Harry> it actually activates the URL and calls the web page.
Indeed, I misunderstood what you were asking for. Of course if you
browse such an url using eww (and honestly, who doesnʼt?), then you
can use 'w' in the *eww buffer to copy the url :-)
Robert
next prev parent reply other threads:[~2020-09-26 14:14 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
2020-09-26 14:13 ` Robert Pluim [this message]
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=m2pn681v89.fsf@gmail.com \
--to=rpluim@gmail.com \
--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).