'execute-extended-command' requires entering into the insert mode to enter a command

xahlee / xah-fly-keys

the most efficient keybinding for emacs

http://xahlee.info/emacs/misc/xah-fly-keys.html

484 stars 83 forks source link

'execute-extended-command' requires entering into the insert mode to enter a command #112

Closed wvwwvwwv closed 3 years ago

wvwwvwwv commented 3 years ago

Thanks all for the great piece of code that eases the pain in my fingers.

One question. Whenever I try M-x in the command mode (querty: 'a'), I additionally have to press 'f' in order to start writing something into minibuffer. Is it by design? Or a flaw in the design?

xahlee commented 3 years ago

that doesn't happen to me. When i press 'a' or space return, it is switched to insert mode in minibuffer.

wvwwvwwv commented 3 years ago

Thanks for your comment. Let me briefly describe my reproducible scenario.

Env.

macOS 11.2 MacBook Air M1 2020 Emacs 27.1 CAPSLOCK <-> ctrl replaced. Default terminal with ‘option’ sending META turned on. .emacs (xah-fly-keys-set-layout "qwerty") (global-set-key (kbd "M-\\") 'xah-fly-command-mode-activate)

Scenario.

Run emacs
M-\<SPC>: command mode
‘a’: open minibuffer, showing “M-x”
Press ‘a’: error, [Command attempted to use minibuffer while in minibuffer]
Press ‘f’: now, typing characters is allowed

DivineDominion commented 3 years ago

@wvwwvwwv I recently picked up XFK and this doesn't happen on my machine, either. (macOS, too) -- when the command runs, it switches to insert mode in the minibuffer. (In fact, I found this quite confusing :))

wvwwvwwv commented 3 years ago

Thanks for your time to test it. I guess that my emacs settings are somehow inconsistent. I’ll close the issue.