From: Pierre Neidhardt <mail@ambrevar.xyz>
To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Subject: Re: Reply inline in notmuch-show buffer, "mu4e-conversation style"
Date: Wed, 10 Apr 2019 15:27:14 +0200 [thread overview]
Message-ID: <87pnpu9ej1.fsf@ambrevar.xyz> (raw)
In-Reply-To: <m2wok212y3.fsf@dme.org>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
David Edmondson <dme@dme.org> writes:
> Yes. My argument was not that we shouldn't have this, just that I wonder
> if it results in a good workflow for people who are not using
> notmuch/mu4e/gmail (or any other client that shares the same kind of
> thread view).
With about 1 year of experience using mu4e-conversation, I found that it
works really well, actually better in most cases since it does not
"pollute" emails with forgotten citations.
Most people use Gmail or clients that support threading, in which case this is
really a good fit.
But really if we think about the workflow of "most people", then most of
the time citations are ignored (e.g. top-posting) and just pollute the
rest of the emails. In those cases (the majority?) a non-threaded
workflow does not really work I think.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-04-10 13:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 10:46 Reply inline in notmuch-show buffer, "mu4e-conversation style" Pierre Neidhardt
2019-03-19 14:03 ` Pierre Neidhardt
2019-04-03 9:12 ` Pierre Neidhardt
2019-04-03 11:08 ` David Edmondson
2019-04-10 10:53 ` Pierre Neidhardt
2019-04-10 11:19 ` David Edmondson
2019-04-10 11:52 ` Pierre Neidhardt
2019-04-10 12:04 ` David Edmondson
2019-04-10 13:27 ` Pierre Neidhardt [this message]
2019-04-10 14:19 ` David Edmondson
2019-04-10 14:38 ` Pierre Neidhardt
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=87pnpu9ej1.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=dme@dme.org \
--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).