From: Matt Armstrong <matt+dated+200201181334.2d810e@lickey.com>
Cc: ding@gnus.org
Subject: Re: Support for encoding format=flowed (RFC 2646)
Date: Sun, 13 Jan 2002 13:53:33 -0700 [thread overview]
Message-ID: <874rlqrn02.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <iluadvknzru.fsf@extundo.com>
Simon Josefsson <jas@extundo.com> writes:
> I have checked in preliminary format=flowed support. The
> missing
> functionality right now is doing the right thing when following
> up >
> > on
> an article.
> > How to use: Enable `use-hard-newlines' (see emacs manual) in
> > the
> message buffer, and the code should fill and format=flow encode
> your
> article according to the soft/hard newlines in the buffer.
> Hint: I
> find `use-hard-newlines' useless without something similar to
> M-x
> longlines-show-hard-newlines RET from longlines.el.
> > (I also changed the format=flowed decoding code to flow the >
> > > message > to
> the width of the window.)
> > As you can see, the above
> paragraphs are filled nicely
> while this one sentences isn't.
> This is because I hit RET after
> each of these lines, without
> using M-q on the paragraph.
> > > --
matt
Seems to work, with some problems that probably aren't all Gnus
related. I have this in my .gnus:
(defun my-message-setup-hook ()
(use-hard-newlines 1 'always)
(require 'longlines)
(set (make-local-variable 'longlines-show-hard-newlines) t))
(add-hook 'gnus-message-setup-hook 'my-message-setup-hook)
First, when I turn on longlines minor mode, my signature gets
glommed onto the text I am replying to (see above). This is
probably a longlines thing. Hmm...
Second, when Gnus inserts my .signature, they get inserted with
hard newlines. So others see a blank line after my '--' signature
line.
Third, maybe this is a longlines thing, but I can't bear to edit a
message without a blank line between each paragraph. Is there a
way to get longlines to do that for me?
Fourth, is inserting two blank lines for every hard newline the
right thing to do? I bet my elisp above is going to look funny.
next prev parent reply other threads:[~2002-01-13 20:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 1:06 Simon Josefsson
2002-01-12 1:27 ` Simon Josefsson
2002-01-12 10:01 ` Kai Großjohann
2002-01-12 11:39 ` Simon Josefsson
2002-01-12 13:18 ` Simon Josefsson
2002-01-19 22:00 ` Lars Magne Ingebrigtsen
2002-01-20 17:11 ` Kai Großjohann
2002-01-20 17:21 ` Simon Josefsson
2002-01-20 17:30 ` Lars Magne Ingebrigtsen
2002-01-21 10:59 ` Malcolm Purvis
2002-01-13 20:53 ` Matt Armstrong [this message]
2002-01-13 20:58 ` Matt Armstrong
2002-01-14 19:36 ` Matt Armstrong
2002-02-05 14:56 ` Niklas Morberg
2002-02-05 17:25 ` Matt Armstrong
2002-02-05 19:18 ` Simon Josefsson
2002-02-05 22:30 ` Matt Armstrong
2002-02-06 7:31 ` Niklas Morberg
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=874rlqrn02.fsf@squeaker.lickey.com \
--to=matt+dated+200201181334.2d810e@lickey.com \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).