Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Ruthard Baudach <rthd@web.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Word wrap for quoted lines
Date: Wed, 11 May 2011 14:19:25 +0200	[thread overview]
Message-ID: <1305116205-sup-2345@PrxServer3> (raw)
In-Reply-To: <BANLkTimTBRbHOTPDpE=qFZetZyccdCdt6w@mail.gmail.com>

> === Antti Kaihola schrieb am 2011-05-10 09:07: === <
> 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.
> Non-quoted content wraps as expected.

The left and right arrow keys give you access to text right or left of
your screen.

Of course it would be nice, if sup would wrap these lines as well.

Ruthard
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2011-05-22 21:50 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 [this message]
2011-05-19 15:11 ` john.wyzer
2011-05-19 15:16   ` john.wyzer
2011-05-23 18:38     ` Antti Kaihola
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=1305116205-sup-2345@PrxServer3 \
    --to=rthd@web.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