GNU bug report logs - #3278
23.0.93; Elisp manual, node Buffer Parameters

Previous Next

Package: emacs;

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

Date: Wed, 13 May 2009 22:35:04 UTC

Severity: normal

Done: Chong Yidong <cyd <at> stupidchicken.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (Emacs bug Tracking System)
To: Chong Yidong <cyd <at> stupidchicken.com>
Subject: bug#3278: marked as done (23.0.93; Elisp manual, node Buffer 
 Parameters)
Date: Thu, 14 May 2009 04:35:04 +0000
[Message part 1 (text/plain, inline)]
Your message dated Thu, 14 May 2009 00:31:02 -0400
with message-id <87fxf8tiex.fsf <at> 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 help-debbugs <at> gnu.org
immediately.)


-- 
3278: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3278
Emacs Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: "Drew Adams" <drew.adams <at> oracle.com>
To: <emacs-pretest-bug <at> gnu.org>
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)'
 



[Message part 3 (message/rfc822, inline)]
From: Chong Yidong <cyd <at> stupidchicken.com>
To: "Drew Adams" <drew.adams <at> oracle.com>
Cc: 3279-done <at> debbugs.gnu.org, 3278-done <at> debbugs.gnu.org
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.


This bug report was last modified 16 years and 12 days ago.

Previous Next


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