From: Toon Claes <toon@iotcl.com>
To: Yuri D'Elia <wavexx@thregr.org>
Cc: emacs-devel@gnu.org
Subject: Re: Composing messages with format=flowed in Gnus from master branch
Date: Wed, 12 Jul 2017 10:41:51 +0200 (CEST) [thread overview]
Message-ID: <m2lgnu3v3k.fsf@iotcl.com> (raw)
In-Reply-To: <87wp9w5j4f.fsf@wavexx.thregr.org> (Yuri D'Elia's message of "Fri, 05 May 2017 00:53:36 +0200")
Yuri D'Elia <wavexx@thregr.org> writes:
> I'd love this to be handled directly in message.el
> It would be about time.
Yuri, just out of curiosity, did get a chance to work on this?
Is there anything I can help you with?
I'd love to see this happen.
-- Toon
next prev parent reply other threads:[~2017-07-12 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 20:11 Composing messages with format=flowed in Gnus from master branch Joseph Mingrone
2017-05-04 22:53 ` Yuri D'Elia
2017-05-08 20:50 ` Lars Ingebrigtsen
2017-07-12 8:41 ` Toon Claes [this message]
2017-07-17 10:40 ` Yuri D'Elia
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=m2lgnu3v3k.fsf@iotcl.com \
--to=toon@iotcl.com \
--cc=emacs-devel@gnu.org \
--cc=wavexx@thregr.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).