From: David Bremner <david@tethera.net>
To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH 0/3] Add notmuch-pick to contrib
Date: Sun, 28 Oct 2012 12:16:53 -0300 [thread overview]
Message-ID: <87390ywrru.fsf@zancas.localnet> (raw)
In-Reply-To: <1351337200-18050-1-git-send-email-markwalters1009@gmail.com>
Mark Walters <markwalters1009@gmail.com> writes:
> This is a new version of notmuch-pick (previous version at
> id:"1343164911-31589-1-git-send-email-markwalters1009@gmail.com")following
> suggestions of Tomi and David in that thread. The main change is that
> it is now entirely self contained in contrib: all the user needs to do
> is copy the notmuch-pick.el somewhere in the emacs load path and add
> (require 'notmuch-pick nil t) to their .emacs file.
I have pushed this to contrib.
We do need tests before this goes mainline. What about (untested) having
the tests in contrib/notmuch-pick for now, including as needed from
../../test.
We should mention it in NEWS; at this point I think it is reasonable to
expect to do at least one release with pick in contrib.
As a vague feature request, what about forwarding unknown keys to
the notmuch-show buffer?
d
next prev parent reply other threads:[~2012-10-28 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-27 11:26 [PATCH 0/3] Add notmuch-pick to contrib Mark Walters
2012-10-27 11:26 ` [PATCH 1/3] contrib: add notmuch-pick.el file itself Mark Walters
2012-10-27 17:39 ` Ethan Glasser-Camp
2012-10-27 17:49 ` Mark Walters
2012-10-27 11:26 ` [PATCH 2/3] contrib: add pick README Mark Walters
2012-10-27 12:55 ` Eirik Byrkjeflot Anonsen
2012-10-27 13:38 ` [PATCH v2] " Mark Walters
2012-10-27 11:26 ` [PATCH 3/3] contrib: add pick TODO file Mark Walters
2012-10-27 12:13 ` [PATCH 0/3] Add notmuch-pick to contrib Tomi Ollila
2012-10-28 15:16 ` David Bremner [this message]
2012-10-29 8:28 ` Mark Walters
2012-12-01 21:03 ` Mark Walters
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=87390ywrru.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=markwalters1009@gmail.com \
--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).