From: "Jörg Volbers" <joerg@joergvolbers.de>
To: Tomi Ollila <tomi.ollila@iki.fi>,
David Bremner <david@tethera.net>,
Emmanuel Beffara <manu@beffara.org>,
notmuch@notmuchmail.org
Subject: Re: feature request: parameters for reply templates
Date: Wed, 13 May 2020 10:03:12 +0200 [thread overview]
Message-ID: <87eero5kjj.fsf@joergvolbers.de> (raw)
In-Reply-To: <m2pnb87szr.fsf@guru.guru-group.fi>
OK, seems there is something I do not understand. What do you mean
with "spec in mind"?
JV
Tomi Ollila <tomi.ollila@iki.fi> writes:
> On Tue, May 12 2020, Jörg Volbers wrote:
>
>>> My gut reaction is that doing more formatting in notmuch reply
>>> is probably a mistake; it's hard enough to get two users to
>>> agree on these kind of customizations, never mind two
>>> different MUAs. Probably what we need to do is make sure the
>>> structured (json/s-expr) output has enough information for
>>> clients to do what they need/want to do.
>>
>> I agree, but why not add some switches which allow to turn some
>> aspects of the reply output on or off? I am thinking here in
>> particular of the parts which are not plain text. Since not
>> every mail has an attachment, it makes perfect sense to let
>> the user decide whether a reply includes a text reference to
>> the attachment. A simple on-off-switch would be enough.
>
> Did you have spec in mind ? =D
>
>>
>> JV
>>
>
> Tomi
--
http://www.joergvolbers.de
https://fu-berlin.academia.edu/joergvolbers
https://www.geisteswissenschaften.fu-berlin.de/we01/institut/mitarbeiter/koop_gaeste/volbers/index.html
next prev parent reply other threads:[~2020-05-13 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 21:15 feature request: parameters for reply templates Emmanuel Beffara
2020-05-12 11:01 ` David Bremner
2020-05-12 18:08 ` Jörg Volbers
2020-05-12 21:17 ` Tomi Ollila
2020-05-13 8:03 ` Jörg Volbers [this message]
2020-05-13 19:51 ` Tomi Ollila
2020-05-15 17:27 ` Jörg Volbers
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=87eero5kjj.fsf@joergvolbers.de \
--to=joerg@joergvolbers.de \
--cc=david@tethera.net \
--cc=manu@beffara.org \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).