From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: bug of display-table & make-glyph-code Date: Thu, 06 Sep 2007 16:49:19 +0200 Message-ID: <46E0136F.6080602@gmx.at> References: <200708271732.22306.zslevin@gmail.com> <46DD9F41.8090700@gmx.at> <46DE63EE.3070509@gmx.at> <87wsv4fvav.fsf@stupidchicken.com> <46DFC3AE.3020009@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: sea.gmane.org 1189091370 16570 80.91.229.12 (6 Sep 2007 15:09:30 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 6 Sep 2007 15:09:30 +0000 (UTC) Cc: Glenn Morris , Chong Yidong , rms@gnu.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 06 17:09:29 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 1ITIyy-0001VP-Io for ged-emacs-devel@m.gmane.org; Thu, 06 Sep 2007 17:09:24 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ITIyw-0008Hz-Dp for ged-emacs-devel@m.gmane.org; Thu, 06 Sep 2007 11:09:22 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ITIys-0008Fy-NO for emacs-devel@gnu.org; Thu, 06 Sep 2007 11:09:18 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ITIyq-0008Ed-LL for emacs-devel@gnu.org; Thu, 06 Sep 2007 11:09:17 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ITIyq-0008Ea-BL for emacs-devel@gnu.org; Thu, 06 Sep 2007 11:09:16 -0400 Original-Received: from mail.gmx.net ([213.165.64.20]) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1ITIyp-000238-NR for emacs-devel@gnu.org; Thu, 06 Sep 2007 11:09:16 -0400 Original-Received: (qmail invoked by alias); 06 Sep 2007 15:09:14 -0000 Original-Received: from N771P016.adsl.highway.telekom.at (EHLO [62.47.40.80]) [62.47.40.80] by mail.gmx.net (mp040) with SMTP; 06 Sep 2007 17:09:14 +0200 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX1/a5eItQUraGb3Df5i6Eh7jXSUD/kPwTcA/KvqBE6 D0ghr7PMOQqSfN User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en In-Reply-To: X-Y-GMX-Trusted: 0 X-Detected-Kernel: 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:77981 Archived-At: >>I suggested to have `display-buffer' not split dedicated windows >>(unless there's just one) which should fix his problem. > > > The case that the OP mentioned seemed like a case where both the old and the > new behaviors are acceptable, with no clear favorite. So I think we may as > well leave the code alone. > Unless I misunderstood or overlooked a detail, of course. Aren't all your windows dedicated, thus it wouldn't make any difference for you? For other users, a dedicated window might express some kind of desire to not have Emacs touch that window if possible. Personally, I have no preferences here. I'd just wanted to propose the OP a way to get his old behavior back. >>If we don't, could someone please tell the OP that we are not going to >>change this. > > > I'm experimenting with a feature that marks some frames as "balanced" such > that any window-creation/deletion or frame resizing causes the windows to be > rebalanced with balance-windows or balance-windows-area. In such > a situation, whether "| a | b |" is split as "|a|c| b |" or as "| a |c|b|" > doesn't matter that much, since that'll be rebalanced to something visually > identical anyway. Would this clash with `temp-buffer-resize-mode'?