From: Aaron Jensen <aaronjensen@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 59208@debbugs.gnu.org
Subject: bug#59208: 29.0.50; tab-bar-auto-width plus display space cpu spin
Date: Sat, 12 Nov 2022 11:39:23 -0800 [thread overview]
Message-ID: <CAHyO48x8tK4JdK0FvZXOFqha70h3FWiwNdPWoQ=nQvyJG7_q=g@mail.gmail.com> (raw)
In-Reply-To: <86tu34ko8s.fsf@mail.linkov.net>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Apologies for top posting, on my phone. I should note that my actual tab
function has text as well (the tab name) and then I add a space at the end.
The spaces are just visual padding.
Aaron
On Sat, Nov 12 2022 at 1:33 PM, Juri Linkov <juri@linkov.net> wrote:
> My tab-bar-tab-name-format-function causes 100% cpu spin as of ca3763af5c.
> Disabling tab-bar-auto-width fixes it.
>
> >
>
> To repro: emacs -Q -l repro.el
>
> >
>
> repro.el:
>
> >
>
> (defun aj/tab-bar-tab-name-format (tab i)
> (propertize
> (propertize " " 'display '(space :width (8)))
> 'face (funcall tab-bar-tab-face-function tab)))
>
> >
>
> (setq tab-bar-tab-name-format-function #'aj/tab-bar-tab-name-format)
>
> >
>
> (tab-bar-mode)
>
> Thanks for the bug report. Since with
> (propertize " " 'display '(space :width (8))) the tab width can't grow
> more than 8 pixels,
> a possible fix would be on every iteration
> that adds more spaces to the tab name
> to check if the tab width remains the same.
>
[-- Attachment #2: Type: text/html, Size: 1807 bytes --]
next prev parent reply other threads:[~2022-11-12 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 7:31 bug#59208: 29.0.50; tab-bar-auto-width plus display space cpu spin Aaron Jensen
2022-11-12 18:33 ` Juri Linkov
2022-11-12 19:39 ` Aaron Jensen [this message]
2022-11-13 18:17 ` Juri Linkov
2022-11-13 19:17 ` Aaron Jensen
2022-11-14 7:50 ` Juri Linkov
2022-11-14 14:50 ` Aaron Jensen
2022-11-14 17:28 ` Juri Linkov
2022-11-14 18:11 ` Aaron Jensen
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='CAHyO48x8tK4JdK0FvZXOFqha70h3FWiwNdPWoQ=nQvyJG7_q=g@mail.gmail.com' \
--to=aaronjensen@gmail.com \
--cc=59208@debbugs.gnu.org \
--cc=juri@linkov.net \
/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.