keysee.el (was: Re: Include which-key.el in the Emacs distribution)

keysee.el (was: Re: Include which-key.el in the Emacs distribution)

[Alfred M. Szmidt]

   > to scroll to the next page?  In particular, after typing
   > "C-h" that shows the first page of Help commands?

   FWIW, this is not a problem for keysee.el.  Scrolling
   *Completions* is as usual (TAB), including after C-h.

So I like these hints, which is why I'm keen on trying them.

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.

  C-h
  ;; Very large pop up pops up taking over my whole terminal window.
  ;; I press the period key, since that seems interesting since it says
  ;; display-local-help.
  .

Nothing happens; OK ... lets try again something different.

  C-h
  ;;; Large pop-up.  Lets try an easy one, C-a for about-emacs.
  C-a

Nothing happens.  Ok, so I must be doing something wrong.  Lets try C-x.

  C-x
  ;;; Large popup.
  C-f
  ;;; Echo area says End of Buffer, and beeps at me.

Hm.  Why can't I open a file when completing?  This occurs for any key
binding I tried while the keysee popup is active.

RE: keysee.el (was: Re: Include which-key.el in the Emacs distribution)

[Drew Adams]

> 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

Re: keysee.el (was: Re: Include which-key.el in the Emacs distribution)

[Alfred M. Szmidt]

   > 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.

That is sorta the point -- one shouldn't need to read a description to
open a file for a mode that tries to add completion.  The pop up shows
keys that one would think are possible to just input so it is easy to
expect that those will just work.

If I press C-x and go for a coffee in the middle of opening a file, it
also becomes confusing since the behaviour of Emacs will magically
change.  

This is specially important when inputting keyboard macros. if you
start a keyboard macro, wait for a bit ... then you're now recording
the input to keysee.  Very confusing, since if you're quick on the
fingers you'll get the expected behaviour but if you pause you get
something totally different.

I tried recording a simple macro, mark the whole buffer, and
upcase-region on it.  

  C-x h			;; mark-whole-buffer
  C-x C-u		;; upcase-region

with kc-auto-mode, it is just very very confundled:

  C-x (
  C-x h
  C-x <wait until popup) C-u
  ;; Nothing happens, so you start typing upcase-region you get
  uuuupcase-region
  ;; you amend that using backspace, and retype
  16*DEL upcase-region RET
  C-x )
  ;; Echo line now complains that parenthesis cannot be found and
  ;; inserts a closing paren in the buffer.
  C-x )

The recorded macro is something like:

  C-x h			;; mark-whole-buffer
  C-x C-u		;; upcase-region
  upcase-region		;; self-insert-command * 13
  16*DEL		;; delete-backward-char
  upcase-region		;; self-insert-command * 13
  RET			;; newline
  C-x )			;; kmacro-end-macro

That isn't exactly what was entered -- yes, I get why it becomes that
-- but consider it from a random user.