From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: *Completions* in minibuffer-only frames
Date: Tue, 19 Feb 2019 18:46:17 +0100 [thread overview]
Message-ID: <5C6C40E9.1010505@gmx.at> (raw)
In-Reply-To: <83o977iw1u.fsf@gnu.org>
> How old is this problem?
It's with us at least since Emacs 25.
> It doesn't sound too serious to me, FWIW
> (but then I never use minibuffer-only frames).
As a rule I don't use minibuffer-only frames either so I only recently
bumped into a number of problems while looking at them a bit harder.
The behavior I describe is a direct consequence of our idiosyncrasy to
consider the minibuffer window of a minibuffer-only frame as the root
window of its frame's window tree while we do not consider the
minibuffer window of a "normal" frame as part of that frame's window
tree. This confuses ‘walk-window-tree’ which may not interpret its
MINIBUF argument as intended when "walking" a minibuffer-only frame.
> I'd really like to release Emacs 26.2 VSN; the bug reports about
> recent regressions or serious bugs all but ceased to arrive, so I
> think we have a stable branch. Installing non-trivial (by their
> effect) changes is something I'd like to avoid if possible.
Since nobody ever complained I have no problems with postponing the
fix to Emacs 27.
martin
next prev parent reply other threads:[~2019-02-19 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 9:31 *Completions* in minibuffer-only frames martin rudalics
2019-02-19 16:26 ` Eli Zaretskii
2019-02-19 17:46 ` martin rudalics [this message]
2019-02-19 18:15 ` Eli Zaretskii
2019-02-20 10:20 ` martin rudalics
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5C6C40E9.1010505@gmx.at \
--to=rudalics@gmx.at \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).