GNU bug report logs -
#45072
28.0.50; Emacs switches other buffer back uncontrollably, if other window's buffer is changed by user during minibuffer editing
Previous Next
Reported by: Jean Louis <bugs <at> gnu.support>
Date: Sun, 6 Dec 2020 14:09:01 UTC
Severity: minor
Tags: fixed
Fixed in version 28.0.50
Done: Juri Linkov <juri <at> linkov.net>
Bug is archived. No further changes may be made.
Full log
Message #152 received at 45072 <at> debbugs.gnu.org (full text, mbox):
>>> It seems that problem is that read_minibuf messes up the windows so much,
>>> that at the end currently the only way to fix this mess is by restoring
>>> the previous window configuration. This means that there is a need
>>> to fix read_minibuf to restore all previous window states without using
>>> restore_window_configuration. Only then it will be possible to add
>>> a user option to disable using restore_window_configuration.
>>
>> But without such an option, it's hard to find and fix the problems,
>> because they're hidden by the `restore_window_configuration`.
>> So maybe we should introduce such an option, and then force ourselves to
>> live with it and then fix the problems we encounter.
>
> Exiting from and quitting `read-minibuffer' is hairy, in particular with
> multiple frames. IIRC it's hard to tell for an application how to clean
> up the state when the user quits and throws it back to the top level.
Since restore_window_configuration doesn't restore multiple frames,
we already don't clean up the previous state completely. So maybe
really it should be sufficient for a new option just to select
the original window if it still exists.
This bug report was last modified 3 years and 291 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.