unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: Juri Linkov <juri@linkov.net>
Cc: Gabriel <gabriel376@hotmail.com>, emacs-devel@gnu.org
Subject: Re: Some minor suggestions to Tab Bar
Date: Wed, 17 Mar 2021 23:31:42 +0100	[thread overview]
Message-ID: <20210317223142.2xx5fb5ofu6iyumm@Ergus> (raw)
In-Reply-To: <87o8fhekvx.fsf@mail.linkov.net>

Hi Juri:

Just a question. I have seen the new groups in tabs-bar, but I sadly
don't understand what a group means and how to use this feature as a
final user.

I evaluated:

(setq tab-bar-format
       '(tab-bar-format-history
	tab-bar-format-tabs-group
	tab-bar-separator
	tab-bar-format-add-tab))

And just a + appears in the tab-bar. So maybe you could explain some
basic steps about how to use the groups?

Best,
Ergus.


On Wed, Mar 17, 2021 at 07:46:30PM +0200, Juri Linkov wrote:
>> 2. Add new faces for group tabs. The idea is to differentiate these 2
>> cases:
>>   2.1. Tabs from the current group X tabs from other groups
>>   2.2. Regular tabs X collapsed group tabs
>>
>> It's not possible to know which tabs belongs to the current group or
>> which tabs represent another group, since all inactive tabs use the same
>> face 'tab-bar-tab-inactive'. I did a slight modification to
>> 'tab-bar-tab-name-format-default' and 'tab-bar-tab-group-format-default'
>> to add two new faces:
>>
>> In the example above (please desconsider the styles I used), we can see
>> that:
>>   * [1], [2] and [8] are tabs that do not belong to any group (ungrouped)
>>   * [3] is a collapsed group tab of a group named "group1", where tab
>>     [4] belongs to the same group and is hidden
>>   * [5] and [7] are tabs that belongs to the current group (same group)
>>   * [6] is the current active tab
>
>As a first stab at tab faces, now there are 3 new faces:
>
>- tab-bar-tab-group-current
>- tab-bar-tab-group-inactive
>- tab-bar-tab-ungrouped
>
>and two new options:
>
>- tab-bar-tab-face-function
>- tab-bar-tab-group-face-function
>
>The latter can be used for color-coding, e.g. by assigning a distinctive
>color to each group of tabs.
>
>I'm striving to make only minimal changes in the core library
>and to provide enough knobs for easy customization.
>
>Please try this to see if there is still anything missing.
>



  reply	other threads:[~2021-03-17 22:31 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 [this message]
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
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=20210317223142.2xx5fb5ofu6iyumm@Ergus \
    --to=spacibba@aol.com \
    --cc=emacs-devel@gnu.org \
    --cc=gabriel376@hotmail.com \
    --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).