From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: About the 'minibuffer' frame parameter Date: Fri, 05 Aug 2016 22:25:59 +0300 Message-ID: <837fbvkofs.fsf@gnu.org> References: <579E3F9E.8020200@gmx.at> <83h9azl4s1.fsf@gnu.org> <57A4C0DE.3060506@gmx.at> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1470425224 9680 195.159.176.226 (5 Aug 2016 19:27:04 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 5 Aug 2016 19:27:04 +0000 (UTC) Cc: emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Aug 05 21:27:01 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bVklf-0000aD-45 for ged-emacs-devel@m.gmane.org; Fri, 05 Aug 2016 21:26:51 +0200 Original-Received: from localhost ([::1]:46873 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bVklb-00088k-O1 for ged-emacs-devel@m.gmane.org; Fri, 05 Aug 2016 15:26:47 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52094) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bVkl3-00088Q-P1 for emacs-devel@gnu.org; Fri, 05 Aug 2016 15:26:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bVkky-0002ik-6P for emacs-devel@gnu.org; Fri, 05 Aug 2016 15:26:12 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:54049) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bVkky-0002ic-30; Fri, 05 Aug 2016 15:26:08 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1290 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bVkkw-00070s-6F; Fri, 05 Aug 2016 15:26:06 -0400 In-reply-to: <57A4C0DE.3060506@gmx.at> (message from martin rudalics on Fri, 05 Aug 2016 18:37:50 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:206433 Archived-At: > Date: Fri, 05 Aug 2016 18:37:50 +0200 > From: martin rudalics > CC: emacs-devel@gnu.org > > > You mean, you think there's some code out there that expects to > > receive nil in that case? Do we have any code in our tree that might > > expect that? > > I'm afraid so, yes. Otherwise this rigmarole would hardly make sense. > > But I haven't checked all places because I rather soonish stumbled upon > things like > > (eq (cdr (or (assq 'minibuffer initial-frame-alist) > (assq 'minibuffer window-system-frame-alist) > (assq 'minibuffer default-frame-alist) > '(minibuffer . t))) > t) > > in ‘frame-notice-user-settings’. And one revealing comment is in > ‘set-frame-configuration’: > > ;; Since we can't set a frame's minibuffer status, > ;; we might as well omit the parameter altogether. We could simply change the above code to follow suit.