From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.help Subject: Re: window-size-fixed behaviour on emacs22-gtk Date: Mon, 22 Jun 2009 15:07:04 +0200 Message-ID: <4A3F81F8.8040401@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1245676168 2311 80.91.229.12 (22 Jun 2009 13:09:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 22 Jun 2009 13:09:28 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: hjuvi-google@yahoo.fr Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Jun 22 15:09:24 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MIjH1-0004Op-JY for geh-help-gnu-emacs@m.gmane.org; Mon, 22 Jun 2009 15:09:23 +0200 Original-Received: from localhost ([127.0.0.1]:44932 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MIjH0-0003Me-Jg for geh-help-gnu-emacs@m.gmane.org; Mon, 22 Jun 2009 09:09:22 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MIjEw-0002Th-Pt for help-gnu-emacs@gnu.org; Mon, 22 Jun 2009 09:07:14 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MIjEs-0002QZ-7z for help-gnu-emacs@gnu.org; Mon, 22 Jun 2009 09:07:14 -0400 Original-Received: from [199.232.76.173] (port=43282 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MIjEr-0002QR-Tf for help-gnu-emacs@gnu.org; Mon, 22 Jun 2009 09:07:09 -0400 Original-Received: from mail.gmx.net ([213.165.64.20]:52935) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MIjEr-0000dq-3Q for help-gnu-emacs@gnu.org; Mon, 22 Jun 2009 09:07:09 -0400 Original-Received: (qmail invoked by alias); 22 Jun 2009 13:07:06 -0000 Original-Received: from 62-47-63-139.adsl.highway.telekom.at (EHLO [62.47.63.139]) [62.47.63.139] by mail.gmx.net (mp071) with SMTP; 22 Jun 2009 15:07:06 +0200 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX19wMAEAoaVwQOb0eAvJtG9b1yB8Pw3Jw2oPUKt5+5 fpcKvkudi+5Xn/ User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) Original-References: 54009744-c71b-469d-b747-7af1bad6985b@z34g2000vbl.googlegroups.com X-Y-GMX-Trusted: 0 X-FuHaFi: 0.71 X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:65429 Archived-At: > I cannot find out whether it is a bug in emacs, or I misuse window- > fixed-size feature. Both problems were probably caused by the introduction of the function `adjust-window-trailing-edge'. The fact that you can drag the upper mode-line is a clear bug because it allows to resize a fixed-size window. Please make a bug report to make sure that this issue gets fixed for Emacs 23.2 (it might take some time, so don't hold your breath). Alas, the only possible fix I can think of currently is that you won't be allowed to drag that mode-line either. The fact that you cannot move an entire window up or down is very regrettable but I'm afraid that fixing that might be very difficult. Note that with Emacs 21 you were able to have three resizable windows above each other and enlarge the lowest one (dragging the mode-line above it) by shrinking the uppermost one. This is unfortunately no longer possible with Emacs 22 (you can only resize the window in the middle) and has the same cause as the problem you describe. I'm still not sure what problem `adjust-window-trailing-edge' was trying to resolve but suppose that writing that function threw out the child with the bathwater. Maybe you can trigger a discussion about this after making the bug report so please make sure to file one. Thanks in advance, martin.