all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 52947@debbugs.gnu.org, dlacewell@gmail.com
Subject: bug#52947: 29.0.50; Newline in tab-bar-format causes lockup
Date: Sun, 02 Jan 2022 20:25:08 +0200	[thread overview]
Message-ID: <83y23yc7wb.fsf@gnu.org> (raw)
In-Reply-To: <86ilv26ndp.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 02 Jan 2022 19:47:14 +0200)

> From: Juri Linkov <juri@linkov.net>
> Date: Sun, 02 Jan 2022 19:47:14 +0200
> Cc: 52947@debbugs.gnu.org
> 
> > #+begin_src emacs-lisp
> >   (defun broken-tab-bar-format ()
> >     (let* ((str (format "%s \n %s"
> >                         "foo" "bar")))
> >       `((global menu-item ,(s-trim str) ignore))))
> 
> This also can be reproduced without s-trim, with just:
> 
>        `((global menu-item ,str ignore))))
> 
> >   (progn
> >     (setq tab-bar-format '(tab-bar-format-align-right
> > broken-tab-bar-format))
> >     (tab-bar-mode 1))
> > #+end_src
> >
> > Emacs will lockup and spin the core it's on.
> 
> If the display engine doesn't support newlines in the
> menu-bar/tool-bar/tab-bar, then we could simply remove newlines
> before feeding the tab-bar items to the display engine.

Do we want to support newlines there? what would be the purpose of
having newlines in the tabs?

Also, you say "display engine", so does it mean you've found where we
infloop with these recipes?  If so, can you tell the details?

Thanks.





  reply	other threads:[~2022-01-02 18:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-02 10:17 bug#52947: 29.0.50; Newline in tab-bar-format causes lockup Dustin Lacewell
2022-01-02 17:47 ` Juri Linkov
2022-01-02 18:25   ` Eli Zaretskii [this message]
2022-01-02 18:38     ` Juri Linkov
2022-01-02 19:38       ` Eli Zaretskii
2022-01-04  7:57         ` 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

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

  git send-email \
    --in-reply-to=83y23yc7wb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=52947@debbugs.gnu.org \
    --cc=dlacewell@gmail.com \
    --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.