[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34623: 25.3; infinite un-quittable loop somwhere under redisplay_win
From: |
Lars Ingebrigtsen |
Subject: |
bug#34623: 25.3; infinite un-quittable loop somwhere under redisplay_window() |
Date: |
Wed, 25 Sep 2019 16:46:08 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
>> So, I am able to reproduce the hang easily (by repeating the narrowing
>> and doing a replace in the narrowed region, with the key bit being that
>> it must be done in a Wanderlust draft message buffer, which is heavily
>> fontified, though the narrowed region is not), and indeed SIGUSR2 pops
>> up a debugger window exactly as hoped:
>>
>> Debugger entered--entering a function:
>> * put-text-property(2875 2876 fontified nil)
>> jit-lock-fontify-now(2850 3350)
>> jit-lock-function(2850)
>> redisplay_internal\ \(C\ function\)()
>
> Is this still Emacs 25.3?
>
>> And with all the frames expanded I see the reason C-g has no effect:
>
> Not sure I understand that reason. Can you spell it out for me?
>
>> Debugger entered--entering a function:
>> * put-text-property(2875 2876 fontified nil)
>> debugger-may-continue = nil
>> inhibit-redisplay = nil
>> inhibit-debugger = t
>> inhibit-changing-match-data = nil
More information was requested, but no response was given within a few
months, so I'm closing this bug report. If the problem still exists,
please reopen this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#34623: 25.3; infinite un-quittable loop somwhere under redisplay_window(),
Lars Ingebrigtsen <=