From: Daniel Schoepe <daniel.schoepe@googlemail.com>
To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: Make the queries used in the all-tags section
Date: Tue, 24 May 2011 23:01:16 +0200 [thread overview]
Message-ID: <87oc2rrexv.fsf@gilead.invalid> (raw)
In-Reply-To: <87ei3nltnz.fsf@yoom.home.cworth.org>
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
On Tue, 24 May 2011 13:39:44 -0700, Carl Worth <cworth@cworth.org> wrote:
> This seems like a useful feature, but perhaps it's a little too general?
>
> I'm imagining a user wanting to use this functionality but not knowing
> anything about writing an emacs-lisp function. For such a user, this
> variable won't provide much of a feature.
>
> I think that might be an argument for dropping this variable from the
> notmuch customization group. That customization page is starting to get
> crowded, and if there are things there that can't be easily manipulated
> with the available controls, I think they're mostly just clutter.
>
> Perhaps this could be addressed by allowing this variable to be an alist
> instead of (or in addition to) a function. What do you think?
Yes, allowing both, an alist or a function for this variable seems
better than forcing the user to write a function, but how should the
alist control the behaviour? I don't think people would like having to
specify a query for each of their tags, and since, by assumption, they
cannot write a function to automate this, they probably wouldn't be much
better off. (Except of course, if they only wanted to change it for a
few individual tags).
Another option would be to also allow various symbols like 'unread (meaning
"tag:TAG and tag:unread") for "popular" queries in addition to a function.
Cheers,
Daniel
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-05-24 21:01 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 [this message]
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
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=87oc2rrexv.fsf@gilead.invalid \
--to=daniel.schoepe@googlemail.com \
--cc=cworth@cworth.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).