From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] Enter on links
Date: Thu, 31 Jan 2008 12:58:13 +0100 [thread overview]
Message-ID: <1201780634-sup-8788@ausone.inria.fr> (raw)
In-Reply-To: <1201739282-sup-912@lenin>
Excerpts from vasudeva's message of Thu Jan 31 01:29:17 +0100 2008:
> 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.
That's not really clean and produce a warning the first time.
I've added this line to one of my hooks (after-poll.rb)
Redwood::Chunk::Text.const_set :WRAP_LEN, 160 unless Redwood::Chunk::Text::WRAP_LEN == 160
--
Nicolas Pouillard aka Ertai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080131/911bc2df/attachment.bin
prev parent reply other threads:[~2008-01-31 11: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
2008-01-30 9:21 ` Nicolas Pouillard
2008-01-31 0:29 ` vasudeva
2008-01-31 11:58 ` Nicolas Pouillard [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1201780634-sup-8788@ausone.inria.fr \
--to=nicolas.pouillard@gmail.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