4

Sometime recently emacs started making me hit C-g twice to quit a minibuffer prompt and I can't figure out how or why it's doing this.

What happens is I start a minibuffer command -- say, C-x C-f -- and then hit C-g to quit. Emacs then appends "[Quit] to the end of the minibuffer prompt, and doing C-g quits as expected.

It's the [Quit] that strikes me. I think that's related to some package I tried, but I don't see anything in my configuration.

I'm using emacs 27.1 on Windows.

There are several seemingly-related questions to this --

...but they seem to be about Linux, or GTK, or something else.

What package or configuration might cause this behavior?

Drew
  • 75,699
  • 9
  • 109
  • 225
Dan Drake
  • 503
  • 2
  • 15
  • 1
    Does it happen with `emacs -q`? If not, you can bisect your init file to find out who the culprit is. FWIW, I don't see that in the simple case, although it might happen with recursive edits in the minibuffer: you might have to `C-g` out of each level of the recursive edit. – NickD Mar 08 '21 at 14:55
  • What @NickD said - try `emacs -Q`. Bisect your init file. – Drew Mar 08 '21 at 16:13
  • Are you using any of the completion engines (ivy, ido, helm)? I am seeing the same thing and my feeling is that it's related to ivy/counsel but I am not sure. – éric Mar 10 '21 at 12:17
  • Please provide a step-by-step recipe to repro the problem, starting with `emacs -Q`. – Drew Apr 14 '21 at 20:16

1 Answers1

1

This was a dependency package -- org-random-todo depends on alert. Uninstalling and reinstalling org-random-todo seems to have cleared up the problem. So something in the installation seems to have gotten mixed up.

Dan Drake
  • 503
  • 2
  • 15