unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Peter Salazar <cycleofsong@gmail.com>
To: Tomi Ollila <tomi.ollila@iki.fi>
Cc: notmuch@notmuchmail.org
Subject: Re: how to make return follow hyperlink?
Date: Fri, 28 Aug 2015 14:13:13 -0400	[thread overview]
Message-ID: <CAE+_6TxRrTXdjwiePOv2LTrid2R65omY0s_wGWRD=1r4y-T_Qw@mail.gmail.com> (raw)
In-Reply-To: <m2twrkufct.fsf@guru.guru-group.fi>

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

Thanks for all the responses! Mark, where could we find the patch you
mentioned? I wouldn't know how to test/update it, but maybe someone else on
the list has the requisite hacking skills...

On Fri, Aug 28, 2015 at 1:55 AM, Tomi Ollila <tomi.ollila@iki.fi> wrote:

> On Wed, Aug 26 2015, Peter Salazar <cycleofsong@gmail.com> wrote:
>
> > How do I make it so that hitting RET on a hyperlink follows it? Is there
> a
> > setting analogous to org-return-follows-link? I often have links in
> > incoming emails, and I'd like to be able to open them in my browser with
> > one keystroke.
>
> BTW: the interesting thing is that in text/plain content id: links already
> do something -- and e.g. https?: do not. in text/html content I get
> 'No usable browser found'(*) when pressing RET on top of http: link so it
> must be doing something ;)
>
> Tomi
>
> (*) Note to self: hack something to show the link using (message ...) in
> this case.
>
> >
> > Thanks!
>

[-- Attachment #2: Type: text/html, Size: 1431 bytes --]

      reply	other threads:[~2015-08-28 18:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 19:10 how to make return follow hyperlink? Peter Salazar
2015-08-27  8:35 ` David Edmondson
2015-08-27 10:53   ` Suvayu Ali
2015-08-27 18:24 ` Mark Walters
2015-08-28  5:55 ` Tomi Ollila
2015-08-28 18:13   ` Peter Salazar [this message]

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE+_6TxRrTXdjwiePOv2LTrid2R65omY0s_wGWRD=1r4y-T_Qw@mail.gmail.com' \
    --to=cycleofsong@gmail.com \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    /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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).