From: Carl Worth <cworth@cworth.org>
To: Kan-Ru Chen <kanru@kanru.info>, notmuch@notmuchmail.org
Subject: Re: [PATCH 2/3] notmuch.el: Add collapse all and expand all to notmuch-show
Date: Fri, 05 Feb 2010 11:45:02 -0800 [thread overview]
Message-ID: <87aavnpiv5.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <1259648253-31034-2-git-send-email-kanru@kanru.info>
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
On Tue, 1 Dec 2009 14:17:32 +0800, Kan-Ru Chen <kanru@kanru.info> wrote:
> These two functions behave like gmail's collapse all and expand all
> commands. notmuch-show-collapse-all is bound to 'B' but
> notmuch-show-expand-all has no keybindig because I thought it is not often
> used.
I haven't applied this one for a few reasons:
1. I don't know what the functions are support to do.
The commit log says "behave like gmail" but I don't know what that
means personally. And the functions don't have any documentation
strings.
I assume that these functions are either showing or hiding all
message bodies in the current thread?
2. You provided a binding for collapse, but not expand. I don't like
functionality which lets a user hide a bunch of data, and then not be
able to get it back---that's really annoying if the user hits the key
accidentally.
Personally, I think I'd be much more likely to use expand before
collapse, (for example, to easily see the context when a new message
arrives in a thread that I'd previously read so comes up collapsed by
default).
Should we perhaps make something which temporarily makes all hidden
messages visible but then toggles back to the previous subset of some
show messages? Once again, I'm worried about providing trapdoor
interfaces where the user can't get back to the previous state easily.
-Carl
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2010-02-05 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 6:13 [PATCH 1/3] notmuch.el: Add keybinding to toggle display of message body and headers Kan-Ru Chen
[not found] ` <1259648033-30653-2-git-send-email-kanru@kanru.info>
2009-12-01 6:13 ` [PATCH 3/3] notmuch.el: Use emacs built-in forward-button and backward-button Kan-Ru Chen
2010-02-05 19:45 ` Carl Worth
2009-12-01 6:17 ` [PATCH 2/3] notmuch.el: Add collapse all and expand all to notmuch-show Kan-Ru Chen
2010-02-05 19:45 ` Carl Worth [this message]
2010-02-05 19:32 ` [PATCH 1/3] notmuch.el: Add keybinding to toggle display of message body and headers Carl Worth
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=87aavnpiv5.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=kanru@kanru.info \
--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).