unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Hannu Hartikainen <hannu@hrtk.in>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] cli/show: add --format=pretty
Date: Mon, 05 Jul 2021 16:31:08 +0300	[thread overview]
Message-ID: <60e3099d.1c69fb81.75191.5f67@mx.google.com> (raw)
In-Reply-To: <87lf6m6t56.fsf@tethera.net>

Hi!

Thanks for starting discussion on the matter. Do feel free to tell me if
I have the completely wrong idea about project goals.

On Sun, 04 Jul 2021 11:38:45 -0300, David Bremner <david@tethera.net> wrote:
> This is not really directed at Hannu, but at the notmuch community. As
> you can imagine I'm not super enthusiastic an every growing number of
> output formats to maintain.

I can appreciate that. I've maintained open source software before and I
know people come up with the weirdest feature requests that simply don't
fit the scenario I'm building the software for. If this text format that
I personally like to use isn't good for the project, it definitely
should not be merged.

What do you see as the mission statement for notmuch-cli? I'd like to
make it ergonomic enough to be usable without a MUA, and it's really
close already. But if notmuch-cli is meant to be something completely
different I might just have my own set of patches or consider starting
my own project.

> One thing the old format did not do, but a generically useful on the
> command-line format probably should is deal with signature verification
> and decryption. There is obviously potential for visual spoofing, but
> maybe color can help.

I'm pretty sure you can embed ^[[31mANSI escapes^[[0m in email and
they'll be displayed by `notmuch show` as color in a typical terminal.
Not sure if anyone should be worried about attacks specifically against
notmuch users, though.

> In my experience, notmuch show --format=raw works pretty well
> for this. There was an issue with encoded line endings but that is fixed
> in git 2.32. What advantage does this new format bring for patches?

--format=pretty is not any better than --format=raw for use with git-am
but the point is that it's as good. I have the shell alias ns="notmuch
show --format=pretty" and I can use something like `ns tag:unread` for
reading and `ns id:some-id | git am` for applying patches. I personally
really, really like simple things that work for multiple purposes.

For human consumption the pretty format is nicer than the raw format,
and it also supports showing multiple messages.

Hannu

      reply	other threads:[~2021-07-05 13:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19 20:38 [PATCH] cli/show: add --format=pretty Hannu Hartikainen
2021-06-22 12:34 ` [PATCH] cli/show: add --color/--no-color Hannu Hartikainen
2021-07-12  8:38   ` Yet another revision of --format=pretty Hannu Hartikainen
2021-07-12  8:38     ` [PATCH v3 1/2] cli/show: add --format=pretty Hannu Hartikainen
2021-07-12 23:40       ` David Bremner
2021-07-13 10:24         ` David Bremner
2021-07-13 11:50           ` Hannu Hartikainen
2021-07-12  8:38     ` [PATCH v3 2/2] cli/show: add color for --format=pretty Hannu Hartikainen
2021-07-12 23:19     ` Yet another revision of --format=pretty David Bremner
2021-07-13 12:07       ` Hannu Hartikainen
2021-07-02 20:31 ` [PATCH v2] cli/show: add --format=pretty Hannu Hartikainen
2021-07-04  9:40   ` Tomi Ollila
2021-07-04 11:54     ` Hannu Hartikainen
2021-07-04 14:38 ` [PATCH] " David Bremner
2021-07-05 13:31   ` Hannu Hartikainen [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=60e3099d.1c69fb81.75191.5f67@mx.google.com \
    --to=hannu@hrtk.in \
    --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).