all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Alfred M. Szmidt" <ams@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: eliz@gnu.org, stefan@marxist.se, justin@burkett.cc, emacs-devel@gnu.org
Subject: RE: keysee.el (was: Re: Include which-key.el in the Emacs distribution)
Date: Tue, 8 Sep 2020 11:58:03 -0700 (PDT)	[thread overview]
Message-ID: <122d2a88-2478-408c-8ed8-a037cbf51be8@default> (raw)
In-Reply-To: <<E1kFiR6-0002dS-Ou@fencepost.gnu.org>>

> Using keysee, while it does provide a slightly better interface it is
> still confusing me.  I loaded sortie.el and keysee.el, and turned on
> kc-auto-mode.

<Snipped description of trying to type keys after prefix keys...>

Please read the description.  Key See is not Which-Key.

Key See shows you the available keys, and their
commands, at any point (any time).

It shows you _descriptions_ of the keys and commands.
You can complete (normally) against those descriptions.

So if you type `C-x' you're shown descriptions (names)
of all keys & commands in that prefix-key's keymap
(`ctl-x-map').  You can narrow the help by completing
against key names or command names (or both).

That means typing text to complete against the names,
not hitting keys to continue the `C-x' key sequence.

It's a different UI (it's the standard Emacs UI, with
`completing-read').  Different pros & cons.  I think
what it does is clear from the doc.  But if you don't
read the doc and just expect which-key behavior... ;-)

Hope it's clear now.  It's different from which-key.

I pointed also to its big brother, Icicles key
completion, which offers more.  The idea is the same.
The description in the Icicles doc is more elaborate,
with screenshots etc.

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



       reply	other threads:[~2020-09-08 18:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<<CADwFkmmvVRqnQGA_d8bMA66SXbpjis+j-1UiceY7Lk7eY6iugA@mail.gmail.com>
     [not found] ` <<<E1kFgO6-0000cE-Dj@fencepost.gnu.org>
     [not found]   ` <<<83sgbskwq8.fsf@gnu.org>
     [not found]     ` <<3b2bc5ac-0469-4c95-86e8-74806a06d3eb@default>
     [not found]       ` <<E1kFiR6-0002dS-Ou@fencepost.gnu.org>
2020-09-08 18:58         ` Drew Adams [this message]
2020-09-08 19:35           ` keysee.el (was: Re: Include which-key.el in the Emacs distribution) Alfred M. Szmidt
     [not found] <<CADwFkmmvVRqnQGA_d8bMA66SXbpjis+j-1UiceY7Lk7eY6iugA@mail.gmail.com>
     [not found] ` <<E1kFgO6-0000cE-Dj@fencepost.gnu.org>
     [not found]   ` <<83sgbskwq8.fsf@gnu.org>
2020-09-08 18:05     ` Include which-key.el in the Emacs distribution Drew Adams
2020-09-08 18:33       ` keysee.el (was: Re: Include which-key.el in the Emacs distribution) Alfred M. Szmidt

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

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

  git send-email \
    --in-reply-to=122d2a88-2478-408c-8ed8-a037cbf51be8@default \
    --to=drew.adams@oracle.com \
    --cc=ams@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=justin@burkett.cc \
    --cc=stefan@marxist.se \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.