From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Enter on links
Date: Tue, 29 Jan 2008 19:58:15 -0800 [thread overview]
Message-ID: <1201665171-sup-7233@south> (raw)
In-Reply-To: <1201636010-sup-8816@buckwheat>
Reformatted excerpts from Daniel Wagner's message of 2008-01-29:
> One thing I find myself doing all the time is highlighting a web
> address and pasting it into Firefox. For long URLs (a sad but common
> truth), it's even more annoying... hit 'D' to open it up in vim,
> navigate to the link, Jx a few times, then *finally* copy and paste.
> Is there a better way to do this?
On my system this is actually handled by the terminal (I'm using
gnome-terminal) directly. You can click on any link and it launches the
default web browser.
> So, here's my real question: how hard would it be for me to allow
> Enter to try to open a (potentially-multiline) link? I am aware that
> there are some subtleties about detecting addresses' beginning/ending
> points here; what I'm really interested in is whether it is easy
> within sup's architecture.
Fairly easy, with some caveats. Sup is fundamentally line-based, at
least at this point. A URL-detecting regex could pick out individual
URLs from the message, pack them into their own kind of Chunk (see
message-chunks.rb) the same way that quoted regions and attachments are
handled, and the rest would follow more or less trivially.
That might make the email look a little weird, as any URLs would sit on
their own line. But Sup has never shied away from reformatting emails
for display. :)
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-01-30 3:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 19:47 Daniel Wagner
2008-01-30 3:58 ` William Morgan [this message]
2008-01-30 9:21 ` Nicolas Pouillard
2008-01-31 0:29 ` vasudeva
2008-01-31 11:58 ` Nicolas Pouillard
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=1201665171-sup-7233@south \
--to=wmorgan-sup@masanjin.net \
/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