[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#38802: new data
From: |
Samuel Wales |
Subject: |
bug#38802: new data |
Date: |
Wed, 17 Aug 2022 19:19:27 -0700 |
hi lars,
yes, that seems to be the case here.
type-break fixing itself like this is very rare. usually nothing
works at the time. always the impudent message.
^g fails along with ALL keys that i am aware of. technically i would
not call it a hang of emacs. however, emacs is completely
inaccessible. [except perhaps for its sigusr1/sigusr2 stuff? i have
no evidence of that and brain cannot put together code that i know
will be useful. and possibly except for some very long timeout that
could hypothetically get type-break to fix itself after your
deadline.]
On 8/17/22, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Samuel Wales <samologist@gmail.com> writes:
>
>> sequence:
>>
>> - i ran a command in shell mode
>> - that command issued a password prompt
>> - that prompt was recognized by comint-password-prompt-regexp
>> - it appeared in minibuffer
>>
>> i surmise that type-break did something around that time due to its
>> keystroke or time count, causing bug. to continue:
>>
>> - i flailed around not wanting to lose data or state
>> - keypresses not recognized
>> - this is the usual bug state
>> - message buffer shows all this for you
>
> Ah, thanks -- so you were entering a password, and the type-break.el
> stuff triggered, and that made Emacs hang? `C-g' or anything didn't
> work?
>
>
>
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com