From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
notmuch@notmuchmail.org
Subject: Re: Display duplicate messages in emacs front-end
Date: Wed, 09 Nov 2022 23:57:37 -0500 [thread overview]
Message-ID: <87r0yb76f2.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87bkpfu9p1.fsf@caltech.edu>
[-- Attachment #1.1: Type: text/plain, Size: 1137 bytes --]
On Wed 2022-11-09 12:58:18 -0800, Jameson Graef Rollins wrote:
> Personally I think it would make sense to have % cycle through
> duplicates, with some indicator of which duplicate we're currently on.
> I wouldn't even bother with the suggested prefixed behavior if we just
> had the cycle behavior.
In my notmuch-show buffer, there already is an indicator in the
right-hand side of any message that has duplicates, so that part doesn't
require any extra work.
In the event that i get a malicious load of dozens of duplicates and i
identify that one of them is of particular interest, i might want the
current behavior available so that i can get back to "duplicate 17"
without hitting '%' 16 times in a row. But i haven't had that situation
happen yet -- the other situation with a pair of dups is much more
common.
it even happened with this message i'm replying to here, b/c one copy of
the message came straight from Jamie's MUA and the other was routed
through the mailing list. It'd be kind of nice in a nerdy way to make
the mailman footer disappear and reappear just by hitting '%' ☺
--dkg
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2022-11-10 5:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 21:45 Display duplicate messages in emacs front-end David Bremner
2022-07-01 21:45 ` [PATCH 1/9] test: use notmuch_json_show_sanitize more places David Bremner
2022-07-01 21:45 ` [PATCH 2/9] test: define and use notmuch_sexp_*_sanitize functions David Bremner
2022-07-01 21:45 ` [PATCH 3/9] test: add new corpus of duplicate messages David Bremner
2022-07-05 10:07 ` David Bremner
2022-07-01 21:45 ` [PATCH 4/9] CLI/show: initial support for --duplicate for (raw output only) David Bremner
2022-07-01 21:45 ` [PATCH 5/9] CLI/show: support --duplicate for structured output David Bremner
2022-07-01 21:45 ` [PATCH 6/9] emacs/show: provide notmuch-show-choose-duplicate David Bremner
2022-07-01 21:45 ` [PATCH 7/9] emacs/show: display count of duplicates in headerline David Bremner
2022-07-01 21:45 ` [PATCH 8/9] CLI/reply: support --duplicate argument David Bremner
2022-07-01 21:45 ` [PATCH 9/9] emacs/reply: reply to correct duplicate David Bremner
2022-07-30 11:50 ` David Bremner
2022-07-02 1:47 ` Display duplicate messages in emacs front-end David Bremner
2022-11-09 14:53 ` Daniel Kahn Gillmor
2022-11-09 16:55 ` Daniel Kahn Gillmor
2022-11-09 20:58 ` Jameson Graef Rollins
2022-11-10 4:57 ` Daniel Kahn Gillmor [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=87r0yb76f2.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=jrollins@finestructure.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).