From: Juri Linkov <juri@linkov.net>
To: martin rudalics <rudalics@gmx.at>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 47300@debbugs.gnu.org
Subject: bug#47300: delete-window to select window with same position
Date: Wed, 19 May 2021 19:07:18 +0300 [thread overview]
Message-ID: <87h7iyzvh5.fsf@mail.linkov.net> (raw)
In-Reply-To: <2ec3b911-4fb1-4b13-a5b8-28278a5c43ba@gmx.at> (martin rudalics's message of "Wed, 19 May 2021 09:42:49 +0200")
>> I can't find where `get-mru-window' is called during window deletion.
>
> It's here in `delete-window-internal'
>
> /* Now look whether `get-mru-window' gets us something. */
> mru_window = call1 (Qget_mru_window, frame);
Thanks, I missed it because I searched with 'C-x p g get-mru-window'
instead of 'C-x p g get.mru.window'.
>> Maybe a new option e.g. `delete-window-select' with type not boolean,
>> but a predicate with the default value `get-mru-window', and another
>> choice `delete-window-select-underlying' to select the "merged" window.
>
> `get-mru-window' is not a predicate. You probably mean a function so
> that someone could also use `get-lru-window' as value of that option?
Yes, a function to get a window to select after window deletion.
> The problem with such a function is that it has to be called with some
> predefined sort of FRAME or ALL-FRAMES argument so some explanatory
> footwork would be required.
It's fine to call it with a FRAME argument. The problem is
how to write such a function that will find the window that
gets the screen space previously owned by the deleted window.
Could you recommend the right direction? Maybe this window that
gets the screen space is just the parent of the deleted window?
next prev parent reply other threads:[~2021-05-19 16:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 20:31 bug#47300: delete-window to select window with same position Juri Linkov
2021-05-18 14:49 ` Lars Ingebrigtsen
2021-05-18 16:00 ` martin rudalics
2021-05-18 20:17 ` Juri Linkov
2021-05-19 7:42 ` martin rudalics
2021-05-19 16:07 ` Juri Linkov [this message]
2021-05-19 17:41 ` martin rudalics
2021-05-22 8:05 ` martin rudalics
2021-05-22 21:25 ` Juri Linkov
2021-05-23 8:43 ` martin rudalics
2021-05-25 6:50 ` martin rudalics
2021-05-26 21:29 ` Juri Linkov
2021-05-27 15:20 ` martin rudalics
2021-05-31 20:46 ` Juri Linkov
2021-06-02 9:08 ` martin rudalics
2021-06-03 21:20 ` Juri Linkov
2021-06-04 9:19 ` martin rudalics
2021-06-04 16:29 ` Juri Linkov
2021-06-06 7:43 ` martin rudalics
2021-06-06 20:47 ` Juri Linkov
2021-06-07 7:35 ` martin rudalics
2021-06-07 21:00 ` Juri Linkov
2021-06-10 7:44 ` martin rudalics
2021-06-11 17:06 ` Juri Linkov
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=87h7iyzvh5.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=47300@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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).