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 13:52:25 +0200 [thread overview]
Message-ID: <87v9zm9ix2.fsf@ambrevar.xyz> (raw)
In-Reply-To: <m2ef6a2jm4.fsf@dme.org>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
David Edmondson <dme@dme.org> writes:
> How? Don't I still have to hit one key?
No, you just start writing at the end of the buffer, this area is then
marked as writable.
>> - No need to play with buffers to display both the thread and the composition.
>
> If a thread is any length, I will want to split the window to show older
> mail while I'm writing my comments at the bottom of the thread. So there
> might only be one buffer, but two windows, so I'm not sure of the
> benefit.
True. But if the thread is not that long, or if we only want to look at
the last thread, then we don't need to. With a separate buffer, we
always have to play with the buffers to display them side by side, for instance.
> Well, this presumes a particular workflow and set of mail
> clients. Whether it's a good idea to top post without the bottom is
> debatable, I think.
I'm confused: can it be top-posting if there is no citation?
Citations don't offer much guarantee in terms of data integrity. If
someone wants to read the previous message, they should open the
previous message, regardless of the workflow / client I think.
All this can be made optional and configurable.
--
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 11:52 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 [this message]
2019-04-10 12:04 ` David Edmondson
2019-04-10 13:27 ` Pierre Neidhardt
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=87v9zm9ix2.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).