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

Previous Next

Full log

View this message in rfc822 format

From: Samuel Wales <samologist <at> gmail.com>
To: 38802 <at> debbugs.gnu.org
Subject: bug#38802: 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

Previous Next

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