From: martin rudalics <rudalics@gmx.at>
To: Lars Ingebrigtsen <larsi@gnus.org>, Juri Linkov <juri@linkov.net>
Cc: 47300@debbugs.gnu.org
Subject: bug#47300: delete-window to select window with same position
Date: Tue, 18 May 2021 18:00:40 +0200 [thread overview]
Message-ID: <7f870f9b-95ad-6b5d-82aa-1bcfe5cc880a@gmx.at> (raw)
In-Reply-To: <87pmxodrmq.fsf@gnus.org>
>> People still have trouble with unpredictable behavior of 'C-x 0'
>> that selects an unexpected window after the current window is deleted.
>>
>> This is a recent example:
>> https://old.reddit.com/r/emacs/comments/m8omt0/how_can_deletewindow_cx_0_be_configured_to_stay/
>>
>> The previous failed attempt to fix this was in bug#32790.
>>
>> I still don't understand the current logic what window is selected
>> after deleting the selected window with 'C-x 0'.
By design it's the most recently used window (`get-mru-window') on the
same frame after the deleted window has been removed from its window
tree.
> `C-x 0' isn't a command I use much, so I don't really have much
> intuition about how it's supposed to work. But, indeed, playing around
> with it, it seems unexpected that `C-x 0' selects a different window
> (instead of remaining in the "merged" window).
>
>> Maybe something like this could be adapted to delete-window
>> by adding an optional interactive argument keep-pos:
>
> If I'm reading that patch correctly (I haven't actually tested), that
> seems more DWIM to me. Perhaps Martin has some comments here; added to
> the CCs. (And if anybody else has an opinion here, please do chime in.)
Personally I don't care but people used to the current behavior might
get confused. So an option should be the provided and could be "ON" by
default.
martin
next prev parent reply other threads:[~2021-05-18 16:00 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 [this message]
2021-05-18 20:17 ` Juri Linkov
2021-05-19 7:42 ` martin rudalics
2021-05-19 16:07 ` Juri Linkov
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=7f870f9b-95ad-6b5d-82aa-1bcfe5cc880a@gmx.at \
--to=rudalics@gmx.at \
--cc=47300@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
/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).