On Fri, 08 Jul 2011 23:23:40 +0200, Michal Sojka 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 QUER
On Thu, 07 Jul 2011, Daniel Schoepe wrote:
Non-text part: multipart/signed
> On Thu, 07 Jul 2011 17:23:13 +0200, Michal Sojka
> wrote:
> > This wouldn't work for me. My all-tags section covers almost entire
> > screen and finding non-zero entries there is not very convenient. I find
> > much more
On Fri, 08 Jul 2011 23:23:40 +0200, Michal Sojka 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 QUER
On Thu, 07 Jul 2011, Daniel Schoepe wrote:
Non-text part: multipart/signed
> On Thu, 07 Jul 2011 17:23:13 +0200, Michal Sojka wrote:
> > This wouldn't work for me. My all-tags section covers almost entire
> > screen and finding non-zero entries there is not very convenient. I find
> > much more us
On Thu, 07 Jul 2011 17:23:13 +0200, Michal Sojka wrote:
> This wouldn't work for me. My all-tags section covers almost entire
> screen and finding non-zero entries there is not very convenient. I find
> much more useful to have a section saying: "Hey, you have unread
> messages only for these thre
On Wed, 06 Jul 2011, Daniel Schoepe wrote:
Non-text part: multipart/signed
> On Wed, 06 Jul 2011 13:34:13 +0200, Michal Sojka
> wrote:
> > So my proposal is to forget about different queries for filters and
> > counts and having here only the following options: filter, hide-tags and
> > hide-if-e
On Thu, 07 Jul 2011 17:23:13 +0200, Michal Sojka wrote:
> This wouldn't work for me. My all-tags section covers almost entire
> screen and finding non-zero entries there is not very convenient. I find
> much more useful to have a section saying: "Hey, you have unread
> messages only for these thre
On Wed, 06 Jul 2011, Daniel Schoepe wrote:
Non-text part: multipart/signed
> On Wed, 06 Jul 2011 13:34:13 +0200, Michal Sojka wrote:
> > So my proposal is to forget about different queries for filters and
> > counts and having here only the following options: filter, hide-tags and
> > hide-if-empt
On Wed, 06 Jul 2011 13:34:13 +0200, Michal Sojka wrote:
> > -(defcustom notmuch-hello-tag-list-make-query nil
> > - "Function or string to generate queries for the all tags list.
>
> I'm not sure it is a good thing to remove customizations that are
> included in a released version. Some users ma
Hi,
this is definitely better than the first version I was using! Thanks.
See other comments below.
On Tue, 05 Jul 2011, Daniel Schoepe wrote:
> This patch makes the notmuch-hello screen fully customizable
> by allowing the user to add and remove arbitrary sections. It
> also provides some conven
On Wed, 06 Jul 2011 13:34:13 +0200, Michal Sojka wrote:
> > -(defcustom notmuch-hello-tag-list-make-query nil
> > - "Function or string to generate queries for the all tags list.
>
> I'm not sure it is a good thing to remove customizations that are
> included in a released version. Some users ma
Hi,
this is definitely better than the first version I was using! Thanks.
See other comments below.
On Tue, 05 Jul 2011, Daniel Schoepe wrote:
> This patch makes the notmuch-hello screen fully customizable
> by allowing the user to add and remove arbitrary sections. It
> also provides some conven
This patch makes the notmuch-hello screen fully customizable
by allowing the user to add and remove arbitrary sections. It
also provides some convenience functions for constructing sections,
e.g. showing the unread message count for each tag.
This is done by specifying a list of functions that wil
This patch makes the notmuch-hello screen fully customizable
by allowing the user to add and remove arbitrary sections. It
also provides some convenience functions for constructing sections,
e.g. showing the unread message count for each tag.
This is done by specifying a list of functions that wil
14 matches
Mail list logo
