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 18:38:57 +0200 [thread overview]
Message-ID: <86o7soii72.fsf@mail.linkov.net> (raw)
In-Reply-To: <87iliw206h.fsf@masteringemacs.org> (Mickey Petersen's message of "Wed, 30 Nov 2022 10:42:30 +0000")
> 1. Enable tab-bar-mode and then alter tab-bar-format to show groups. Something like this:
>
> (setq tab-bar-format '(tab-bar-format-history tab-bar-format-tabs-groups tab-bar-separator tab-bar-format-add-tab))
>
> 2. Create three tabs: A, B, C. Now switch to A and use M-x
> tab-bar-change-tab-group and name it "foo". Now switch to C and name
> it "foo" also.
>
> 3. The tab bar groups are _not_ merged; with a large array of tab
> bars, this causes endless confusion as there are man duplicae tab
> groups. You would expect a tab group to coalesce like tab group
> members into a singular tab group --- that is after all their purpose.
Thanks for the bug report. We had a discussion about this problem
in the past, and in the result we arrived at such a solution that the
customizable variable `tab-bar-tab-post-change-group-functions' provides
an option `tab-bar-move-tab-to-group', so that when you select it,
then after changing the group name the tab is moved to its tab group.
next prev parent reply other threads:[~2022-11-30 16:38 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 [this message]
2022-11-30 16:43 ` Mickey Petersen
2022-11-30 17:09 ` Juri Linkov
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=86o7soii72.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).