bug#63988: closed (30.0.50; Recent header line format changes cause spin/seg fault with format-mode-line)

[GNU bug Tracking System]

Your message dated Fri, 23 Jun 2023 13:53:39 +0300
with message-id <83pm5m1mbw.fsf@gnu.org>
and subject line Re: bug#63988: 30.0.50; Recent header line format changes 
cause spin/seg fault with format-mode-line
has caused the debbugs.gnu.org bug report #63988,
regarding 30.0.50; Recent header line format changes cause spin/seg fault with 
format-mode-line
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
63988: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63988
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 30.0.50; Recent header line format changes cause spin/seg fault with format-mode-line
>
>
>
>
> Date: 
>
> Fri, 09 Jun 2023 21:09:45 -0400
>
>
>
>
> (setq header-line-format '(:eval (format-mode-line "")))
>
> This causes Emacs to spin as of commit:
> 4f66cbbfe520ee31ef26676e09a926217d9736fe
>
> After some time, it will segfault.
>
>
> In GNU Emacs 30.0.50 (build 1, aarch64-apple-darwin22.4.0, NS
>  appkit-2299.50 Version 13.3.1 (a) (Build 22E772610a)) of 2023-05-19
>  built on Aarons-Laptop.local
> Windowing system distributor 'Apple', version 10.3.2299
> System Description:  macOS 13.4
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#63988: 30.0.50; Recent header line format changes cause spin/seg fault with format-mode-line
>
>
>
>
> Date: 
>
> Fri, 23 Jun 2023 13:53:39 +0300
>
>
>
>
> > Cc: 63988@debbugs.gnu.org, aaronjensen@gmail.com, monnier@iro.umontreal.ca
> > Date: Thu, 15 Jun 2023 08:59:09 +0300
> > From: Eli Zaretskii <eliz@gnu.org>
> > 
> > It sounds like the consensus here is that indeed this feature is not
> > worth the complications, and so, unless I hear some good reasons not
> > to do so, I intend to delete it in a week's time.
>
> Time's up, so I've now reverted all the commits that dealt with this
> feature, and I'm marking this bug done.
>
>
> --- End Message ---