unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: 路客 <luke.yx.lee@gmail.com>, "Juri Linkov" <juri@linkov.net>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: [ELPA] Brief v5.90: neighboring window merge on deletion
Date: Sun, 24 Mar 2024 10:54:37 +0100	[thread overview]
Message-ID: <ea29c62e-7ebb-4ba1-9022-d778d085db29@gmx.at> (raw)
In-Reply-To: <CAA=xLRNPk3WqwOjVAgE902OY1SFtPc5mpWGRg9iNuVScZxqeEg@mail.gmail.com>

 > Now if we use Brief `<F4> <right>' command from the `S' (`S'elected)
 > window to delete the `T' (`T'arget) window, it will reconstruct the
 > windows by deleting all the windows keeping only `S', then re-split
 > the frame by first split horizontally the window, then reconstruct
 > the bottom two windows achieving the desired layout:
 >   _____
 > |_S___|
 > |__|__|
 >
 > This reconstruction happens instantaneously so it's almost not
 > noticeable to users unless on slow terminals.  Sometimes in X windows
 > the affected window boundary might shift a little if the original layout
 > is complicated or is 1-character in width/height difference between
 > `S' and `T' (my default 1-character tolerance setting).

Your reconstruction kills all previously live windows but 'S' and
produces new ones.  This means that buffer overlays with a 'window'
property will not work correctly in any of the new ones.  Moreover, if
such windows were stored in Lisp variables, they would be considered
dead although they apparently still exist like the ones in the lower
part of your frame.

 > This also explains why the following `circular' layout is not possible
 > as we can't find a split line either vertically or horizontally.
 >   ______
 > |____| |
 > | |__|_|
 > |_|____|

Emacs frames are guillotine-patterns.  Each window split corresponds to
a non-intersecting guillotine-cut of the parent window.

martin



  reply	other threads:[~2024-03-24  9:54 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
2024-03-24  5:13   ` 路客
2024-03-24  9:54     ` martin rudalics [this message]
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=ea29c62e-7ebb-4ba1-9022-d778d085db29@gmx.at \
    --to=rudalics@gmx.at \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=luke.yx.lee@gmail.com \
    /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).