From: vasudeva@linkswarm.com (vasudeva)
Subject: [sup-talk] Enter on links
Date: Wed, 30 Jan 2008 19:29:17 -0500 [thread overview]
Message-ID: <1201739282-sup-912@lenin> (raw)
In-Reply-To: <1201684735-sup-6012@ausone.inria.fr>
Excerpts from Nicolas Pouillard's message of Wed Jan 30 04:21:28 -0500 2008:
> Concerning multiline links, I've hacked sup to don't wrap at 80 columns but
> at 160. This fixes the problem at least when the mail has not been wrapped by
> the sender.
Care to share? I'd like to see this so I can figure out a way to make
sup wrap where I want to.
--
linkswarm.com :: Collaborative Insolence
vasudeva.linkswarm.com/gallery :: For The Faint of Heart
next prev parent reply other threads:[~2008-01-31 0:29 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
2008-01-30 9:21 ` Nicolas Pouillard
2008-01-31 0:29 ` vasudeva [this message]
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=1201739282-sup-912@lenin \
--to=vasudeva@linkswarm.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