GNU bug report logs - #12144
24.1; (elisp) `Initial Parameters' misleading about minibuffer-only

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 12144 in the body.
You can then email your comments to 12144 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

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

From: "Drew Adams" <drew.adams <at> oracle.com>
To: <bug-gnu-emacs <at> gnu.org>
Subject: 24.1; (elisp) `Initial Parameters' misleading about minibuffer-only
Date: Sun, 5 Aug 2012 16:06:23 -0700

In this node, the text tries to say that if `initial-frame-alist'
contains (minbuffer), i.e., (minibuffer . nil) then that means that you
also want to create another, minibuffer-only frame, which has the
parameter value (minbuffer . only).  And so Emacs creates that
standalone minibuffer frame for you automatically.
 
The existing text that tries to say this is highly misleading.  It
actually suggests that (minibuffer . nil) specifies a separate
minibuffer-only frame, whereas it is (minibuffer . only) that specifies
that.
 
IOW, it tries to do too much in a single sentence.  What it should say
is that (minibuffer . nil) means that the initial frame has NO
minibuffer.  And that if you do that then Emacs assumes you want a
standalone minibuffer frame, so it creates one for you.
 
IOW, although creation of the standalone minibuffer frame is really
separate from creation of the initial frame, if the initial frame does
not have a minibuffer then Emacs creates two frames, the second being
minibuffer-only.
 
All that should be said is this:
 
"If `initial-frame-alist' contains (minibuffer . nil) then Emacs creates
not only an initial frame, with no minibuffer, but also a separate,
minibuffer-only frame."
 

In GNU Emacs 24.1.1 (i386-mingw-nt5.1.2600)
 of 2012-06-10 on MARVIN
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
 `configure --with-gcc (4.6) --cflags
 -ID:/devel/emacs/libs/libXpm-3.5.8/include
 -ID:/devel/emacs/libs/libXpm-3.5.8/src
 -ID:/devel/emacs/libs/libpng-dev_1.4.3-1/include
 -ID:/devel/emacs/libs/zlib-dev_1.2.5-2/include
 -ID:/devel/emacs/libs/giflib-4.1.4-1/include
 -ID:/devel/emacs/libs/jpeg-6b-4/include
 -ID:/devel/emacs/libs/tiff-3.8.2-1/include
 -ID:/devel/emacs/libs/gnutls-3.0.9/include'
 

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

From: "Drew Adams" <drew.adams <at> oracle.com>
To: <12144 <at> debbugs.gnu.org>
Subject: RE: bug#12144: 24.1;
	(elisp) `Initial Parameters' misleading about minibuffer-only
Date: Sun, 16 Sep 2012 16:36:12 -0700

ping

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

From: Chong Yidong <cyd <at> gnu.org>
To: "Drew Adams" <drew.adams <at> oracle.com>
Cc: 12144 <at> debbugs.gnu.org
Subject: Re: bug#12144: 24.1;
	(elisp) `Initial Parameters' misleading about minibuffer-only
Date: Mon, 05 Nov 2012 22:31:15 +0800

"Drew Adams" <drew.adams <at> oracle.com> writes:

> In this node, the text tries to say that if `initial-frame-alist'
> contains (minbuffer), i.e., (minibuffer . nil) then that means that you
> also want to create another, minibuffer-only frame, which has the
> parameter value (minbuffer . only).  And so Emacs creates that
> standalone minibuffer frame for you automatically.
>  
> The existing text that tries to say this is highly misleading.  It
> actually suggests that (minibuffer . nil) specifies a separate
> minibuffer-only frame, whereas it is (minibuffer . only) that specifies
> that.

Fixed, thanks.

Previous Next

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