From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: [ELPA] Brief v5.90: neighboring window merge on deletion Date: Sat, 23 Mar 2024 20:33:31 +0200 Organization: LINKOV.NET Message-ID: <86il1cvp7o.fsf@mail.linkov.net> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40382"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu) Cc: Emacs developers , martin rudalics To: =?utf-8?B?6Lev5a6i?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Mar 23 19:35:38 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ro6DR-000AJd-Rx for ged-emacs-devel@m.gmane-mx.org; Sat, 23 Mar 2024 19:35:37 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ro6Cc-0001py-R0; Sat, 23 Mar 2024 14:34:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ro6Ca-0001pY-WC for emacs-devel@gnu.org; Sat, 23 Mar 2024 14:34:45 -0400 Original-Received: from relay1-d.mail.gandi.net ([217.70.183.193]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ro6CZ-0000lN-8B for emacs-devel@gnu.org; Sat, 23 Mar 2024 14:34:44 -0400 Original-Received: by mail.gandi.net (Postfix) with ESMTPSA id D431A240002; Sat, 23 Mar 2024 18:34:39 +0000 (UTC) In-Reply-To: (=?utf-8?B?Iui3r+WuoiIncw==?= message of "Fri, 22 Mar 2024 19:23:55 +0800") X-GND-Sasl: juri@linkov.net Received-SPF: pass client-ip=217.70.183.193; envelope-from=juri@linkov.net; helo=relay1-d.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:317253 Archived-At: > In case you are interested. I've just released the Brief editor mode > v5.90 targeting the feature `merge neighboring window on deletion'. > This functionality merges two aligned adjacent windows regardless of how > Emacs currently splits the frame. It meaning that even if two aligned > neighboring windows in the same frame belong to different parent > (internal) windows, they can almost always be merged by reconstructing > the window tree properly. Please explain how this differs from the value 'pos' of 'delete-window-choose-selected'. > This is probably not a big deal but for me this task had been postponed > for over 20 years due to not finding time to implement them until > recently. It took me sometime early this year to figure out an > efficient algorithm. It reconstructs window subtree reorganizing > vertical/horizontal spliter lines to achieve the desired window layout. > However, due to the restriction on how Emacs split windows there are > still layouts that can't be displayed by Emacs. A typical such window > layout is: > ______ > |____| | > | |__|_| > |_|____| > > Any such structure within any sub-window of a frame cannot be displayed, > as far as I know (let me know if any of you know a simple way to do so). > But for regular daily use we don't really need this kind of window > layout so it won't be supported unless a simple approach is found. > > Notice that the atomic window is not yet properly handled and is > on-going, if you find any other window attribute not taken care of > properly, please be sure to let me know.