all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Gabriel <gabriel376@hotmail.com>
Cc: 59620@debbugs.gnu.org
Subject: bug#59620: 29.0.50; Wrong global-mode-string position in tab-bar + emacs -nw
Date: Mon, 28 Nov 2022 09:54:17 +0200	[thread overview]
Message-ID: <86h6yjmpm6.fsf@mail.linkov.net> (raw)
In-Reply-To: <SJ0PR06MB8609CC157C0BC043FC9731B08B109@SJ0PR06MB8609.namprd06.prod.outlook.com> (Gabriel's message of "Sun, 27 Nov 2022 05:05:58 -0300")

>> Looks like tab-bar-format-align-right is evaluated with the wrong window
>> being the selected one: it should use the tab-bar pseudo-window to do what
>> you expect.
>
> I don't know what is the root cause, but it's a reasonable hypothesis.
> Not sure why it only affects "emacs -nw", though.
>
> Do you know how to get the tab-bar pseudo-window?  It seems that
> "f->tab_bar_window" it's not exposed from C to elisp.

Unless Eli can suggest how to fix `(space :align-to (- right (,hpos)))
to work on TTY frames the same way as it works on GUI frames,
I could try to rewrite it to avoid the keyword `right', i.e. to use
`(space :align-to (,hpos-from-left)) where hpos-from-left could be
calculated by using string-pixel-width on the text from the left side.





  reply	other threads:[~2022-11-28  7:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26 21:46 bug#59620: 29.0.50; Wrong global-mode-string position in tab-bar + emacs -nw Gabriel
2022-11-27  6:19 ` Eli Zaretskii
2022-11-27  8:05   ` Gabriel
2022-11-28  7:54     ` Juri Linkov [this message]
2022-11-28 12:58       ` Eli Zaretskii
2022-11-28 17:29         ` Juri Linkov
2022-11-28 18:34           ` Eli Zaretskii
2022-12-02  7:59             ` Juri Linkov
2022-12-02 15:01               ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86h6yjmpm6.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=59620@debbugs.gnu.org \
    --cc=gabriel376@hotmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.