From: Jameson Rollins <jrollins@finestructure.net>
To: Dirk Hohndel <hohndel@infradead.org>,
Carl Worth <cworth@cworth.org>,
notmuch@notmuchmail.org
Subject: draft handling [was: Re: Plans for the 0.2 release (this week)]
Date: Thu, 08 Apr 2010 11:57:54 -0400 [thread overview]
Message-ID: <87ochuaqd9.fsf@servo.finestructure.net> (raw)
In-Reply-To: <m3tyrmgfdk.fsf@x200.gr8dns.org>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
On Thu, 08 Apr 2010 07:58:47 -0700, Dirk Hohndel <hohndel@infradead.org> wrote:
> > And as for drafts, they could be easily indexed and managed by the UI if
> > the folder: search term is available.
>
> Hmm - haven't even thought about drafts, yet. How would the UI deal with
> those?
My idea is the following:
Currently for me drafts are stored in ~/.mail/drafts. If we have
folder: searching, then I can starting indexing my drafts directory and
apply the following post-new filter:
notmuch tag +draft -inbox -unread -- folder:drafts
I'll then make a simple elisp "resume" function that is available for
resuming draft messages, that would be available when viewing messages
From a draft search results.
One could also imagine a "notmuch-draft" emacs mode that would provide
functions specifically for viewing and resuming draft messages.
Anyway, my plan was to work on all of this when some sane way of
indexing draft messages was available (ie. folder: searching).
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2010-04-08 15:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 22:12 Plans for the 0.2 release (this week) Carl Worth
2010-04-07 22:23 ` James Westby
2010-04-08 14:34 ` Mike Kelly
2010-04-12 18:27 ` Mike Kelly
2010-04-08 7:47 ` Sebastian Spaeth
2010-04-08 12:21 ` Anthony Towns
2010-04-13 16:02 ` Carl Worth
2010-04-08 8:13 ` David Edmondson
2010-04-08 14:54 ` Dirk Hohndel
2010-04-08 13:52 ` Jameson Rollins
2010-04-08 14:55 ` Dirk Hohndel
2010-04-13 16:06 ` Carl Worth
2010-04-08 14:03 ` Jameson Rollins
2010-04-08 14:58 ` Dirk Hohndel
2010-04-08 15:21 ` Michal Sojka
2010-04-08 15:57 ` Jameson Rollins [this message]
2010-04-08 21:28 ` Carl Worth
2010-04-08 21:38 ` Jameson Rollins
2010-04-09 0:22 ` Mike Kelly
2010-04-08 15:30 ` Mike Kelly
2010-04-09 3:22 ` Anthony Towns
2010-04-09 4:25 ` Michal Sojka
2010-04-09 16:21 ` micah anderson
2010-04-08 14:22 ` Michal Sojka
2010-04-09 4:32 ` Michal Sojka
2010-04-09 7:35 ` Sebastian Spaeth
2010-04-09 17:14 ` Dirk Hohndel
2010-04-10 3:06 ` Carl n∅tmuch 䚳 Worth
2010-04-10 4:44 ` Dirk Hohndel
2010-04-10 4:47 ` Dirk Hohndel
2010-04-10 13:05 ` Jameson Rollins
2010-04-10 14:39 ` Dirk Hohndel
2010-04-10 9:02 ` Michal Sojka
2010-04-10 13:06 ` Jameson Rollins
2010-04-10 13:09 ` Jameson Rollins
2010-04-10 14:06 ` Michael Elkins
2010-04-10 19:58 ` Michal Sojka
2010-04-10 13:52 ` Sebastian Spaeth
2010-04-10 13:56 ` Jameson Rollins
2010-04-10 14:41 ` Dirk Hohndel
2010-04-13 17:20 ` Carl Worth
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=87ochuaqd9.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=cworth@cworth.org \
--cc=hohndel@infradead.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).