From: "Amadeusz Żołnowski" <aidecoe@aidecoe.name>
To: Adam Wolfe Gordon <awg+notmuch@xvx.ca>
Cc: notmuch@notmuchmail.org
Subject: Re: miraculous from: field
Date: Wed, 08 May 2013 22:00:49 +0200 [thread overview]
Message-ID: <87ip2ts0lq.fsf@raeviah.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <CAMoJFUt6+a+d=RVyuG0dgebPRbX1HYSMDP=Z2J2p8op6jJNjSQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
Hi!
I am resurrecting quite an old thread…
Adam Wolfe Gordon <awg+notmuch@xvx.ca> writes:
> On Wed, Jun 20, 2012 at 5:33 AM, Jani Nikula <jani@nikula.org> wrote:
>> The reply template comes from 'notmuch reply' cli command, while the
>> forwarding is internal to the emacs ui. I don't have any quick solutions,
>> but perhaps in the long run we should do the forwarding template in the cli
>> too.
>
> I think this is the right approach. Someone suggested a while ago that
> we have a notmuch compose, which would do new message creation (for
> frontends that can't do it themselves), reply, and forward in one
> place. It would probably support raw and JSON like the current reply
> does.
>
> Something I'll do if I find some time, but would be happy to see
> someone else work on :-).
It seems nobody has done work yet. Could you reconsider adding this
feature? I am really looking forward to it and I think I am not alone.
Regards,
--
Amadeusz Żołnowski
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-05-08 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 11:25 miraculous from: field David Belohrad
2012-06-20 11:33 ` Jani Nikula
2012-06-21 3:57 ` Adam Wolfe Gordon
2013-05-08 20:00 ` Amadeusz Żołnowski [this message]
2012-06-20 19:35 ` Austin Clements
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ip2ts0lq.fsf@raeviah.i-did-not-set--mail-host-address--so-tickle-me \
--to=aidecoe@aidecoe.name \
--cc=awg+notmuch@xvx.ca \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).