From: Antti Kaihola <akaihola@gmail.com>
To: "john.wyzer" <john.wyzer@gmx.de>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Word wrap for quoted lines
Date: Mon, 23 May 2011 21:38:56 +0300 [thread overview]
Message-ID: <BANLkTinb5qq5t67TSkPGF6mrExaHV=GYCw@mail.gmail.com> (raw)
In-Reply-To: <1305818177-sup-9473@localhost>
Excerpts from Antti Kaihola's message of Tue May 10 09:07:13 +0200 2011:
>> > Hi,
>> >
>> > When reading messages in Sup and expanding quoted lines, long quoted
>> > lines are not word wrapped and thus I can't read all the content.
2011/5/19 john.wyzer <john.wyzer@gmx.de>:
> Ah. Here's a fix:
> https://github.com/rburchell/sup/commit/a60dd01fe297bf3cd5a12c17a40849219c7f8a91
Thanks, it works perfectly! It also seems to live in the wrap_quoted
branch of the sup repository.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-05-23 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 7:07 Antti Kaihola
2011-05-11 12:19 ` Ruthard Baudach
2011-05-19 15:11 ` john.wyzer
2011-05-19 15:16 ` john.wyzer
2011-05-23 18:38 ` Antti Kaihola [this message]
2011-05-24 10:26 ` dtk
2011-05-29 17:34 ` Hamish
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='BANLkTinb5qq5t67TSkPGF6mrExaHV=GYCw@mail.gmail.com' \
--to=akaihola@gmail.com \
--cc=john.wyzer@gmx.de \
--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