unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Tim Johnson <tim@akwebsoft.com>, Emacs <Help-gnu-emacs@gnu.org>
Subject: RE: Key sequence completion with evil
Date: Tue, 28 Aug 2018 15:46:58 -0700 (PDT)	[thread overview]
Message-ID: <e5ca25be-426e-4595-bf88-256a10e46f7b@default> (raw)
In-Reply-To: <20180828221740.GA21599@mail.akwebsoft.com>

> Using evil and evil-leader with emacs 26.1 Gui on Ubuntu 16.04
> 
> I'd welcome recommendations and/or comments regarding a package to
> enable key sequence completion in evil normal and insert states as
> well as evil emacs state.
> 
> I know that there are many completion packages and that those
> packages offer other features, but the primary feature I am
> interested in is where interactive candidates are offered (as
> opposed to non interactive textual candidates such as C-h would
> provide.)
> 
> Icicles? Ido? Ivy? ....

No idea how well it interacts with Evil, but Icicles has key-sequence completion.

You can see all keys available at the current time (including after one or more prefix keys). You can filter (narrow) the set of candidates any number of times, by matching against key names or command names. You can sort the candidates in a few ways. You can traverse the key-sequence hierarchy (e.g., go back up prefix keys). You can traverse menu-bar menus too.

As with any Icicles completion, you can initiate this on demand or automatically (e.g. after a delay).

https://www.emacswiki.org/emacs/Icicles_-_Key_Completion



  reply	other threads:[~2018-08-28 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 22:17 Key sequence completion with evil Tim Johnson
2018-08-28 22:46 ` Drew Adams [this message]
2018-08-28 23:22   ` Tim Johnson
2018-08-29  3:05   ` Tim Johnson
2018-08-30  0:38     ` Tim Johnson

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e5ca25be-426e-4595-bf88-256a10e46f7b@default \
    --to=drew.adams@oracle.com \
    --cc=Help-gnu-emacs@gnu.org \
    --cc=tim@akwebsoft.com \
    /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.
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).