unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Sanjoy Mahajan <sanjoy@olin.edu>, notmuch@notmuchmail.org
Subject: Re: all intermediate drafts appear in threads (v0.24.2, Emacs 25.2)
Date: Tue, 18 Jul 2017 07:42:51 -0300	[thread overview]
Message-ID: <87h8yaauvo.fsf@tethera.net> (raw)
In-Reply-To: <877ezcbdvk.fsf@olin.edu>

Sanjoy Mahajan <sanjoy@olin.edu> writes:

> I save an outgoing email as I write it and often (as if it were a
> regular document) by using the usual Emacs key sequence C-x C-s.  With
> notmuch v0.24, notmuch saves a proper draft each time I use C-x C-s.
> The result is a million drafts, which may be good.
>
> However, it means that the thread view (in notmuch-show mode) includes
> the zillion drafts.  Attached is a screenshot of what I mean (sorry that
> it is so small -- I downsampled it to get within the message-size
> limit).  I made the example by sending myself (sanjoy@localhost) a short
> msg.  Then I replied to it with 'r', and saved the reply a few times
> (first with "Draft v1" as the body text, the next time with "Draft v2",
> etc.).

It could be a nice feature to toggle visibility of drafts (and other
excluded messages) in notmuch-show mode. So far nobody wrote such a
thing.

Two things you might find useful to know:

    - you can resume editing a previous draft with 'e'
    - autosaving does not create drafts

If it really bugs you, you could override the binding C-x C-s in
notmuch-show mode.

  parent reply	other threads:[~2017-07-18 10:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 14:38 all intermediate drafts appear in threads (v0.24.2, Emacs 25.2) Sanjoy Mahajan
2017-07-13 16:03 ` Gregor Zattler
2017-07-18 10:42 ` David Bremner [this message]
2017-08-16  1:00   ` Matt Armstrong
2017-08-16  1:13     ` David Bremner
2017-08-16 16:53       ` Matt Armstrong
2017-08-28  2:06   ` Sanjoy Mahajan

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=87h8yaauvo.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    --cc=sanjoy@olin.edu \
    /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).