From: Mark Walters <markwalters1009@gmail.com>
To: Matt Armstrong <marmstrong@google.com>,
David Bremner <david@tethera.net>,
notmuch@notmuchmail.org
Subject: Re: feature request: highlighting of partial jump sequences
Date: Tue, 18 Oct 2016 10:38:49 +0100 [thread overview]
Message-ID: <87h98aatee.fsf@qmul.ac.uk> (raw)
In-Reply-To: <qf5y41mhnf0.fsf@marmstrong-linux.kir.corp.google.com>
On Mon, 17 Oct 2016, Matt Armstrong <marmstrong@google.com> wrote:
> David Bremner <david@tethera.net> writes:
>
>> I (very) recently started using longer key sequences with Mark's
>> tag-jump feature. One thing I miss from a similar feature in org-mode
>> (e.g. exporting) is some visual feedback on what I have typed so far,
>> and thus what my next key is likely to do.
>
> Tangentially, has an alternative UI been considered such as something
> based on ido? I mention this merely because building on something
> standard is probably going to be less work and more familiar to users.
The nice feature of jump is that it is very fast to type: I can get to
my common saved searches in two keystrokes. I think the multistep is
more specialised and probably more useful for tag-jump -- I imagine uses
along the lines of k (to enter tag jump) n to enter notmuch:: prefixed
tags, and then a letter for the appropriate notmuch:: tag.
> The other day I was thinking that if no "jumps" are configured, and the
> user has ido mode on, selecting among all saved searches with ido would
> be a natural thing for 'j' to do. Some users (probably me) may then
> never bother to set up shortcut keys.
I think this would make it very confusing when/if people did add a saved
jump. If we want to offer something like ido completion then I would
suggest putting it under a further character in the jump map. eg j j
would lead to ido completion, and then if people add normal jump short
cuts everything stays the same. (We would want to make sure that user
jump binding override this j binding so that we don't break anybodies
existing setup.)
Best wishes
Mark
next prev parent reply other threads:[~2016-10-18 9:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 15:09 feature request: highlighting of partial jump sequences David Bremner
2016-10-08 23:00 ` [PATCH] emacs: jump: make multilevel keys do multilevel jump Mark Walters
2016-10-09 2:37 ` David Bremner
2016-10-09 7:37 ` Mark Walters
2016-10-09 11:46 ` David Bremner
2016-10-15 11:50 ` Mark Walters
2016-10-16 1:01 ` David Bremner
2016-10-17 17:53 ` feature request: highlighting of partial jump sequences Matt Armstrong
2016-10-18 9:38 ` Mark Walters [this message]
2016-10-18 17:07 ` Matt Armstrong
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=87h98aatee.fsf@qmul.ac.uk \
--to=markwalters1009@gmail.com \
--cc=david@tethera.net \
--cc=marmstrong@google.com \
--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).