From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: Re: v2 WIP commands to choose duplicates in emacs interface
Date: Wed, 29 Jun 2022 09:15:40 -0300 [thread overview]
Message-ID: <87v8sjacnn.fsf@tethera.net> (raw)
In-Reply-To: <20220619232152.846823-1-david@tethera.net>
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
David Bremner <david@tethera.net> writes:
> It needs better error handling, and one could imagine a nicer UI
> (completion maybe? keys to move to next or previous duplicate?). It
> also needs more tests, but before I invest in that I want to fix the
> screen appearance; the main change here is the n/d indicator at
> the right margin.
Attached is a screen shot of
(notmuch-show "id:87a6cp2s8x.fsf@no.workgroup")
with (a revised version of) these patches applied. You can see the 1/2
along the right margin for my messages, this is because of Fcc.
[-- Attachment #2: 2022-06-29-091327_1276x406_scrot.png --]
[-- Type: image/png, Size: 138107 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2022-06-29 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 23:21 v2 WIP commands to choose duplicates in emacs interface David Bremner
2022-06-19 23:21 ` [RFC PATCH v2 1/7] test: use notmuch_json_show_sanitize more places David Bremner
2022-06-19 23:21 ` [RFC PATCH v2 2/7] test: define and use notmuch_sexp_*_sanitize functions David Bremner
2022-06-19 23:21 ` [RFC PATCH v2 3/7] test: add new corpus of duplicate messages David Bremner
2022-06-19 23:21 ` [RFC PATCH v2 4/7] CLI/show: WIP support --duplicate for raw output David Bremner
2022-06-19 23:21 ` [RFC PATCH v2 5/7] WIP: support show --duplicate for structured output David Bremner
2022-06-19 23:21 ` [RFC PATCH v2 6/7] WIP/emacs: replace message with different duplicate David Bremner
2022-06-19 23:21 ` [RFC PATCH v2 7/7] WIP/emacs: display count of duplicates in headerline David Bremner
2022-06-29 12:15 ` 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=87v8sjacnn.fsf@tethera.net \
--to=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).