From: Kev <kcf_nospam_maguire@yahoo.com>
Subject: using emavcs to generate format-flowed emails
Date: 17 May 2005 19:22:24 GMT [thread overview]
Message-ID: <slrnd8kh3g.c3n.kcf_nospam_maguire@pc004862.hq.eso.org> (raw)
Hi
I use pine to read/organise/send mails and emacs to compose the text parts.
I would like to be able to compose properly "format=flowed" mails, i.e
according to RFC 2646 (http://www.faqs.org/rfcs/rfc2646.html)
I dont see a really good (perfect) way to do this with emacs. I use "meta-q"
lots to re-format paragraphs after making changes. I can use "meta-x
set-hard-newlines" but that screws up my editing window (an xterm or konsole),
and does not react properly to resizing or meta-q reformatting. At least not
currently, maybe it can be made to do so?
pine itself supports viewing format=flowed well, as does pico for composition.
But I dont like pico :-)
Ideas?
Kevin
next reply other threads:[~2005-05-17 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 19:22 Kev [this message]
2005-05-18 0:46 ` using emavcs to generate format-flowed emails Thien-Thi Nguyen
2005-05-18 7:59 ` Reiner Steib
2005-05-20 15:06 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrnd8kh3g.c3n.kcf_nospam_maguire@pc004862.hq.eso.org \
--to=kcf_nospam_maguire@yahoo.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).