RE: keysee.el

[Drew Adams]

>> Please read the description.
> 
> 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.

How did you know there was such a mode and what
it does and how?  Either you read about it
somewhere or someone told you about it.  Or
perhaps you dreamt it.

You have preconceptions.  They didn't come from
reading the doc, right?

It's possible there's something confusing,
incorrect, or misleading in the doc.  Please
point that out, if so, and I'll try to fix it.

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

Why would you think completion candidates in
*Completions* are not something to be matched
by typing text in the minibuffer?

That's the usual Emacs behavior.  I'd think that
would be the default expectation for an Emacs
user.

You have different expectations, presumably from
your experience with which-key.  This isn't that.

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

If you do `M-x fi TAB' and go for coffee, same
thing.  Same thing for `C-x C-f fo TAB'.

This is no different, except here you initiate
completion with S-TAB, not TAB (by default).

Or it's initiated automatically after a delay
(no key), if you use `kc-auto-mode' instead of
`kc-mode'.

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

As the doc tells you (it's quite short!), you
can use `kc-mode' to get completion on demand.
Or you can use `kc-auto-mode' to get automatic
completion.

You can use automatic completion while recording
a keyboard macro, if you like.  You just need to
type minibuffer text to match `key  =  command'
completions.

But complete automatically when recording a
keyboard macro?  If you had auto-completion
for `find-file', that too might be confusing
while trying to record a macro.

For key completion while recording, you might
be better off with `kc-mode'.  Or with no key
completion at all.

> I get why it becomes that -- but consider it
> from a random user.

I guess I kinda expect a user, random or not,
to look at a doc string or the doc - or the
code.  YMMV.