GNU bug report logs - #56305
29.0.50; 'yes-or-no-p' deselects minibuffer frame

Previous Next

Full log

Message #245 received at 56305 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: rudalics <at> gmx.at, 56305 <at> debbugs.gnu.org, acm <at> muc.de
Subject: Re: bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame
Date: Wed, 20 Jul 2022 19:02:16 +0300

> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: rudalics <at> gmx.at,  acm <at> muc.de,  56305 <at> debbugs.gnu.org
> Date: Wed, 20 Jul 2022 10:54:46 -0400
> 
> >> But `save-selected-window` can't&shouldn't bind `inhibit-redisplay`.
> > I don't think I understand.  First, how is save-selected-window
> > related to this discussion?
> 
> `save-selected-window` uses `select-window`.

That select-window will do nothing unless BODY changes the selected
window, right?  So it isn't save-selected-window's business to do
anything about the issue at hand: it's the business of that BODY.

> [ Actually I meant to write `with-selected-window` which is even more
>   directly related, but the same hold for `save-selected-window`.  ]

What is the problem with with-selected-window, exactly?

> > And second, why cannot/shouldn't it bind inhibit-redisplay?
> 
> Because code within a `save-selected-window` may want to use `sit-for`,
> `read-event`, `recursive-edit`, `read-from-minibuffer`, ..

You assume the binding should be in effect while BODY runs.  But
that's not needed: you only need to do that around the call to
select-window (if at all).

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.