From: Daniel Schoepe <daniel.schoepe@googlemail.com>
To: Michal Sojka <sojkam1@fel.cvut.cz>, notmuch@notmuchmail.org
Subject: Re: [PATCH v3 1/2] emacs: User-defined sections in notmuch-hello
Date: Sat, 09 Jul 2011 00:03:28 +0200 [thread overview]
Message-ID: <87r5602zwu.fsf@gilead.invalid> (raw)
In-Reply-To: <87k4bs4gbn.fsf@steelpick.2x.cz>
[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]
On Fri, 08 Jul 2011 23:23:40 +0200, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
> OK. I changed my mind. I thought that the approach with 'notmuch
> search-tags QEURY' followed by 'notmuch count tag:XXX and QUERY' for
> returned tags would be faster then 'notmuch search-tags' followed by
> 'notmuch count tag:XXX and QUERY' for all tags, but it turned out not to
> be the case.
For me, the stronger argument was that the code would have been simpler,
because notmuch-hello refreshes don't happen that often that performance
shouldn't matter much.
>
> I played with the customization interface a bit and found the following
> problems:
>
> - It is annoying to insert section titles that includes ": " at the end
> in order to be nicely "rendered". I think this could be appended
> automatically.
Agreed.
>
> - :hide-empty-tags should be renamed in :hide-empty-searches to be
> effective (see the patch below).
This has been done in v4 of the patch, for which I screwed up the
In-Reply-To header and hence is listed as a separate thread:
id:"1310079227-19120-1-git-send-email-daniel.schoepe@googlemail.com"
>
> - The title of custom tags section was not passed correctly to the
> functions. This is also fixed in the patch below.
I changed title to a mandatory argument for consistency with
notmuch-insert-searches and because a title-less section wouldn't make
much sense anyway.
Cheers,
Daniel
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-07-08 22:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 20:26 [PATCH 0/2] emacs: User-defined sections in notmuch-hello Daniel Schoepe
2011-06-29 20:27 ` [PATCH 1/2] " Daniel Schoepe
2011-06-29 20:27 ` [PATCH 2/2] emacs: Tests for user-defined sections Daniel Schoepe
2011-07-02 13:31 ` [PATCH v2 0/2] emacs: User-defined sections in notmuch-hello Daniel Schoepe
2011-07-02 13:31 ` [PATCH 1/2] " Daniel Schoepe
2011-07-02 13:31 ` [PATCH 2/2] emacs: Tests for user-defined sections Daniel Schoepe
2011-07-05 0:00 ` [PATCH 0/2] emacs: User-defined sections in notmuch-hello Michal Sojka
2011-07-05 8:24 ` Daniel Schoepe
2011-07-05 14:09 ` Michal Sojka
2011-07-05 14:55 ` Daniel Schoepe
2011-07-05 16:43 ` Daniel Schoepe
2011-07-05 16:23 ` [PATCH v3 " Daniel Schoepe
2011-07-05 16:23 ` [PATCH v3 1/2] " Daniel Schoepe
2011-07-06 11:34 ` Michal Sojka
2011-07-06 12:41 ` Daniel Schoepe
2011-07-07 15:23 ` Michal Sojka
2011-07-07 18:25 ` Daniel Schoepe
2011-07-08 21:23 ` Michal Sojka
2011-07-08 22:03 ` Daniel Schoepe [this message]
2011-07-05 16:23 ` [PATCH v3 2/2] emacs: Tests for user-defined sections Daniel Schoepe
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=87r5602zwu.fsf@gilead.invalid \
--to=daniel.schoepe@googlemail.com \
--cc=notmuch@notmuchmail.org \
--cc=sojkam1@fel.cvut.cz \
/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).