unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: owner@emacsbugs.donarmstrong.com (Emacs bug Tracking System)
To: Chong Yidong <cyd@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	[thread overview]
Message-ID: <handler.3278.D3278.124227545732647.ackdone@emacsbugs.donarmstrong.com> (raw)
In-Reply-To: 008f01c9d41a$4bc48ba0$0200a8c0@us.oracle.com

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]


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

[-- Attachment #2: Type: message/rfc822, Size: 3411 bytes --]

From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-pretest-bug@gnu.org>
Subject: 23.0.93; Elisp manual, node Buffer Parameters
Date: Wed, 13 May 2009 15:29:34 -0700
Message-ID: <008f01c9d41a$4bc48ba0$0200a8c0@us.oracle.com>

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




[-- Attachment #3: Type: message/rfc822, Size: 1372 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 3279-done@emacsbugs.donarmstrong.com, 3278-done@emacsbugs.donarmstrong.com
Subject: Re: 23.0.93; doc for frame parameter `minibuffer'
Date: Thu, 14 May 2009 00:31:02 -0400
Message-ID: <87fxf8tiex.fsf@cyd.mit.edu>

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


  reply	other threads:[~2009-05-14  4:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87fxf8tiex.fsf@cyd.mit.edu>
2009-05-13 22:29 ` bug#3278: 23.0.93; Elisp manual, node Buffer Parameters Drew Adams
2009-05-14  4:35   ` Emacs bug Tracking System [this message]
2009-05-13 22:38 ` bug#3279: 23.0.93; doc for frame parameter `minibuffer' Drew Adams
2009-05-14  4:35   ` bug#3279: marked as done (23.0.93; doc for frame parameter `minibuffer') Emacs bug Tracking System

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=handler.3278.D3278.124227545732647.ackdone@emacsbugs.donarmstrong.com \
    --to=owner@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).