[debbugs-tracker] bug#32038: closed (27.0.50; Emacs hangs when using :propertize mode line construct and not providing a property value)

[GNU bug Tracking System]

Your message dated Sat, 14 Jul 2018 14:30:04 +0300
with message-id <address@hidden>
and subject line Re: bug#32038: 27.0.50; Emacs hangs when using :propertize 
mode line construct and not providing a property value
has caused the debbugs.gnu.org bug report #32038,
regarding 27.0.50; Emacs hangs when using :propertize mode line construct and 
not providing a property value
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
32038: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=32038
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 27.0.50; Emacs hangs when using :propertize mode line construct and not providing a property value
>
>
>
>
> Date: 
>
> Mon, 2 Jul 2018 18:15:20 +0200
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
>
>
>
>
> When I evaluate this, Emacs becomes unresponsive and keeps
> consuming 100% of my cpu:
>
> (progn
>   (setq mode-line-format '(:propertize "a" face))
>   (force-mode-line-update))
>
> Repository revision: ee3e432300054ca488896e39fca57b10d733330a
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#32038: 27.0.50; Emacs hangs when using :propertize mode line construct and not providing a property value
>
>
>
>
> Date: 
>
> Sat, 14 Jul 2018 14:30:04 +0300
>
>
>
>
> > From: Jonathan Kyle Mitchell <address@hidden>
> > Cc: address@hidden, address@hidden
> > Date: Wed, 04 Jul 2018 23:14:01 -0500
> > 
> > That makes sense. I added one function to call Fset_text_properties
> > through internal_condition_case_n in the attached revised patch. The
> > error gets caught and safe_eval_handler appends an error message to the
> > *Messages* buffer.
> > 
> > The error message is put in *Messages* on the first time only though,
> > subsequent (force-mode-line-update) calls just append nil. I don't know
> > if that's expected for redisplay's internal messaging routines.
> > 
> > Thanks for reviewing the patch.
>
> Thanks, I pushed this to the master branch, and I'm marking the bug
> done.
>
> > From 621bc3df19eaf2258c9a2ec0c72004ea8336ce0f Mon Sep 17 00:00:00 2001
> > From: Jonathan Kyle Mitchell <address@hidden>
> > Date: Wed, 4 Jul 2018 22:38:29 -0500
> > Subject: [PATCH] Call Fset_text_properties through internal_condition_case_n
> > 
> > * xdisp.c (display_mode_element, safe_set_text_properties):
>
> The header line and the log message are sub-optimal/incomplete, and
> don't mention the bug number.  Please see how I fixed that in the
> actual commit, and try following this example in the future.
>
>
> --- End Message ---