From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: 23.0.50; Cannot run calculator on TTY Date: Fri, 12 Oct 2007 20:18:58 -0400 Message-ID: References: <20071001023514.E164D12A4071@localhost> <470090AD.7020701@gmx.at> <18176.62320.27921.579761@gargle.gargle.HOWL> <4701153E.7010408@gmx.at> <18177.46954.59945.891659@gargle.gargle.HOWL> <4701F402.6060403@gmx.at> <18178.18023.858644.85600@gargle.gargle.HOWL> <47028522.60003@gmx.at> <18178.62745.602748.437486@gargle.gargle.HOWL> <470334E7.9020102@gmx.at> <18179.41840.532732.664369@gargle.gargle.HOWL> <18187.33374.913139.901742@gargle.gargle.HOWL> <470BB544.8090708@gmx.at> <18189.42188.229008.184425@gargle.gargle.HOWL> <470DE3E8.3080401@gmx.at> <18190.9560.402525.665860@gargle.gargle.HOWL> <470F3D19.2080702@gmx.at> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1192234906 12504 80.91.229.12 (13 Oct 2007 00:21:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 13 Oct 2007 00:21:46 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, raman@users.sf.net To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 13 02:21:33 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IgUkm-00019S-Jd for ged-emacs-devel@m.gmane.org; Sat, 13 Oct 2007 02:21:16 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IgUkg-0006s0-AS for ged-emacs-devel@m.gmane.org; Fri, 12 Oct 2007 20:21:10 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IgUib-0005nL-A2 for emacs-devel@gnu.org; Fri, 12 Oct 2007 20:19:01 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IgUiZ-0005lr-Ri for emacs-devel@gnu.org; Fri, 12 Oct 2007 20:19:00 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IgUiZ-0005lU-F4 for emacs-devel@gnu.org; Fri, 12 Oct 2007 20:18:59 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IgUiZ-0002HF-6c for emacs-devel@gnu.org; Fri, 12 Oct 2007 20:18:59 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1IgUiY-0008AF-7R; Fri, 12 Oct 2007 20:18:58 -0400 In-reply-to: <470F3D19.2080702@gmx.at> (message from martin rudalics on Fri, 12 Oct 2007 11:23:37 +0200) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:80755 gmane.emacs.pretest.bugs:20103 Archived-At: Presently, `split-window' has a problem with mode/header lines and small heights (presumably also with scroll-bars and fringes). To check whether all windows are large enough after splitting it must make an assumption about the presence of these on the new window. It currently bases its judgments on the appearance of the window that shall be split. Strictly speaking, that is correct. Splitting the window shows the same buffer in both of the resulting windows, so it is valid if that buffer could be displayed in both. However, in a larger sense, given that the aim is to display another window there, this does not really DTRT. One idea that occurs to me is that `window-min-height' could count the header line, if any. That way, the fact that some buffers have header lines and others don't will not cause any problems for vertical splitting of windows. In the most usual cases, at least -- but not in all cases, perhaps. Another solution would be to pass a two buffers to `split-window', telling it to select those two buffers, and to calculate based on the assumption that those buffers will be displayed.