From mboxrd@z Thu Jan 1 00:00:00 1970 Path: quimby.gnus.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Weird frame/buffer interaction Date: Wed, 6 Mar 2002 19:30:03 -0700 (MST) Message-ID: <200203070230.g272U3Y02066@wijiji.santafe.edu> References: <37D24D4FFB26F74D8F4C82CF039354F1013883C4@xch-stl-08.mw.nos.boeing.com> Reply-To: rms@gnu.org NNTP-Posting-Host: quimby2.netfonds.no X-Trace: quimby2.netfonds.no 1015468852 18990 195.204.10.66 (7 Mar 2002 02:40:52 GMT) X-Complaints-To: usenet@quimby2.netfonds.no NNTP-Posting-Date: 7 Mar 2002 02:40:52 GMT Cc: storm@cua.dk, eliz@is.elta.co.il, emacs-devel@gnu.org Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby2.netfonds.no with esmtp (Exim 3.12 #1 (Debian)) id 16inps-0004wC-00 for ; Thu, 07 Mar 2002 03:40:52 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.33 #1 (Debian)) id 16inid-0000Jd-00; Wed, 06 Mar 2002 21:33:23 -0500 Original-Received: from pele.santafe.edu ([192.12.12.119]) by fencepost.gnu.org with esmtp (Exim 3.33 #1 (Debian)) id 16infR-0006r3-00; Wed, 06 Mar 2002 21:30:05 -0500 Original-Received: from wijiji.santafe.edu (wijiji [192.12.12.5]) by pele.santafe.edu (8.11.6+Sun/8.9.3) with ESMTP id g272UEu11090; Wed, 6 Mar 2002 19:30:14 -0700 (MST) Original-Received: (from rms@localhost) by wijiji.santafe.edu (8.11.6+Sun/8.9.3) id g272U3Y02066; Wed, 6 Mar 2002 19:30:03 -0700 (MST) X-Authentication-Warning: wijiji.santafe.edu: rms set sender to rms@wijiji using -f Original-To: michael.p.broida@boeing.com In-reply-to: <37D24D4FFB26F74D8F4C82CF039354F1013883C4@xch-stl-08.mw.nos.boeing.com> (michael.p.broida@boeing.com) Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: quimby.gnus.org gmane.emacs.devel:1772 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:1772 I appreciate the effort that you are making to explore the envelope of this bug, but that is not an effective way to get to the bottom of things. Information about the envelope of the bug will never lead us to the cause of the problem. That is not the way problems are found. What would in fact help is a test case that we can really try. I cannot try the test case that was sent because I can't do anything with such a tall frame. Can you find a test case which uses an ordinary size frame? I suggest you read the Bugs section in the Emacs manual, which explains what information will actually help find the bug. _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://mail.gnu.org/mailman/listinfo/emacs-devel