bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#3279: marked as done (23.0.93; doc for frame parameter `minibuffer'


From: Emacs bug Tracking System
Subject: bug#3279: marked as done (23.0.93; doc for frame parameter `minibuffer')
Date: Thu, 14 May 2009 04:35:06 +0000

Your message dated Thu, 14 May 2009 00:31:02 -0400
with message-id <87fxf8tiex.fsf@cyd.mit.edu>
and subject line Re: 23.0.93; doc for frame parameter `minibuffer'
has caused the Emacs bug report #3279,
regarding 23.0.93; doc for frame parameter `minibuffer'
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.)


-- 
3279: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=3279
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems
--- Begin Message --- Subject: 23.0.93; doc for frame parameter `minibuffer' Date: Wed, 13 May 2009 15:38:45 -0700
The Elisp manual should say that you cannot change the value of
parameter `minibuffer' for an existing frame.
 
If you try to set it to nil, you get one error. If you try to set it
to a minibuffer window on another frame, you get a different error. If
you try to set it to `only', you get no error, but nothing happens.
We should say that this parameter is only for use in a frame alist
before the frame is created.
 

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




--- End Message ---
--- Begin Message --- Subject: Re: 23.0.93; doc for frame parameter `minibuffer' Date: Thu, 14 May 2009 00:31:02 -0400
> 2. For `minibuffer', "If the value is a minibuffer window (in some
> other frame), the new frame uses that minibuffer." What "new frame"?
> There is no new frame involved here.
>
> The Elisp manual should say that you cannot change the value of
> parameter `minibuffer' for an existing frame.

I clarified this.

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]