GNU bug report logs - #3276
23.0.93; doc for minibuffer-frame-alist

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 3276 in the body.
You can then email your comments to 3276 AT debbugs.gnu.org in the normal way.

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

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: "Drew Adams" <drew.adams <at> oracle.com>
To: <emacs-pretest-bug <at> gnu.org>
Subject: 23.0.93; doc for minibuffer-frame-alist
Date: Wed, 13 May 2009 15:10:48 -0700

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'.

Message #10 received at 3276-done <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Chong Yidong <cyd <at> stupidchicken.com>
To: "Drew Adams" <drew.adams <at> oracle.com>
Cc: 3276-done <at> debbugs.gnu.org
Subject: Re: 23.0.93; doc for minibuffer-frame-alist
Date: Thu, 14 May 2009 00:02:10 -0400

>  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.

Message #11 received at 3276-done <at> emacsbugs.donarmstrong.com (full text, mbox):

From: "Drew Adams" <drew.adams <at> oracle.com>
To: "'Chong Yidong'" <cyd <at> stupidchicken.com>
Cc: <3276-done <at> debbugs.gnu.org>
Subject: RE: 23.0.93; doc for minibuffer-frame-alist
Date: Thu, 14 May 2009 00:43:00 -0700

> From: Chong Yidong Sent: Wednesday, May 13, 2009 9:02 PM
> >  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.

All the more reason that that example alone is unclear. It needs to be said
explicitly that that example setting is sufficient because (minibuffer . only)
is automatically appended. The `only' value needs to be mentioned somewhere here
- it is what this is all about.

> > 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.

Thanks.

Message #16 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 3276 <at> debbugs.gnu.org, <emacs-pretest-bug <at> gnu.org>
Subject: Re: bug#3276: 23.0.93; doc for minibuffer-frame-alist
Date: Sun, 17 May 2009 15:13:46 -0400

>  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

Previous Next

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