bug#3276: 23.0.93; doc for minibuffer-frame-alist

bug#3276: 23.0.93; doc for minibuffer-frame-alist

[Drew Adams]

In GNU Emacs 23.0.93.1 (i386-mingw-nt5.1.2600)
 of 2009-05-02 on SOFT-MJASON
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'
 
Doc string says:
 
 Alist of parameters for initial minibuffer frame.
 You can set this in your init file; for example,
 
  (setq minibuffer-frame-alist
        '((top . 1) (left . 1) (width . 80) (height . 2)))
 
 Parameters specified here supersede the values given in
 `default-frame-alist', for a minibuffer frame.
 
But this option is *only* for a standalone minibuffer frame, and such
a frame must have this frame parameter: (minibuffer . only). So that
example is a bad one.
 
Elisp manual says:
 
 This variable's value is an alist of parameter values used when
 creating an initial minibuffer-only frame--if such a frame is
 needed, according to the parameters for the main initial frame.
 
What does "if such a frame is needed" mean here?  When (why) would it
be needed?  What does "according to the parameters for the main
initial frame" mean here? 
 
This description is less informative than the doc string. And like the
doc string, it should mention that parameter `minibuffer' should have
value `only'.

bug#3276: marked as done (23.0.93; doc for minibuffer-frame-alist)

[Emacs bug Tracking System]

[-- Attachment #1: Type: text/plain, Size: 864 bytes --]


Your message dated Thu, 14 May 2009 00:02:10 -0400
with message-id <87zldg9vst.fsf@cyd.mit.edu>
and subject line Re: 23.0.93; doc for minibuffer-frame-alist
has caused the Emacs bug report #3276,
regarding 23.0.93; doc for minibuffer-frame-alist
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
3276: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=3276
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 3881 bytes --]

From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-pretest-bug@gnu.org>
Subject: 23.0.93; doc for minibuffer-frame-alist
Date: Wed, 13 May 2009 15:10:48 -0700
Message-ID: <008201c9d417$acb8d360$0200a8c0@us.oracle.com>

In GNU Emacs 23.0.93.1 (i386-mingw-nt5.1.2600)
 of 2009-05-02 on SOFT-MJASON
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'
 
Doc string says:
 
 Alist of parameters for initial minibuffer frame.
 You can set this in your init file; for example,
 
  (setq minibuffer-frame-alist
        '((top . 1) (left . 1) (width . 80) (height . 2)))
 
 Parameters specified here supersede the values given in
 `default-frame-alist', for a minibuffer frame.
 
But this option is *only* for a standalone minibuffer frame, and such
a frame must have this frame parameter: (minibuffer . only). So that
example is a bad one.
 
Elisp manual says:
 
 This variable's value is an alist of parameter values used when
 creating an initial minibuffer-only frame--if such a frame is
 needed, according to the parameters for the main initial frame.
 
What does "if such a frame is needed" mean here?  When (why) would it
be needed?  What does "according to the parameters for the main
initial frame" mean here? 
 
This description is less informative than the doc string. And like the
doc string, it should mention that parameter `minibuffer' should have
value `only'.




[-- Attachment #3: Type: message/rfc822, Size: 1728 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 3276-done@emacsbugs.donarmstrong.com
Subject: Re: 23.0.93; doc for minibuffer-frame-alist
Date: Thu, 14 May 2009 00:02:10 -0400
Message-ID: <87zldg9vst.fsf@cyd.mit.edu>

>  Alist of parameters for initial minibuffer frame.
>  You can set this in your init file; for example,
> 
>   (setq minibuffer-frame-alist
>         '((top . 1) (left . 1) (width . 80) (height . 2)))
> 
>  Parameters specified here supersede the values given in
>  `default-frame-alist', for a minibuffer frame.
> 
> But this option is *only* for a standalone minibuffer frame, and such
> a frame must have this frame parameter: (minibuffer . only). So that
> example is a bad one.

Actually, (minibuffer . only) is automatically appended.

> What does "if such a frame is needed" mean here?  When (why) would it
> be needed?

I clarified this in the docstring and the manual.

bug#3276: 23.0.93; doc for minibuffer-frame-alist

[Stefan Monnier]

>  Alist of parameters for initial minibuffer frame.
>  You can set this in your init file; for example,
 
>   (setq minibuffer-frame-alist
>         '((top . 1) (left . 1) (width . 80) (height . 2)))
 
>  Parameters specified here supersede the values given in
>  `default-frame-alist', for a minibuffer frame.
 
> But this option is *only* for a standalone minibuffer frame, and such
> a frame must have this frame parameter: (minibuffer . only).  So that
> example is a bad one.

No: the (minibuffer . only) part will be added automatically.
 
> What does "if such a frame is needed" mean here?

If the current terminal doesn't have any minibuffer (all the frame are
minibuffer-less). then a minibuffer-only frame is automatically created
(using the settings in minibuffer-frame-alist).


        Stefan