unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Peter Wang <novalazy@gmail.com>
To: Jani Nikula <jani@nikula.org>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] show: add In-reply-to, References fields to structured formats
Date: Mon, 13 Jan 2014 08:08:36 +1100	[thread overview]
Message-ID: <20140113080836.GA1138@hili.localdomain> (raw)
In-Reply-To: <878uulush7.fsf@nikula.org>

On Sun, 12 Jan 2014 17:31:32 +0200, Jani Nikula <jani@nikula.org> wrote:
> On Sun, 12 Jan 2014, Peter Wang <novalazy@gmail.com> wrote:
> > This is useful when 'show' is used to retrieve a draft message
> > which is in reply to another message.
> 
> I'd like to know more about *how* this is useful. Indeed the whole big
> picture about supporting draft or postponed messages is foggy. I would
> like to have some clarity about that first.
> 
> Apparently the idea is to index draft messages. How do you save them?
> What guarantees are there that they look enough like real messages that
> they get indexed? Does this patch mean that the idea is to resume draft
> messages using the structured formats instead of opening the raw file?
> Why?  What do you plan to do with the saved draft? And so on...

I didn't realise storing drafts in your Maildir was unusual.

A draft message (including its attachments) may be added to a Maildir
folder with notmuch insert or notmuch-deliver, and then tagged.
The message must look enough like a real message for indexing but it is
not hard for an email client to arrange -- the message is ostensibly to
be sent anyway.  Unlike saving in a local file, keeping the draft in a
central mail store means it will be accessible anywhere that you can
access the rest of your mail.

Draft messages may be retrieved for previewing or resumption with
notmuch show, like other messages.  The raw file may be on another
machine so it is not always possible to read it directly.  The advantage
of using a structured output format instead of the raw output format is
the same as for any other message -- notmuch has already parsed it for
you.  The disadvantage is that notmuch show's structured output only
presents a subset of headers, so other headers will be lost.
(This suggests an alternative change if notmuch maintainers are
receptive.)

Indexed draft messages will, by default, show up in normal display
so they will need to be hidden with notmuch search exclusions.
Drafts may tagged with 'delete' for eventual removal.

Peter

      reply	other threads:[~2014-01-12 21:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12  5:00 [PATCH] show: add In-reply-to, References fields to structured formats Peter Wang
2014-01-12 15:31 ` Jani Nikula
2014-01-12 21:08   ` Peter Wang [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=20140113080836.GA1138@hili.localdomain \
    --to=novalazy@gmail.com \
    --cc=jani@nikula.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).