From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] How can I make sup use word wrap in the message preview buffer?
Date: Tue, 04 Nov 2008 13:08:14 -0800 [thread overview]
Message-ID: <1225832450-sup-3822@entry> (raw)
In-Reply-To: <1225814283-sup-1783@sgoldmanlinux.tower-research.com>
Hi Steve!
Reformatted excerpts from Steve Goldman's message of 2008-11-04:
> I write a message in emacs and then save it, and then the message is
> displayed to me with signature, etc., in a preview buffer. But the
> paragraphs are displayed as long lines.
Sup displays exactly what the email looks like. Emacs may be displaying
it wrapped, but it isn't actually wrapping it (i.e. putting \n's in.)
You need to press meta-Q or whatever the Emacs command is to actually
wrap those paragraphs.
I don't have Sup do any wrapping because it's better left to the
editor---there may very well be portions of the message you don't want
wrapped (code snippets, log file snippets, etc.)
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-11-04 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 15:59 Steve Goldman
2008-11-04 21:08 ` William Morgan [this message]
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=1225832450-sup-3822@entry \
--to=wmorgan-sup@masanjin.net \
/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