all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mickey Petersen <mickey@masteringemacs.org>
To: Juri Linkov <juri@linkov.net>
Cc: 59721@debbugs.gnu.org
Subject: bug#59721: 30.0.50; tab bar groups are not ordered properly
Date: Wed, 30 Nov 2022 18:41:48 +0000	[thread overview]
Message-ID: <87wn7cz3kx.fsf@masteringemacs.org> (raw)
In-Reply-To: <86pmd4fjxh.fsf@mail.linkov.net>


Juri Linkov <juri@linkov.net> writes:

>> 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.
>

Good stuff. Thanks, Juri.

>> 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.

I feel it's what people expect to happen -- what do you think?





  reply	other threads:[~2022-11-30 18:41 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
2022-11-30 18:41       ` Mickey Petersen [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wn7cz3kx.fsf@masteringemacs.org \
    --to=mickey@masteringemacs.org \
    --cc=59721@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.