From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>, 28978@debbugs.gnu.org
Subject: bug#28978: 26.0; Regression: separate, dedicated `*Completions*' frame no longer has parameter `minibuffer'
Date: Wed, 25 Oct 2017 09:45:51 +0200 [thread overview]
Message-ID: <59F0412F.9090206@gmx.at> (raw)
In-Reply-To: <4d0c5535-246a-4356-914f-3c8d030ba9c9@default>
> It should be the case in my context that this returns the minibuffer
> window:
>
> (cdr (assoc 'minibuffer (frame-parameters
> (#<frame *Completions* 000000000cacf6c8>))))
>
> Instead, it now returns nil. Parameter `minibuffer' for the
> `*Completions*' frame is no longer the minibuffer window; it is nil.
Since the 'minibuffer' parameter of a frame cannot be changed (from nil
to some non-nil value and vice-versa at least) after its creation, your
code somehow now seems to fail to set up that parameter. Please show
the corresponding part where your code tries to set the parameter. If
necessary, debug it to show that after the corresponding ‘make-frame’
call the frame does not have that parameter set as requested.
Thanks, martin
next prev parent reply other threads:[~2017-10-25 7:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 20:20 bug#28978: 26.0; Regression: separate, dedicated `*Completions*' frame no longer has parameter `minibuffer' Drew Adams
2017-10-25 7:45 ` martin rudalics [this message]
2017-10-25 14:47 ` Drew Adams
2017-10-26 7:57 ` martin rudalics
2017-10-26 14:01 ` Drew Adams
2017-10-27 8:25 ` martin rudalics
2017-10-27 14:19 ` Drew Adams
2017-10-28 8:45 ` martin rudalics
2017-10-28 19:15 ` Drew Adams
2017-10-29 11:18 ` martin rudalics
2017-10-29 15:59 ` Drew Adams
2017-10-29 18:13 ` martin rudalics
2017-10-29 23:56 ` Drew Adams
2017-10-30 8:24 ` martin rudalics
2017-10-30 14:32 ` Drew Adams
2017-10-30 19:00 ` martin rudalics
2017-10-30 19:16 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59F0412F.9090206@gmx.at \
--to=rudalics@gmx.at \
--cc=28978@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.