From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37667@debbugs.gnu.org
Subject: bug#37667: 27.0.50; Tab Bar display problems with more than 5 tabs
Date: Thu, 17 Oct 2019 01:39:27 +0300 [thread overview]
Message-ID: <87pniwuwj5.fsf@mail.linkov.net> (raw)
In-Reply-To: <83eezceir2.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 16 Oct 2019 19:51:29 +0300")
>> But the first question popped up quickly: I don't understand
>> how to detect the situation where the tab-line is truncated?
>
> The situation that it's truncated, or the situation that it _needs_ to
> be truncated, i.e. the next tab doesn't fit on the line?
>
> If the former, the glyph_row->truncated_on_right_p flag should be set.
> You can see it being set in display_string, which is called from
> display_mode_line.
>
> If you mean the latter, then look how the truncated_on_right_p flag is
> being set in display_line or in other similar display functions, like
> display_tab_bar_line.
>
>> And how to find the tab that is visible partially?
>> Especially when the font is variable-pitch.
>
> I think you will need to walk the glyphs in the tab-line looking for
> the last glyph whose character position has the property you put on
> tabs in tab-line (as specified in by tab-line-format). Or maybe
> tab-line-format should put some special property on the last glyph of
> a tab, so that you could look for it more easily?
>
> Let me know if the above is not detailed enough to get you off the
> ground.
Thanks for the explanation. One thing that I still don't understand is
how to find the exact position in the mode-line string where it's
truncated. For example, in the string "...abc|xyz", the part
until "abc" is visible, but the rest of the string is truncated,
so "xyz" is not visible. How to find this position where truncation occurs?
Actually, it seems I found it, it's it.last_visible_x. Is this correct?
next prev parent reply other threads:[~2019-10-16 22:39 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 18:55 bug#37667: 27.0.50; Tab Bar display problems with more than 5 tabs Eli Zaretskii
2019-10-10 22:25 ` Juri Linkov
2019-10-11 7:16 ` Eli Zaretskii
2019-10-13 22:39 ` Juri Linkov
2019-10-14 7:00 ` Eli Zaretskii
2019-10-14 21:47 ` Juri Linkov
2019-10-15 9:09 ` Eli Zaretskii
2019-10-15 18:07 ` Juri Linkov
2019-10-15 18:46 ` Eli Zaretskii
2019-10-15 19:10 ` Eli Zaretskii
2019-10-15 22:39 ` Juri Linkov
2019-10-16 16:51 ` Eli Zaretskii
2019-10-16 22:39 ` Juri Linkov [this message]
2019-10-17 7:20 ` Eli Zaretskii
2019-10-17 22:34 ` Juri Linkov
2019-10-18 6:57 ` Eli Zaretskii
2019-10-20 22:28 ` Juri Linkov
2019-10-21 7:58 ` Eli Zaretskii
2019-10-21 22:20 ` Juri Linkov
2019-10-22 15:16 ` Eli Zaretskii
2019-10-22 21:19 ` Juri Linkov
2019-10-23 16:10 ` Eli Zaretskii
2019-10-28 22:38 ` Juri Linkov
2019-10-29 12:01 ` Eli Zaretskii
2019-10-30 0:35 ` Juri Linkov
2019-10-30 15:59 ` Eli Zaretskii
2019-10-30 23:59 ` Juri Linkov
2019-10-31 14:25 ` Eli Zaretskii
2019-10-31 0:03 ` Juri Linkov
2019-10-31 14:30 ` Eli Zaretskii
2019-10-31 20:46 ` Juri Linkov
2019-11-01 7:43 ` Eli Zaretskii
2019-11-02 19:06 ` Juri Linkov
2019-11-02 19:28 ` Eli Zaretskii
2019-11-02 22:36 ` Juri Linkov
2019-11-17 21:44 ` Juri Linkov
2019-11-18 16:18 ` Eli Zaretskii
2019-11-18 21:57 ` Juri Linkov
2019-11-19 16:51 ` Eli Zaretskii
2019-11-19 22:25 ` Juri Linkov
2019-11-20 3:45 ` Eli Zaretskii
2019-11-20 22:40 ` Juri Linkov
2019-11-21 8:23 ` martin rudalics
2019-11-21 14:20 ` Eli Zaretskii
2019-11-21 21:56 ` Juri Linkov
2019-11-22 8:16 ` martin rudalics
2019-10-11 8:17 ` martin rudalics
2019-10-13 22:31 ` Juri Linkov
2019-10-14 6:51 ` Eli Zaretskii
2019-10-14 20:07 ` Juri Linkov
2019-10-14 20:22 ` Eli Zaretskii
2019-10-14 21:50 ` Juri Linkov
2019-10-15 6:26 ` Eli Zaretskii
2019-10-15 17:54 ` Juri Linkov
2019-10-16 18:14 ` martin rudalics
2019-10-16 20:58 ` Juri Linkov
2019-10-17 8:25 ` martin rudalics
2020-09-20 11:24 ` Lars Ingebrigtsen
2020-09-20 11:27 ` Eli Zaretskii
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=87pniwuwj5.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=37667@debbugs.gnu.org \
--cc=eliz@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).