From: Gabriel <gabriel376@hotmail.com>
To: emacs-devel@gnu.org
Subject: Re: Some minor suggestions to Tab Bar
Date: Wed, 24 Mar 2021 21:47:23 -0300 [thread overview]
Message-ID: <CH2PR01MB5879BE6DCAFAB6F590DB5C4E8B629@CH2PR01MB5879.prod.exchangelabs.com> (raw)
In-Reply-To: <87mtustidk.fsf@mail.linkov.net> (Juri Linkov's message of "Wed, 24 Mar 2021 22:19:03 +0200")
>
> To keep all tabs of the same group next to each other,
> now there is a new option tab-bar-tab-post-change-group-functions
> that can be customized to tab-bar-move-tab-to-group that will move
> the tab after changing its group closer to other tabs of the same
> group.
This is really great! Thank you!
I did some tests and works fine. I have found one edge case,
though. Imagine these tabs, consisting of [hint group name]:
[1 g1 A] [2 g1 B] [3 g1 C] [4 g2 D] [5 g2 E] [6 g2 F]
If we go to tab 2 and unset the group or set a new group (e.g.: "g3"),
the tab will not be moved, which will split the group "g1":
[1 g1 A] [2 g3 B] [3 g1 C] [4 g2 D] [5 g2 E] [6 g2 F]
I suspect that 'tab-bar-move-tab-to-group' fails to find another tab of
the same group to move to a closer position, so it leaves the current
tab where it is, without checking if this creates a misalignment.
next prev parent reply other threads:[~2021-03-25 0:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 22:51 Some minor suggestions to Tab Bar Gabriel
2021-03-15 9:24 ` Juri Linkov
2021-03-15 17:25 ` Juri Linkov
2021-03-17 17:46 ` Juri Linkov
2021-03-17 22:31 ` Ergus
2021-03-18 9:20 ` Juri Linkov
2021-03-19 0:28 ` Gabriel
2021-03-22 11:07 ` Zhiwei Chen
2021-03-22 18:47 ` Juri Linkov
2021-03-23 12:17 ` Zhiwei Chen
2021-03-23 18:30 ` Repeat lambda (was: Some minor suggestions to Tab Bar) Juri Linkov
2021-03-26 6:00 ` Zhiwei Chen
2021-03-29 19:28 ` Repeat lambda Juri Linkov
2021-04-05 21:03 ` Juri Linkov
2021-04-11 23:40 ` Ergus
2021-04-12 2:25 ` Zhiwei Chen
2021-04-12 16:32 ` Juri Linkov
2021-04-13 19:35 ` Juri Linkov
2021-04-13 23:45 ` T.V Raman
2021-04-14 17:51 ` Juri Linkov
2021-04-14 5:37 ` Richard Stallman
2021-04-14 7:18 ` peat lambda Kévin Le Gouguec
2021-04-14 7:59 ` Repeat lambda Kévin Le Gouguec
2021-04-16 5:10 ` peat lambda Richard Stallman
2021-04-14 17:56 ` Repeat lambda Juri Linkov
2021-04-15 5:24 ` Richard Stallman
2021-04-05 21:19 ` Some minor suggestions to Tab Bar Juri Linkov
2021-04-06 3:16 ` Zhiwei Chen
2021-03-24 20:19 ` Juri Linkov
2021-03-25 0:47 ` Gabriel [this message]
2021-03-25 9:31 ` Juri Linkov
2021-03-26 5:52 ` Gabriel
2021-03-29 19:20 ` 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=CH2PR01MB5879BE6DCAFAB6F590DB5C4E8B629@CH2PR01MB5879.prod.exchangelabs.com \
--to=gabriel376@hotmail.com \
--cc=emacs-devel@gnu.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).