From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] [PATCH] Use terminal width instead of hardcoded 80 as the wrap length.
Date: Wed, 27 May 2009 12:05:09 -0400 [thread overview]
Message-ID: <1243440258-sup-7690@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1243439667-sup-3947@entry>
Excerpts from William Morgan's message of Wed May 27 11:58:23 -0400 2009:
> Seems like there are three main modes of operation that would be
> desirable:
>
> 1. wrap at 80 chars;
> 2. wrap at current terminal width;
> 3. don't wrap.
>
> (In all cases, existing line breaks in the message are left alone.)
>
> Would a three-way toggle irritate anyone?
Yes, for the message itself, this would work just fine. I'm ok with
the toggle too.
For the header display though, the terminal width should be honoured,
I think.
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090527/4914d9ff/attachment.bin>
next prev parent reply other threads:[~2009-05-27 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 18:19 Mark Alexander
2009-05-23 19:23 ` Ben Walton
[not found] ` <4c4248150905231318kab3819dw68e3a3a614241c0d@mail.gmail.com>
2009-05-24 0:00 ` Ben Walton
2009-05-27 15:58 ` William Morgan
2009-05-27 16:05 ` Ben Walton [this message]
2009-05-27 16:13 ` Mark Alexander
2009-05-27 17:43 ` Nicolas Pouillard
2009-06-06 0:35 ` Ingmar Vanhassel
[not found] ` <1244392518-sup-9746@cabinet>
2009-06-12 19:29 ` William Morgan
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=1243440258-sup-7690@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
/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