From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: feature request: highlighting of partial jump sequences
Date: Sat, 08 Oct 2016 12:09:25 -0300 [thread overview]
Message-ID: <8737k6andm.fsf@zancas.localnet> (raw)
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.
d
next reply other threads:[~2016-10-08 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 15:09 David Bremner [this message]
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
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=8737k6andm.fsf@zancas.localnet \
--to=david@tethera.net \
--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).