unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jani Nikula <jani@nikula.org>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
	notmuch@notmuchmail.org
Subject: Re: [PATCH 3/4] emacs: Add pseudo saved search to match mail that no saved search matches
Date: Wed, 29 Jun 2011 20:15:22 +0000	[thread overview]
Message-ID: <87y60kv1gl.fsf@nikula.org> (raw)
In-Reply-To: <87liwkxxfm.fsf@servo.factory.finestructure.net>

On Wed, 29 Jun 2011 12:14:05 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
Non-text part: multipart/signed
> On Tue, 28 Jun 2011 07:31:31 +0000, Jani Nikula <jani@nikula.org> wrote:
> > Add a pseudo saved search that matches all the mail that no other saved
> > search matches. Add new customization option notmuch-saved-searches-nomatch
> > to enable and name the pseudo saved search.
> 
> Hi, Jani.  I haven't looked too closely at these patches yet, although
> they seem to look ok at first glance.  However, I would like to argue
> *against* using new customization variables for the names of certain
> static saved searches.  For instance I don't see the point of the
> "notmuch-saved-searches-nomatch" and "notmuch-tags-nomatch"
> customization variables.  Do people *really* need to be able to
> customize those names?  Why not just pick a sensible name and go with
> it?

Hi, I didn't add the customization specifically to customize the name,
but rather to be able to switch the feature on/off. I felt that people
might want to customize that. And while at it, customizing the name in
the same variable seemed like a good idea. It's probably not desirable
to collide with whatever search/tag names people might use.

So to clarify, do you prefer having on/off switches, or just enabling
this without customization at all? Personally I'd shy away from the
latter, but I guess it depends on how useful vs. distracting people find
this.

> Customization is great, but if there's too much the code and
> customization UI become overly cluttered and hard to parse.

Agreed.


Jani

  reply	other threads:[~2011-06-29 20:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28  7:31 [PATCH 0/4] emacs: find non-matching mails, plus small tweaks Jani Nikula
2011-06-28  7:31 ` [PATCH 1/4] emacs: Add functions and bindings to archive and mark thread as read Jani Nikula
2011-06-28  7:31 ` [PATCH 2/4] emacs: Add option to make adding saved searches append, not prepend Jani Nikula
2011-06-28  7:31 ` [PATCH 3/4] emacs: Add pseudo saved search to match mail that no saved search matches Jani Nikula
2011-06-29 19:14   ` Jameson Graef Rollins
2011-06-29 20:15     ` Jani Nikula [this message]
2011-06-29 20:49       ` Jameson Graef Rollins
2011-06-29 21:47         ` Jani Nikula
2011-06-28  7:31 ` [PATCH 4/4] emacs: Add pseudo tag to match all messages that have no tags Jani Nikula
2011-06-30  7:56   ` Pieter Praet

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=87y60kv1gl.fsf@nikula.org \
    --to=jani@nikula.org \
    --cc=jrollins@finestructure.net \
    --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).