unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: 路客 <luke.yx.lee@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>,
	martin rudalics <rudalics@gmx.at>
Subject: Re: [ELPA] Brief v5.90: neighboring window merge on deletion
Date: Sat, 23 Mar 2024 20:33:31 +0200	[thread overview]
Message-ID: <86il1cvp7o.fsf@mail.linkov.net> (raw)
In-Reply-To: <CAA=xLRMmkA4n2j-uvM40QzEg=xxo9TEDNkO1xcr1wOZPT5+ABQ@mail.gmail.com> ("路客"'s message of "Fri, 22 Mar 2024 19:23:55 +0800")

> 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.



  parent reply	other threads:[~2024-03-23 18:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 11:23 [ELPA] Brief v5.90: neighboring window merge on deletion 路客
2024-03-22 13:22 ` Emanuel Berg
2024-03-23 18:33 ` Juri Linkov [this message]
2024-03-24  5:13   ` 路客
2024-03-24  9:54     ` martin rudalics
2024-03-24 15:51       ` 路客
2024-03-25  9:40         ` martin rudalics
2024-03-26  2:31           ` 路客
2024-03-26  9:57             ` martin rudalics
2024-03-26 12:51               ` Eli Zaretskii
2024-03-27  7:35                 ` martin rudalics
  -- strict thread matches above, loose matches on Subject: below --
2024-03-24  3:25 路客

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86il1cvp7o.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=emacs-devel@gnu.org \
    --cc=luke.yx.lee@gmail.com \
    --cc=rudalics@gmx.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).