From: Hannu Hartikainen <hannu@hrtk.in>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: Yet another revision of --format=pretty
Date: Tue, 13 Jul 2021 15:07:15 +0300 [thread overview]
Message-ID: <60ed81f4.1c69fb81.7b6b6.aadf@mx.google.com> (raw)
In-Reply-To: <87eec386ie.fsf@tethera.net>
On Mon, 12 Jul 2021 20:19:37 -0300, David Bremner <david@tethera.net> wrote:
> The main thing I was worried about was the vim interface and Felipe
> confirmed that it does not use text format at all. There are no doubt
> user scripts out there that will have to be adjusted, so it would have
> to be a long-ish deprecation, but we've done that before.
Cool!
> I guess the question for you is if the format will still be useful for
> you if we need to include _some_ metadata in order to replace use cases
> for text format? I'm thinking of potentially a couple of X-Notmuch-*
> headers. But that in itself is another design discussion.
I'm fine with that. There also *could* be a way to configure which
headers are displayed; Tomi suggested that the colors should be
configurable, and I think configuring pairs of header+color would be one
option of implementing that. But I need to dogfood some more before I
can confidently say what I like best.
> I think having some quick mail pager for search results makes sense. I'm
> not sure how far in the direction of MH we should go, but we can look at
> each potential change as it arrives.
I'd never heard of MH before. I'll need to try it out :) (For those not
familiar, it can be found at https://www.nongnu.org/nmh/ .) It sounds
philosophically like what I want from a CLI mail client. But then again
I really don't need much. I'm writing this message with this shell
function (and Neovim) and I think it's good enough. :)
nr() {
draft=$(mktemp $HOME/draft-XXXX)
$notmuch reply $1 > "$draft" || return
nvim -c 'set filetype=mail' "$draft" || return
cat "$draft"
echo
echo "Press ENTER to send (Ctrl-C to cancel)"
read || return
cat "$draft" | msmtp -t || return
rm "$draft"
}
Hannu
next prev parent reply other threads:[~2021-07-13 12:07 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 [this message]
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
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=60ed81f4.1c69fb81.7b6b6.aadf@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).