unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Subject: Re: [RFC PATCH v2 0/3] lib/cli/emacs: limit number of messages in search results
Date: Tue, 01 Nov 2011 09:30:56 -0300	[thread overview]
Message-ID: <87zkgg6n3z.fsf@zancas.localnet> (raw)
In-Reply-To: <cover.1320093940.git.jani@nikula.org>

On Mon, 31 Oct 2011 23:18:07 +0200, Jani Nikula <jani@nikula.org> wrote:
> 
> I'm still marking it as RFC. It works for me, but patch 1 might be deemed
> unacceptable.
> 

Hi Jani;

Is just because it add a function to the library that you think this
might be problematic?  I don't think we are super-dogmatic about the
library never growing.  When notmuch started, there were no bindings, so
in retrospect maybe more functionality went into the CLI than might
happen if we started from scratch. If I remember Carl's statement
correctly, one rule is that stuff in the library should not require
configuration.

Just my personal view,

David

  parent reply	other threads:[~2011-11-01 12:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 21:18 [RFC PATCH v2 0/3] lib/cli/emacs: limit number of messages in search results Jani Nikula
2011-10-31 21:18 ` [RFC PATCH v2 1/3] lib: add function to get the number of threads matching a search Jani Nikula
2011-10-31 21:18 ` [RFC PATCH v2 2/3] cli: add options --first and --maxitems to notmuch search Jani Nikula
2011-10-31 21:18 ` [RFC PATCH v2 3/3] emacs: support limiting the number of results shown in search results Jani Nikula
2011-11-04 20:54   ` Austin Clements
2011-11-06 20:57     ` Jani Nikula
2011-10-31 21:44 ` [RFC PATCH v2 0/3] lib/cli/emacs: limit number of messages " Jameson Graef Rollins
2011-10-31 22:07   ` Jani Nikula
2011-10-31 22:19     ` Jameson Graef Rollins
2011-11-04 20:21     ` Austin Clements
2011-11-01 12:30 ` David Bremner [this message]
2011-11-02  9:27   ` Jani Nikula

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=87zkgg6n3z.fsf@zancas.localnet \
    --to=david@tethera.net \
    --cc=jani@nikula.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).