From: Austin Clements <amdragon@mit.edu>
To: Daniel Schoepe <daniel.schoepe@googlemail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: Make the queries used in the all-tags section
Date: Wed, 25 May 2011 18:42:30 -0400 [thread overview]
Message-ID: <BANLkTi=729DWai4q57iBSfz1wDhBXsmndQ@mail.gmail.com> (raw)
In-Reply-To: <87ei3mcw7h.fsf@gilead.invalid>
On Wed, May 25, 2011 at 5:21 PM, Daniel Schoepe
<daniel.schoepe@googlemail.com> wrote:
> On Wed, 25 May 2011 15:11:16 -0400, Austin Clements <amdragon@mit.edu> wrote:
>> So, perhaps something like
>>
>> (defcustom notmuch-hello-tag-list-counts nil
>> "Method for generating counts displayed in the all tags list.
>>
>> This variable controls the query used to generate counts for each
>> tag in the \"all tags\" list. If nil, the tag list will count
>> all messages with each tag. This can be a query string that will
>> filter the messages counted for each tag. Finally, this can be a
>> function that will be called for each tag and should return a
>> filter query for that tag, or nil to hide the tag."
>> :type '(choice (const :tag "Count all messages" nil)
>> (const :tag "Count unread messages" "tag:unread")
>> (const :tag "Custom filter" string)
>> (const :tag "Custom filter function" function))
>> :group 'notmuch)
>
> That is slightly less accurate though, since the query is not only used
> to generate the counts, but also the searches that are performed when
> one presses return on a tag in the list.
'Doh. That's what I get for not reading the surrounding code. I
misunderstood what your patch was going for and assumed it was what
*I* wanted notmuch to do, which is to show me useful counts (e.g.,
unread count), but not to change the underlying query. ]:--8)
So, to me, it seems like this turns the all tags section into another
saved searches section, just with a slight twist, and makes me wonder
if there's a better way to reconcile these.
> Ah, thanks. I guess too much exposure to Haskell (and how smart GHC is)
> makes me write things in a functional style without thinking about
> performance.
Hah, been there. I have to constantly remind myself that Elisp is
*not* a self-respecting functional programming language, despite how
much it may look like Scheme.
next prev parent reply other threads:[~2011-05-25 22:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 23:18 [PATCH] emacs: Make the queries used in the all-tags section Daniel Schoepe
2011-05-24 20:39 ` Carl Worth
2011-05-24 21:01 ` Daniel Schoepe
2011-05-24 22:04 ` Carl Worth
2011-05-25 4:10 ` Austin Clements
2011-05-25 10:04 ` Daniel Schoepe
2011-05-25 14:44 ` Austin Clements
2011-05-25 16:51 ` Daniel Schoepe
2011-05-25 17:56 ` Daniel Schoepe
2011-05-25 19:11 ` Austin Clements
2011-05-25 21:21 ` Daniel Schoepe
2011-05-25 22:42 ` Austin Clements [this message]
2011-05-25 23:21 ` Daniel Schoepe
2011-05-26 1:05 ` Carl Worth
2011-05-26 22:04 ` Carl Worth
2011-05-27 3:56 ` Daniel Kahn Gillmor
-- strict thread matches above, loose matches on Subject: below --
2011-05-26 3:27 Austin Clements
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='BANLkTi=729DWai4q57iBSfz1wDhBXsmndQ@mail.gmail.com' \
--to=amdragon@mit.edu \
--cc=daniel.schoepe@googlemail.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).