From: Juri Linkov <juri@linkov.net>
To: Visuwesh <visuweshm@gmail.com>
Cc: 65554@debbugs.gnu.org
Subject: bug#65554: 30.0.50; help-echo string for truncated tab-bar names is not viewable
Date: Mon, 28 Aug 2023 19:57:49 +0300 [thread overview]
Message-ID: <86a5ubcdf6.fsf@mail.linkov.net> (raw)
In-Reply-To: <87msyb2rij.fsf@gmail.com> (Visuwesh's message of "Mon, 28 Aug 2023 19:33:32 +0530")
>> Next I could rename tab-bar-tab-name-format-function to
>> tab-bar-tab-name-format-functions with the default value
>> composed from the code fragments of tab-bar-tab-name-format-default:
>>
>> '(tab-bar-tab-name-format-hints
>> tab-bar-tab-name-format-close-button
>> tab-bar-tab-name-format-face
>> )
>>
>> Then you will be able to customize it to:
>>
>> '(tab-bar-tab-name-format-truncate
>> tab-bar-tab-name-format-hints
>> tab-bar-tab-name-format-close-button
>> tab-bar-tab-name-format-face
>> )
>>
>> That first will truncate the tab name, then add numeric hints to the
>> truncated name, then add the close button, then put faces on the final string
>> that will be displayed on the tab bar.
>
> That would be much more convenient, and make the customisation around
> the tab name a lot less confusing.
Now tab-bar-tab-name-format-functions is pushed to master.
Please try to customize it and add tab-bar-tab-name-format-truncated
to the top of the list.
PS: I think no functions/defcustoms should be obsoleted with this change.
next prev parent reply other threads:[~2023-08-28 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 19:17 bug#65554: 30.0.50; help-echo string for truncated tab-bar names is not viewable Visuwesh
2023-08-27 16:11 ` Juri Linkov
2023-08-27 16:30 ` Visuwesh
2023-08-27 16:55 ` Juri Linkov
2023-08-28 6:53 ` Juri Linkov
2023-08-28 14:03 ` Visuwesh
2023-08-28 16:57 ` Juri Linkov [this message]
2023-08-31 4:50 ` Visuwesh
2023-08-31 6:40 ` 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=86a5ubcdf6.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=65554@debbugs.gnu.org \
--cc=visuweshm@gmail.com \
/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).