bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#48254: 28.0.50; minibuffer does not show the prompt of a command on


From: Gregory Heytings
Subject: bug#48254: 28.0.50; minibuffer does not show the prompt of a command on first invocation
Date: Fri, 07 May 2021 15:28:17 +0000


(add-hook 'change-major-mode-hook (lambda () (or (minibufferp) (set-input-method 
"english-dvorak"))))
(add-hook 'minibuffer-setup-hook (lambda () (set-input-method 
"english-dvorak")))
...
Does that solve the problem you have?

Thanks, this solves the issue.


Okay.


But I have some other issues related to input methods, which I don't know how to reproduce reliably. Maybe you can give me some hints and I will report them as separate bugs.

One issue is related to the prompts, where the input is a single key like "y" or "!", like the prompt shown when you have some modified buffers while exiting Emacs. Sometimes I have to press the key as it is laid on qwerty layout, but sometimes it is as on dvorak layout. This is quite annoying, since I always have to guess, which layout is active for the shown yes-no prompt.


I don't use a global input method myself, so I cannot give you a general advice alas. In my tests, with the two above lines, everything that is read in the minibuffer (yes-or-no-p, y-or-n-p, read-answer, ...) uses the Dvorak layout. Without a recipe, I cannot do more.


The other issue is probably somehow related to Edebug. I am learning elisp, so I often run Edebug just to learn how some functionality works. Once in a while, when some breakpoint is hit, something bad happens to Emacs in a way that each keymap that defines just basic characters (I mean without modifier bits), like Info buffer, or Edebug, or Gnus is turned to think that underlying layout is dvorak. So pressing "l" inside Info buffer runs actually 'Info-next' command, which is bound to "n", istead of going back in history. So to make keybindings operate normally again I have to press "C-\" in every buffer to reset input method. The other side effect of this is that read-only edebug buffer suddenly becomes editable and I can enter text there, though mode line still shows '%%'.


Again, in my tests this doesn't happen, so alas I cannot give you an advice without a recipe.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]