From: William Morgan <wmorgan-sup@masanjin.net>
To: Sup-talk mailing list <sup-talk@rubyforge.org>
Subject: [sup-talk] line-wrapping
Date: Sat, 19 Dec 2009 10:09:57 -0800 [thread overview]
Message-ID: <1261246000-sup-3729@masanjin.net> (raw)
I've just added a thread-view-mode feature in next where text portions
of messages are now wrapped at the current screen width, and pressing
'w' toggles between that and no wrapping at all.
If anyone wants the old behavior of wrapping at 80 columns regardless of
screen width, you will have to submit a patch to make this a three-way
toggle, or keep your window at 80 chars. :)
(Branch toggle-line-wrap, merged into next.)
Probably a million other Sup things that are higher priority, but this
is what I felt like working on....
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
reply other threads:[~2009-12-19 18:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1261246000-sup-3729@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--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