unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Subject: Re: [RFC PATCH] show: Add support for -format=raw -body=false
Date: Mon, 15 Feb 2021 17:19:35 -0400	[thread overview]
Message-ID: <877dn9t4ew.fsf@tethera.net> (raw)
In-Reply-To: <cun7dnmorde.fsf@dme.org>

David Edmondson <dme@dme.org> writes:

> On Thursday, 2021-02-04 at 22:33:06 -04, David Bremner wrote:
>
>> David Edmondson <dme@dme.org> writes:
>>
>>>> I'm just nervous about more legacy formats. I think we will get the
>>>> arbitrary headers thing working eventually, but I can see it might take
>>>> some time.
>>>
>>> Are we ever likely to get rid of the raw format? I use it quite a bit,
>>> and it seems to be relatively low complexity and simple to support.
>>
>> It isn't completely without maintenance overhead, but I agree it's not
>> going away. I can live with the body=false option if you think it's
>> better / more feasible than the arbitrary headers series.
>
> At the moment I'm using the former because the latter is missing, but in
> principle I think that they might fill different needs. Could we have
> both?

On the scale of things, the extra code is not a big deal, so sure.

d

      reply	other threads:[~2021-02-15 21:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-17 18:37 [RFC PATCH] show: Add support for -format=raw -body=false David Edmondson
2021-01-18 17:37 ` David Bremner
2021-01-18 17:58   ` David Edmondson
2021-01-18 18:28     ` David Bremner
2021-01-18 18:39       ` David Edmondson
2021-01-18 19:39         ` Tomi Ollila
2021-02-05  2:33         ` David Bremner
2021-02-05  8:23           ` David Edmondson
2021-02-15 21:19             ` David Bremner [this message]

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=877dn9t4ew.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=dme@dme.org \
    --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).