Re: [notmuch] [PATCH 2/2] notmuch list: A new command to produce various lists.

diff --git a/2d/789a3451977c29adb42ad1145e966e7dce097a b/2d/789a3451977c29adb42ad1145e966e7dce097a
new file mode 100644 (file)
index 0000000..93669d6
--- /dev/null
+++ b/2d/789a3451977c29adb42ad1145e966e7dce097a
@@ -0,0 +1,114 @@
+Return-Path: <cworth@cworth.org>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 18CCF431FC3;\r
+       Sat, 21 Nov 2009 15:08:11 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id hZdYdiz5SYb6; Sat, 21 Nov 2009 15:08:10 -0800 (PST)\r
+Received: from cworth.org (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id A40AC431FBC;\r
+       Sat, 21 Nov 2009 15:08:09 -0800 (PST)\r
+From: Carl Worth <cworth@cworth.org>\r
+To: Jan Janak <jan@ryngle.com>\r
+In-Reply-To: <f35dbb950911211307t1cd8e039xca754828c75b26f6@mail.gmail.com>\r
+References: <1258630481-5133-1-git-send-email-jan@ryngle.com>\r
+       <1258630481-5133-2-git-send-email-jan@ryngle.com>\r
+       <f35dbb950911190352q2dcd041fr83a2f722f3231f44@mail.gmail.com>\r
+       <87lji2bmrb.fsf@yoom.home.cworth.org>\r
+       <f35dbb950911211307t1cd8e039xca754828c75b26f6@mail.gmail.com>\r
+Date: Sun, 22 Nov 2009 00:07:57 +0100\r
+Message-ID: <87my2f329e.fsf@yoom.home.cworth.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Cc: notmuch@notmuchmail.org\r
+Subject: Re: [notmuch] [PATCH 2/2] notmuch list: A new command to produce\r
+ various lists.\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.12\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 21 Nov 2009 23:08:11 -0000\r
+\r
+On Sat, 21 Nov 2009 22:07:14 +0100, Jan Janak <jan@ryngle.com> wrote:\r
+> My patch no longer works and I have been thinking about updating it to\r
+> current HEAD. But before I do that, I wanted to check with you to see\r
+> if you would prefer to use a different name for the command, here are\r
+> some options:\r
+> \r
+>   1) notmuch tags\r
+>   2) notmuch list tags\r
+>   3) notmuch list-tag\r
+> \r
+> Any opinions?\r
+> \r
+> I also plan to add support for search-terms later so that we can\r
+> produce tag lists for a set of messages, as you mentioned in one of\r
+> your previous emails.\r
+\r
+I don't think "list" would make sense unless it didn't support search\r
+terms at all.\r
+\r
+So I proposed my "search-messages" command earlier as well.\r
+\r
+It's clear that there are lots of different things that we're going to\r
+want to search for in the database and then lots of way's that we're\r
+going to want to present the resulting data.\r
+\r
+I would rather like there to be some correlation between commands with\r
+shorter names being more likely to be the kind of thing that a user\r
+would use directly from the command line. And longer names can be used\r
+for things that are more for interfaces to use, and for people to use in\r
+writing scripts.\r
+\r
+So how about "search-tags" and "search-messages" ?\r
+\r
+Any better ideas?\r
+\r
+Another option would be to just call this "notmuch search" and have an\r
+option to control what is output:\r
+\r
+       notmuch search  # for threads, as currently\r
+       notmuch search --output=tags\r
+       notmuch search --output=messages\r
+\r
+Actually, I kind of like that. For one thing, it makes it easy to\r
+eliminate the redundancy I made with the option-parsing in both\r
+notmuch-search.c and notmuch-search-message.c.\r
+\r
+> A quick description for those who joined later: This command produces\r
+> a list of all tags defined in the database. The emacs interface uses\r
+> it to implement tag name completion.\r
+\r
+And I can't wait to have tag completion in the interface. This will be\r
+nice.\r
+\r
+One thing we'll still have to think about is how to remove the "virtual\r
+tags" from the completion list, (once we have virtual tags in the\r
+configuration file---that is, tags applied automatically based on search\r
+specifications).\r
+\r
+The place we'd want to remove these from the completion list is when\r
+adding/removing a tag---it should be illegal to add/remove virtual tags\r
+since they will be maintained by the system according to the search\r
+specifications.\r
+\r
+Of course, when searching/filtering by tag, the completion list should\r
+include all tags, whether manual or virtual.\r
+\r
+So, what we're going to need for that is something like "notmuch config"\r
+that allows the interface to query the configuration.\r
+\r
+But that's all down the road. Let's get that tag completion working!\r
+\r
+-Carl\r