From: David Edmondson <dme@dme.org>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [RFC PATCH] show: Add support for -format=raw -body=false
Date: Mon, 18 Jan 2021 18:39:13 +0000 [thread overview]
Message-ID: <cunh7new0mm.fsf@dme.org> (raw)
In-Reply-To: <87eeiigkwd.fsf@tethera.net>
On Monday, 2021-01-18 at 14:28:02 -04, David Bremner wrote:
> David Edmondson <dme@dme.org> writes:
>> Now, it would be nice to be able to say something like...
>>
>> notmuch show --format=sexp --body=false \
>> --headers=received-by,face,x-face \
>> id:foo
>>
>> ...to get some extra headers in the sexp output, but I didn't look at it
>> yet.
>
> There was a series at id:20191122230730.35712-2-johan.parin@gmail.com
> that got stalled due to (I think) some issues with passing around
> configuration information.
I will go and look at this.
>> The proposed change seems like a simple, obvious improvement that is
>> entirely in-line with the existing interface and implementation. Is
>> there any reason not to do it?
>
> 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.
dme.
--
They must have taken my marbles away.
next prev parent reply other threads:[~2021-01-18 18:39 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 [this message]
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
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=cunh7new0mm.fsf@dme.org \
--to=dme@dme.org \
--cc=david@tethera.net \
--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).