From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: links in mail body
Date: Fri, 03 Sep 2010 19:36:02 +0200 [thread overview]
Message-ID: <m3tym6d919.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87tym7gv1u.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> That's because I remembered the name wrong :) It's "Copy Link Location"
> and the "Link" menu is defined in emacs-w3m. So that's that mystery
> solved. I guess, even if w3m is used to display the message (I see
> there's another ongoing thread on that topic), I don't want it
> intervening with links.
I've now implemented the `u' behaviour from emacs-w3m in both text/plain
URLs and in the new HTML mode.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-09-03 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 11:59 Eric Abrahamsen
2010-09-02 12:23 ` Daniel Pittman
2010-09-02 14:35 ` Lars Magne Ingebrigtsen
2010-09-03 7:12 ` Eric Abrahamsen
2010-09-03 17:36 ` Lars Magne Ingebrigtsen [this message]
2010-09-04 2:58 ` Eric Abrahamsen
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=m3tym6d919.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).