emacs-devel
[Top][All Lists]
Advanced

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

Re: New multi-command facility displays in the wrong echo area.


From: Eli Zaretskii
Subject: Re: New multi-command facility displays in the wrong echo area.
Date: Sat, 10 Oct 2020 15:50:07 +0300

> Date: Sat, 10 Oct 2020 12:44:46 +0000
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
> 
> When just the isearch is active, f10 does indeed work.  When,
> additionally, C-x b is active on another frame, it throws the error
> "Command attempted to use minibuffer while in minibuffer".  This is
> surely correct.  However, the isearch highlighting doesn't get removed in
> this error case.  That is incorrect.

Is this different from what happened in versions of Emacs before 27.1?

> > Another, perhaps more important, use case is when you type "M-s e"
> > during Isearch: that enters the minibuffer to let you edit the search
> > string.
> 
> This works fine.  Without the C-x b in another frame, it just works.
> With the C-x b in the other frame it throws the "Command ... minibuffer"
> error and removes the highlighting.
> 
> > Yet another similar use case is when you type "C-x 8 RET" during
> > Isearch: that reads the character's name/codepoint from the minibuffer.
> 
> This goes wrong.  With C-x b active on frame F1, move to F2, start an
> isearch, C-x 8 RET, use TAB completion to select a character and RET.
> This displays
> 
>     Switch to buffer (default xdisp.c):  [Failing I-search: su�] 
> 
> on F2.  On terminating the isearch and completing the C-x b action in
> F2's minibufer, the buffer switch has worked in frame F1.

Same question here.

If Gregory's change doesn't make things worse than they were before
Emacs 27.1, then I think we should install it.  In the emacs-27
branch, please.

Thanks.



reply via email to

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