From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@linkov.net>
Cc: 38354@debbugs.gnu.org
Subject: bug#38354: 27.0.50; Implement display action display-buffer-in-tab
Date: Fri, 6 Dec 2019 08:37:10 +0100 [thread overview]
Message-ID: <b19df32e-306b-3249-1ad5-6f7f04ec5aca@gmx.at> (raw)
In-Reply-To: <87r21is5h9.fsf@mail.linkov.net>
> Still unclear what window currently code prefers in case of two
> or more windows displaying the same buffer, or when the buffer
> is displayed in windows of two or more frames. What window/frame it
> reuses? Just the first found?
The order is determined by 'get-buffer-window-list' which in its turn
relies on 'window-list-1'.
> Is it possible to express such
> preferences for multiple windows/frames in display-buffer-alist?
It tries the selected window first and a window on the selected frame
afterwards. If both fail it respects 'reusable-frames'.
>> OK. But what if another action adds something to such a tab and we
>> then quit the window. Or is such a scenario impossible?
>
> Does a similar situation happen in case of window quitting?
> Then the same logic could be reused for tab quitting.
> When another buffer is displayed in the same window,
> then quit-window doesn't delete the window with another buffer?
Correct. 'quit-restore-window' is quite sensitive wrt such changes
and refrains from doing more drastic things (like deleting a window or
frame) when the user has switched buffers in between.
martin
next prev parent reply other threads:[~2019-12-06 7:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 23:09 bug#38354: 27.0.50; Implement display action display-buffer-in-tab Juri Linkov
2019-11-26 9:32 ` martin rudalics
2019-11-26 22:30 ` Juri Linkov
2019-11-26 22:43 ` Juri Linkov
2019-11-27 9:49 ` martin rudalics
2019-11-27 21:37 ` Juri Linkov
2019-11-28 9:20 ` martin rudalics
2019-11-28 23:02 ` Juri Linkov
2019-11-29 9:24 ` martin rudalics
2019-12-01 22:29 ` Juri Linkov
2019-12-02 9:40 ` martin rudalics
2019-12-02 23:43 ` Juri Linkov
2019-12-03 9:18 ` martin rudalics
2019-12-03 23:36 ` Juri Linkov
2019-12-04 9:22 ` martin rudalics
2019-12-04 22:51 ` Juri Linkov
2019-12-05 9:05 ` martin rudalics
2019-12-05 23:54 ` Juri Linkov
2019-12-06 7:37 ` martin rudalics [this message]
2022-12-06 17:40 ` 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=b19df32e-306b-3249-1ad5-6f7f04ec5aca@gmx.at \
--to=rudalics@gmx.at \
--cc=38354@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).