unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
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: Thu, 07 Jul 2011 20:25:37 +0200	[thread overview]
Message-ID: <87wrfuc5i6.fsf@gilead.invalid> (raw)
In-Reply-To: <871uy25d3y.fsf@steelpick.2x.cz>

[-- Attachment #1: Type: text/plain, Size: 3166 bytes --]

On Thu, 07 Jul 2011 17:23:13 +0200, Michal Sojka <sojkam1@fel.cvut.cz> 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 three tags". Moreover, it wouldn't help me to see
> non-zero number of unread messages and when I click the button I would
> see all the messages, not only the unread ones. It simply seems very
> confusing to me.

I agree with you, personally, but I don't think this particular bit
(:hide-empty-searches) increases code complexity that much (and all of
it is localized to the functions generating the sections, which possibly
should be moved to a separate file). I also find it plausible that a
user might want behavior like this (as, e.g. an overview, if he doesn't
want an all tags section, but still see what tags he has set).

Hence I don't see why we should not provide this option.

> > If we decide to keep this functionality, it should be inverted though,
> > i.e. one has to explicitly specify :show-empty-searches to get them.
> 
> > 
> > About the counts: I introduced this because Austin Clements says he
> > finds it useful in his comment here:
> > 
> > id:"BANLkTi=729DWai4q57iBSfz1wDhBXsmndQ@mail.gmail.com"
> 
> I agree that it is useful to see unread counts, but it is not useful to
> see all messages when I click the button.

As I said, this is not my preference either, but personal taste is not
necessarily the best argument for _not including_ something, especially
for the UI of a mail client. And in this case there even is someone
saying that behavior would be useful to him.

> > A user might still want to have the section collapsed when starting the
> > notmuch UI and only have it shown when he needs it. (I use that for a
> > section that displays unread counts for each tag).
> 
> You are right. I use emacs --daemon so I actually initialize notmuch UI
> only when emacs crashes or when I run out of battery power ;-)

Yes, me too, but I like seeing only sections that I care about every
time I open notmuch while still having more information available in a
convenient way. But I'm not too attached to this feature, so if the
consensus is that that bit should be removed, I'll bow to public opinion. :)

> If I understand this variable correctly, it stores the label (text) of
> the button you have your point at. This allows you to stay at the same
> button after reloading of notmuch-hello even if the layout changes,
> right? Then having the same named button in multiple sections results in
> moving the first (or last) occurrence of this button when notmuch-hello
> is reloaded.

Ah, I misunderstood what you were referring to earlier. That was already
case before my patch though, except that now it's more likely to have
buttons with the same name. Anyway, I think this is just a minor issue
and can be addressed in a different patch.

In any event, this definitely needs better documentation.

Thanks for all your input on this!

Cheers,
Daniel

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2011-07-07 18:25 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 [this message]
2011-07-08 21:23             ` Michal Sojka
2011-07-08 22:03               ` Daniel Schoepe
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=87wrfuc5i6.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).