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.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 3278 in the body.
You can then email your comments to 3278 AT debbugs.gnu.org in the normal way.

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

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>:
bug#3278; Package emacs. (Wed, 13 May 2009 22:35:04 GMT) Full text and rfc822 format available.
Acknowledgement sent to "Drew Adams" <drew.adams <at> oracle.com>:
New bug report received and forwarded. Copy sent to Emacs Bugs <bug-gnu-emacs <at> gnu.org>. (Wed, 13 May 2009 22:35:04 GMT) Full text and rfc822 format available.

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; 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)'
Reply sent to Chong Yidong <cyd <at> stupidchicken.com>:
You have taken responsibility. (Thu, 14 May 2009 04:35:04 GMT) Full text and rfc822 format available.
Notification sent to "Drew Adams" <drew.adams <at> oracle.com>:
bug acknowledged by developer. (Thu, 14 May 2009 04:35:04 GMT) Full text and rfc822 format available.

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

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.
bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> emacsbugs.donarmstrong.com. (Thu, 11 Jun 2009 14:24:09 GMT) Full text and rfc822 format available.
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.