GNU bug report logs - #38802
24.5; emacs unusable, unpredictably, with "k is undefined" for every key

Previous Next

To reply to this bug, email your comments to 38802 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Samuel Wales <samologist <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.5;
 emacs unusable, unpredictably, with "k is undefined" for every key
Date: Sun, 29 Dec 2019 18:20:15 -0700

To: bug-gnu-emacs <at> gnu.org
Subject: 24.5; emacs unusable in minibuffer, unpredictably, with "k is
undefined" for every key
--text follows this line--
I have long had a bug where everything I type says "k is undefined",
where k stands for any key including ESC and C-g.  this occurs
randomly.

It is impossible to get out of this mode, unless you can figure out
some SIGUSR1 voodoo.  Except once, I think type-break activating got
me out of the mode.  And once I got
out by just coming back to it after a half hour or something.

I suspect maybe type-break also causes the bug, if certain conditions
obtain.  I am not sure.  But it is the only timer-based thing I can
think of.

I believe it occurs when I am in the minibuffer.  Perhaps only at a
password prompt.

I don't know if this bug report is useful.

Thanks.

In GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.11)
 of 2017-09-12 on hullmann, modified by Debian
Windowing system distributor `The X.Org Foundation', version 11.0.11902000
System Description:	Debian GNU/Linux 9.11 (stretch)

Message #8 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Samuel Wales <samologist <at> gmail.com>
Cc: 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5;
 emacs unusable, unpredictably, with "k is undefined" for every key
Date: Mon, 30 Dec 2019 17:45:37 +0200

> From: Samuel Wales <samologist <at> gmail.com>
> Date: Sun, 29 Dec 2019 18:20:15 -0700
> 
> I have long had a bug where everything I type says "k is undefined",
> where k stands for any key including ESC and C-g.  this occurs
> randomly.
> 
> It is impossible to get out of this mode, unless you can figure out
> some SIGUSR1 voodoo.  Except once, I think type-break activating got
> me out of the mode.  And once I got
> out by just coming back to it after a half hour or something.

Can you show a screenshot of how your Emacs session looks when this
happens?

Message #11 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Samuel Wales <samologist <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Tue, 31 Dec 2019 15:39:36 -0700

On 12/30/19, Eli Zaretskii <eliz <at> gnu.org> wrote:
> Can you show a screenshot of how your Emacs session looks when this
> happens?

it is quite infrequent.  basically, last time, the screen showed the
buffer, password prompt in minibuffer, and then whenever you type any
key, it says that key is undefined.

-- 
The Kafka Pandemic

What is misopathy?
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

Message #14 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Samuel Wales <samologist <at> gmail.com>, 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Wed, 01 Jan 2020 01:31:01 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

> Can you show a screenshot of how your Emacs session looks when this
> happens?

Dunno if it's related, but I sometimes saw something similar when I had
been kicked out of an y-or-n-p prompt somehow, AFAIR.  But I'm currently
not able to provoke something like this.

Michael.

Message #17 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Samuel Wales <samologist <at> gmail.com>
Cc: 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Wed, 01 Jan 2020 05:32:38 +0200

> From: Samuel Wales <samologist <at> gmail.com>
> Date: Tue, 31 Dec 2019 15:39:36 -0700
> Cc: 38802 <at> debbugs.gnu.org
> 
> On 12/30/19, Eli Zaretskii <eliz <at> gnu.org> wrote:
> > Can you show a screenshot of how your Emacs session looks when this
> > happens?
> 
> it is quite infrequent.  basically, last time, the screen showed the
> buffer, password prompt in minibuffer, and then whenever you type any
> key, it says that key is undefined.

Please post a screenshot next time it happens.

Message #20 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: samologist <at> gmail.com, 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Wed, 01 Jan 2020 05:33:18 +0200

> From: Michael Heerdegen <michael_heerdegen <at> web.de>
> Cc: Samuel Wales <samologist <at> gmail.com>,  38802 <at> debbugs.gnu.org
> Date: Wed, 01 Jan 2020 01:31:01 +0100
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Can you show a screenshot of how your Emacs session looks when this
> > happens?
> 
> Dunno if it's related, but I sometimes saw something similar when I had
> been kicked out of an y-or-n-p prompt somehow, AFAIR.  But I'm currently
> not able to provoke something like this.

You are saying that sometimes y-or-n-p doesn't react to C-g?

Message #23 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: samologist <at> gmail.com, 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Wed, 01 Jan 2020 04:38:42 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

> You are saying that sometimes y-or-n-p doesn't react to C-g?

No, when that happens, the y-or-n-p prompt is gone.  Everything looks
like normal top level, but all keys are "undefined" (maybe all except
"y" and "n"?).

I can't be more specific, haven't seen the problem for a long time now.
AFAIR that happened when I somehow stepped out of the prompt, e.g. by
forcing Emacs into debugger, or using Edebug.  I don't recall exactly,
and maybe it is unrelated, but there are similarities to what the OP
described.  Too bad I currently can't reproduce the issue I mean.  I
think the OP can be of more help.

Michael.

Message #26 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Samuel Wales <samologist <at> gmail.com>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Tue, 31 Dec 2019 22:29:57 -0700

i'd be delighted to be of more help.  however, besides posting a
screenshot next time it occurs [which is infrequent enough that it
could be /quite/ a long time], what would you suggest i do to be of
more help?

i have no idea why you said that.  i thought it could be useful to
somebody to post the bug report, in case it jogs somebody's memory of
code interaction, although there wasn't much to it.  i don't want to
regret doing so.

Message #29 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Samuel Wales <samologist <at> gmail.com>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Tue, 31 Dec 2019 22:39:37 -0700

i will try to post a screenshot next time.  it could be quite a long time.

i think i forgot to mention that the password prompt, in the most
recent instance, was triggered by shell mode.

any suggestions of what to put in for a sigusr1 or sigusr2  would be
interesting.  i could put debug there maybe.  or find out what modes
are active, or the values of hooks.

Message #32 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Samuel Wales <samologist <at> gmail.com>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Tue, 31 Dec 2019 22:43:11 -0700

i think i misunderstood "can be of more help" to mean "is not helping"
instead of "can be of more help than me".  i get it now :).

although there are few things i can do.  :)

Message #35 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Samuel Wales <samologist <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Wed, 01 Jan 2020 06:56:28 +0100

Samuel Wales <samologist <at> gmail.com> writes:

> i think i misunderstood "can be of more help" to mean "is not helping"
> instead of "can be of more help than me".  i get it now :).

Indeed - and I'm very sorry for the unintentional insult :-(  I guess I
really have to improve my English until something really bad happens one
day...

Michael.

Message #38 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Samuel Wales <samologist <at> gmail.com>
Cc: michael_heerdegen <at> web.de, 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Wed, 01 Jan 2020 17:38:02 +0200

> From: Samuel Wales <samologist <at> gmail.com>
> Date: Tue, 31 Dec 2019 22:39:37 -0700
> Cc: Eli Zaretskii <eliz <at> gnu.org>, 38802 <at> debbugs.gnu.org
> 
> i will try to post a screenshot next time.  it could be quite a long time.

That's OK.  If this problem happens to others, they might come up with
data sooner; if not, it means the problem is rare enough for it not to
be urgent.

Btw, if you can afford that, I'd suggest to upgrade to a newer version
of Emacs, because perhaps this problem was already solved.  The
current version is 26.3, and 27.1 will start its pretest soon.

> any suggestions of what to put in for a sigusr1 or sigusr2  would be
> interesting.

I'd suggest to use debug-on-event.  You can read about it in the ELisp
manual, node "Error Debugging".

Message #41 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Samuel Wales <samologist <at> gmail.com>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Sun, 5 Jan 2020 15:32:04 -0700

your english is very good and your politeness impeccable.

Message #44 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Samuel Wales <samologist <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: michael_heerdegen <at> web.de, 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Sun, 5 Jan 2020 15:33:49 -0700

it is quite rare, but has been around for many emacs versions.

i could test my intuition that it might be related to type-break by
setting type-break to trigger frequently, then running passwd in the
shell, but i don't have it in me atm.

Message #47 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Samuel Wales <samologist <at> gmail.com>
Cc: michael_heerdegen <at> web.de, Eli Zaretskii <eliz <at> gnu.org>,
 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Tue, 22 Sep 2020 17:19:27 +0200

Samuel Wales <samologist <at> gmail.com> writes:

> it is quite rare, but has been around for many emacs versions.
>
> i could test my intuition that it might be related to type-break by
> setting type-break to trigger frequently, then running passwd in the
> shell, but i don't have it in me atm.

This was some months ago.  Have you seen this problem again?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #50 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Samuel Wales <samologist <at> gmail.com>
Cc: michael_heerdegen <at> web.de, Eli Zaretskii <eliz <at> gnu.org>,
 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Mon, 26 Oct 2020 16:51:20 +0100

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> Samuel Wales <samologist <at> gmail.com> writes:
>
>> it is quite rare, but has been around for many emacs versions.
>>
>> i could test my intuition that it might be related to type-break by
>> setting type-break to trigger frequently, then running passwd in the
>> shell, but i don't have it in me atm.
>
> This was some months ago.  Have you seen this problem again?

More information was requested one month ago, but was not given, so
I'm closing this bug report.  If further progress can be made here,
please respond to the debbugs address and we'll reopen.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #55 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Samuel Wales <samologist <at> gmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: michael_heerdegen <at> web.de, Eli Zaretskii <eliz <at> gnu.org>,
 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Mon, 26 Oct 2020 15:39:58 -0700

have not seen it since last time.  it is pretty rare.

if you are in the middle of some critical irc conversation, have a lot
of unsaved buffers, etc.  it can feel like you've been denied the
source and life of all computing -- emacs.

if it needs closing, then whatever is appropriate.

for health reason i am limited in computer use.

On 9/22/20, Lars Ingebrigtsen <larsi <at> gnus.org> wrote:
> Samuel Wales <samologist <at> gmail.com> writes:
>
>> it is quite rare, but has been around for many emacs versions.
>>
>> i could test my intuition that it might be related to type-break by
>> setting type-break to trigger frequently, then running passwd in the
>> shell, but i don't have it in me atm.
>
> This was some months ago.  Have you seen this problem again?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no
>


-- 
The Kafka Pandemic

Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html

Message #58 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Samuel Wales <samologist <at> gmail.com>
Cc: michael_heerdegen <at> web.de, Eli Zaretskii <eliz <at> gnu.org>,
 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: 24.5; emacs unusable, unpredictably, with "k is
 undefined" for every key
Date: Tue, 27 Oct 2020 08:49:58 +0100

Samuel Wales <samologist <at> gmail.com> writes:

> have not seen it since last time.  it is pretty rare.
>
> if you are in the middle of some critical irc conversation, have a lot
> of unsaved buffers, etc.  it can feel like you've been denied the
> source and life of all computing -- emacs.
>
> if it needs closing, then whatever is appropriate.

OK, it doesn't sound likely that we'll make further progress in this bug
report, so I'm closing it.  If you come up with a recipe for reproducing
the bug, please respond to the debbugs address and we'll reopen.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #67 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Samuel Wales <samologist <at> gmail.com>
To: 38802 <at> debbugs.gnu.org
Subject: new data
Date: Sat, 13 Aug 2022 21:03:07 -0700

this bug is infrequent, but of course the possible loss of data and
opportunity cost is there.

new data consistent with my suspicion that type-break + password-type
prompt can cause the bug and also can fix it:

here is a case of type-break probably causing and then fixing the bug
around the time of a password-type prompt:

n is undefined
ding nil
n is undefined
ding nil
a is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
<f6> is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
C-g is undefined
ding nil
ESC is undefined
ding nil
ESC is undefined
ding nil
ESC is undefined
ding nil
ESC is undefined
ding nil
ESC is undefined
ding nil
ESC is undefined
ding nil
ESC is undefined
ding nil
ESC is undefined
ding nil
ESC is undefined
ding nil
ESC is undefined
ding nil
ESC is undefined
ding nil [2 times]
[20:37] Take a break from typing now? (y or n) y
Press any key to resume from typing break.
[20:38] You really ought to rest 14 minutes more.  Continue break? (y or n) n

it seems possible type-break activated at prompt, although i don't
remember what it could have done as i don't have it issue warnings.
it then fixed the bug by prompting me.  i likely said y, then n n.

it seems possible that it would also fix if you did nothing until
type-break prompted.  thanks all.


p.s.  incidentally, although i did not open a new bug yet, there is a
bug in type-break in which it prompts via minibuffer if it /started/
when you were using minibuffer, otherwise dialog box.  it should be
the time of asking, not starting.



-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com

Message #70 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Samuel Wales <samologist <at> gmail.com>
Cc: 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: new data
Date: Mon, 15 Aug 2022 08:52:35 +0200

Samuel Wales <samologist <at> gmail.com> writes:

> [20:37] Take a break from typing now? (y or n) y
> Press any key to resume from typing break.
> [20:38] You really ought to rest 14 minutes more.  Continue break? (y or n) n
>
> it seems possible type-break activated at prompt, although i don't
> remember what it could have done as i don't have it issue warnings.
> it then fixed the bug by prompting me.  i likely said y, then n n.
>
> it seems possible that it would also fix if you did nothing until
> type-break prompted.  thanks all.

Sorry; I don't understand what you mean here.  Can you rephrase?

Message #73 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Samuel Wales <samologist <at> gmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: new data
Date: Mon, 15 Aug 2022 15:57:16 -0700

i am limited in computer use so i hope this helps.

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

then, fortune intervened.  type-break prompted for whatever reason.  i
interacted with the type-break prompt.

note that i was ABLE to interact with it.  it had magical bug-evading
powers.  nothing else in emacs that i know of does.

e.g. it was not in a state where self-insert-command was undefined
when i interacted with it.

i indicated to type-break to not continue the break.  it complied.

then emacs operated normally.  that is the best i can do to try to rephrase.

idk if type-break tried to issue a first prompt.  but my guess is that
the temporally nearby combination of password entry state and an
action that type-break took [e.g. issuing a prompt or perhaps trying
to do so] caused the bug.

[never mind the stuff about type-break warnings.  i was trying to
speculate why there would be no indication of what type-break did in
the messags buffer but that speculation doesn't really make sense so
you can ignore it.]


On 8/14/22, Lars Ingebrigtsen <larsi <at> gnus.org> wrote:
> Samuel Wales <samologist <at> gmail.com> writes:
>
>> [20:37] Take a break from typing now? (y or n) y
>> Press any key to resume from typing break.
>> [20:38] You really ought to rest 14 minutes more.  Continue break? (y or
>> n) n
>>
>> it seems possible type-break activated at prompt, although i don't
>> remember what it could have done as i don't have it issue warnings.
>> it then fixed the bug by prompting me.  i likely said y, then n n.
>>
>> it seems possible that it would also fix if you did nothing until
>> type-break prompted.  thanks all.
>
> Sorry; I don't understand what you mean here.  Can you rephrase?
>
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com

Message #76 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Samuel Wales <samologist <at> gmail.com>
Cc: 38802 <at> debbugs.gnu.org
Subject: Re: bug#38802: new data
Date: Wed, 17 Aug 2022 12:57:36 +0200

Samuel Wales <samologist <at> 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?

Message #79 received at 38802 <at> debbugs.gnu.org (full text, mbox):

From: Samuel Wales <samologist <at> gmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 38802 <at> debbugs.gnu.org
Subject: Re: 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 <at> gnus.org> wrote:
> Samuel Wales <samologist <at> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.