From: Juri Linkov <juri@linkov.net>
To: Gregor Zattler <grfz@gmx.de>
Cc: 38693@debbugs.gnu.org
Subject: bug#38693: 27.0.50; tab-bar: automatic tab names should be shortened
Date: Mon, 20 Jan 2020 02:36:51 +0200 [thread overview]
Message-ID: <87blqzklp8.fsf@mail.linkov.net> (raw)
In-Reply-To: <87a77ghyf0.fsf@mail.linkov.net> (Juri Linkov's message of "Wed, 25 Dec 2019 23:45:39 +0200")
>>>> Please provide an option to dynamically shorten at least
>>>> automatic tab labels in order not to overflow the tab bar into
>>>> another line OR provide an option with sensible default for the
>>>> max length of automatic tab labels (e.g. 23 characters per tab
>>>> label would allow for at least 3 tabs on a 80 char terminal) OR
>>>> something to such effect.
>>>
>>> Maybe such a new option:
>>>
>>> (defcustom tab-bar-tab-name-max 23
>>>
>>> and using it on the default values of tab-bar-tab-name-current,
>>> tab-bar-tab-name-current-with-count, tab-bar-tab-name-all?
>>
>> yes, this would be helpful for me.
>
> I'm still not sure whether to use the new option in all functions above,
> or add a new function that truncates the name. It seems the latter is
> better:
>
> +(defcustom tab-bar-tab-name-truncated-max 20
> + "Maximum length of the tab name from the current buffer.
> +Effective when `tab-bar-tab-name-function' is customized
> +to `tab-bar-tab-name-truncated'."
> + :type 'integer
> + :group 'tab-bar
> + :version "27.1")
The same option should be added also to tab-line to truncate tab-line
tab names. Currently I fixed a bug that occurred when a tab name
was longer than window width. With such an option set to some reasonable
default value this situation won't happen.
next prev parent reply other threads:[~2020-01-20 0:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 17:48 bug#38693: 27.0.50; tab-bar: automatic tab names should be shortened Gregor Zattler
2019-12-21 23:36 ` Juri Linkov
2019-12-23 20:15 ` Gregor Zattler
2019-12-25 21:45 ` Juri Linkov
2020-01-20 0:36 ` Juri Linkov [this message]
2020-01-20 23:03 ` 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=87blqzklp8.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=38693@debbugs.gnu.org \
--cc=grfz@gmx.de \
/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).