Re: Some minor suggestions to Tab Bar

[Juri Linkov]

> Tab Bar is awesome and the recently added features to work with tab
> groups made it even better. I know it's still a working in progress, but
> I would like to suggest some minor improvements:

Thanks for suggestions.

The current implementation is not yet finished.  It will take
a few days to polish and push remaining patches.

But you are welcome to try it out now and to make suggestions
for improvements.

> 1. Add an initial input for the 'completing-read' of
> 'tab-bar-change-tab-group', so when we type 'C-x t G' to set/unset the
> group name, the minibuffer contents is filled with the current group
> value. A possible downside is that pressing TAB may not show the
> Completions list, in case the current value does not match any item of
> the completion list provided.

Prefilling the initial contents of the minibuffer is deprecated.
This is what the documentation says about it:

     The argument INITIAL is mostly deprecated; we recommend using a
     non-‘nil’ value only in conjunction with specifying a cons cell for
     HISTORY.  For default input, use DEFAULT instead.

> 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

Your suggestions 3, 4, 5 are currently already under construction,
but for the suggestion 2 of adding new faces your help is needed
to design a set of new faces.  This your list could be used as a base
where new faces could be created:

> * [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