bug#3278: marked as done (23.0.93; Elisp manual, node Buffer Parameters)

[Emacs bug Tracking System]

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 #3278,
regarding 23.0.93; Elisp manual, node Buffer Parameters
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.)


-- 
3278: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=3278
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 23.0.93; Elisp manual, node Buffer Parameters
>
>
>
>
> Date: 
>
> Wed, 13 May 2009 15:29:34 -0700
>
>
>
>
> 1. Neither `minibuffer' nor `unsplittable' seem to have much to do
> with `Buffer Parameters'. The node organization is not good.
>  
> 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. 
>  
> If the value is a minibuffer window in some other frame, then this
> frame does not have its own minibuffer (remember, this is about
> "whether this frame has its own minibuffer"). Instead, this frame uses
> the minibuffer in that window.
>  
>
> 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 ---