all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Samuel Wales <samologist@gmail.com>
Cc: 38802@debbugs.gnu.org
Subject: bug#38802: 24.5; emacs unusable, unpredictably, with "k is undefined" for every key
Date: Wed, 01 Jan 2020 05:32:38 +0200	[thread overview]
Message-ID: <835zhvlull.fsf@gnu.org> (raw)
In-Reply-To: <CAJcAo8sNP2Y5wQk-OuHY1siHOzV86yzjaAXmwE_Vr=EWjhShAw@mail.gmail.com> (message from Samuel Wales on Tue, 31 Dec 2019 15:39:36 -0700)

> From: Samuel Wales <samologist@gmail.com>
> Date: Tue, 31 Dec 2019 15:39:36 -0700
> Cc: 38802@debbugs.gnu.org
> 
> On 12/30/19, Eli Zaretskii <eliz@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.





  reply	other threads:[~2020-01-01  3:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-30  1:20 bug#38802: 24.5; emacs unusable, unpredictably, with "k is undefined" for every key Samuel Wales
2019-12-30 15:45 ` Eli Zaretskii
2019-12-31 22:39   ` Samuel Wales
2020-01-01  3:32     ` Eli Zaretskii [this message]
2020-01-01  0:31   ` Michael Heerdegen
2020-01-01  3:33     ` Eli Zaretskii
2020-01-01  3:38       ` Michael Heerdegen
2020-01-01  5:29         ` Samuel Wales
2020-01-01  5:39           ` Samuel Wales
2020-01-01  5:43             ` Samuel Wales
2020-01-01  5:56               ` Michael Heerdegen
2020-01-05 22:32                 ` Samuel Wales
2020-01-01 15:38             ` Eli Zaretskii
2020-01-05 22:33               ` Samuel Wales
2020-09-22 15:19                 ` Lars Ingebrigtsen
2020-10-26 15:51                   ` Lars Ingebrigtsen
2020-10-26 22:39                   ` Samuel Wales
2020-10-27  7:49                     ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=835zhvlull.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=38802@debbugs.gnu.org \
    --cc=samologist@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.