unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jani Nikula <jani@nikula.org>
To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: hello: display jump key next to saved search when available
Date: Sun, 07 Feb 2016 12:58:41 +0200	[thread overview]
Message-ID: <87y4aw3hy6.fsf@nikula.org> (raw)
In-Reply-To: <cunwpqgop0m.fsf@disaster-area.hh.sledj.net>

On Sun, 07 Feb 2016, David Edmondson <dme@dme.org> wrote:
> On Sun, Dec 13 2015, Jani Nikula <jani@nikula.org> wrote:
>> Display the shortcut jump key next to the saved search name in notmuch
>> hello, if one is defined for the saved search.
>
> I quite like the idea of this (and Mark's followup), but I wonder about
> the utility. With notmuch-jump, as soon as I hit `j' a list of the
> possible keystrokes and the corresponding search is presented, so I
> don't need to refer to the list in the hello buffer to know what to do.

Much of the point in this was to discuss how to make the UI, and the
very capable features we have, more discoverable to new uses. Most
people won't start by reading the documentation (which we don't even
really have for notmuch-emacs). Keeping the UI uncluttered and clean at
the same time is hard.

Perhaps promoting the '?' key in my other patch is enough. Perhaps an
alternative would be to highlight the 'j' key in "Saved searches:
[edit]" somehow.

BR,
Jani.

  reply	other threads:[~2016-02-07 10:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-13 18:24 [PATCH] emacs: hello: display jump key next to saved search when available Jani Nikula
2015-12-13 19:09 ` Andrew Burgess
2015-12-20  9:26 ` [PATCH] emacs: jump: show key shortcut Mark Walters
2015-12-20 12:50   ` Jani Nikula
2016-02-07  9:20 ` [PATCH] emacs: hello: display jump key next to saved search when available David Edmondson
2016-02-07 10:58   ` Jani Nikula [this message]
2016-02-09 20:42     ` David Edmondson

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=87y4aw3hy6.fsf@nikula.org \
    --to=jani@nikula.org \
    --cc=dme@dme.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).