From: Juri Linkov <juri@linkov.net>
To: Mickey Petersen <mickey@masteringemacs.org>
Cc: 59721@debbugs.gnu.org
Subject: bug#59721: 30.0.50; tab bar groups are not ordered properly
Date: Wed, 30 Nov 2022 19:09:46 +0200 [thread overview]
Message-ID: <86pmd4fjxh.fsf@mail.linkov.net> (raw)
In-Reply-To: <871qpk1jcl.fsf@masteringemacs.org> (Mickey Petersen's message of "Wed, 30 Nov 2022 16:43:21 +0000")
> I did not check if that solves it, but this issue --
> and how I discovered it -- manifests itself when you use
> `display-buffer-in-[new]-tab' and set a tab group that way.
>
> This can result in a large amount of distinct tab group entries for
> the same tab group; does `tab-bar-tab-post-change-group-functions'
> also resolve this?
Your guess is right. After customizing this variable and using e.g.
(add-to-list 'display-buffer-alist
'("buffer1" .
(display-buffer-in-tab
(tab-name . "C")
(tab-group . "foo"))))
it merges the new tab with its group.
> Because just about anybody who'd use said display buffer action would
> find themselves in this predicament and that variable (and
> subsequently adding that function to it) is... unintuitive.
So you suggest to make this value the default? Ok, the default value
will be changed in the release branch.
next prev parent reply other threads:[~2022-11-30 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 10:42 bug#59721: 30.0.50; tab bar groups are not ordered properly Mickey Petersen
2022-11-30 16:38 ` Juri Linkov
2022-11-30 16:43 ` Mickey Petersen
2022-11-30 17:09 ` Juri Linkov [this message]
2022-11-30 18:41 ` Mickey Petersen
2022-11-30 19:38 ` 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=86pmd4fjxh.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=59721@debbugs.gnu.org \
--cc=mickey@masteringemacs.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).