From: Anthony Martinez <pi+sup@pihost.us>
To: sup-talk <sup-talk@rubyforge.org>, sup-devel <sup-devel@rubyforge.org>
Subject: [sup-talk] [CORRECTED PATCH] If we can get the terminal width, use that for WRAP_LEN.
Date: Tue, 03 Nov 2009 20:51:46 -0700 [thread overview]
Message-ID: <1257306460-sup-1506@home.mrtheplague.net> (raw)
In-Reply-To: <1257303919-30524-1-git-send-email-pi+sup@pihost.us>
I find that this provides a much smoother terminal experience,
especially with elinks configured to dump to the same size in hook
scripts.
At least on Linux, "stty size"'s second numerical output is the number
of columns, and if that fails somehow, sup will continue to happily
default to 80.
---
lib/sup/message-chunks.rb | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/lib/sup/message-chunks.rb b/lib/sup/message-chunks.rb
index 581b707..56ddf1e 100644
--- a/lib/sup/message-chunks.rb
+++ b/lib/sup/message-chunks.rb
@@ -41,7 +41,8 @@ end
module Redwood
module Chunk
- WRAP_LEN = 80 # wrap messages and text attachments at this width
+ TERM_WIDTH = `stty size 2>/dev/null`.split[1].to_i # to_i returns 0 if it fails.
+ WRAP_LEN = TERM_WIDTH > 0 && TERM_WIDTH || 80 # wrap messages and text attachments at this width
class Attachment
HookManager.register "mime-decode", <<EOS
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-11-04 3:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 3:05 [sup-talk] [PATCH] If we have a COLUMNS environment variable, wrap to that instead of 80 Anthony Martinez
2009-11-04 3:22 ` Anthony Martinez
2009-11-04 3:51 ` Anthony Martinez [this message]
2009-11-04 19:06 ` Mark Alexander
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=1257306460-sup-1506@home.mrtheplague.net \
--to=pi+sup@pihost.us \
--cc=sup-devel@rubyforge.org \
--cc=sup-talk@rubyforge.org \
/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