GNU bug report logs -
#36083
26.2; Bell every 10 seconds with message "<noname> is undefined"
Previous Next
Reported by: Rick McCarty <rjmccarty <at> live.com>
Date: Tue, 4 Jun 2019 00:24:02 UTC
Severity: normal
Found in version 26.2
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Hi Eli,
Thanks! You were correct. I found I also had to disable the modifier key combinations as well, so I did:
(define-key global-map [noname] 'ignore)
(define-key global-map [C-noname] 'ignore)
(define-key global-map [M-noname] 'ignore)
Your input that I should have reported this earlier is well taken - then perhaps Emacs could have been updated long ago to simply ignore these nonname pseudo keys by default or a workaround documented.
Again, thanks for reaching back out to me on this!
Best regards,
Rick
Rick McCarty
rjmccarty <at> live.com
________________________________
From: Eli Zaretskii <eliz <at> gnu.org>
Sent: Tuesday, June 4, 2019 9:13 AM
To: Rick McCarty
Cc: 36083 <at> debbugs.gnu.org
Subject: Re: bug#36083: 26.2; Bell every 10 seconds with message "<noname> is undefined"
> From: Rick McCarty <rjmccarty <at> live.com>
> Date: Tue, 4 Jun 2019 00:18:28 +0000
>
> In a new install of Windows 10, every 10 seconds the bell rings in Emacs, and the message "<noname> is
> undefined" is printed. It only happens when focus is on the Emacs window. This makes Emacs completely
> unusable.
This is produced if Emacs receives the 'noname' (VK_NONAME) pseudo-key
key-press event from Windows. It sounds like DishAnywhere and
SlingPlayer are sending these pseudo-keys to make sure the system
doesn't go to sleep when these applications are active.
Does typing the below inside Emacs make the problem go away?
M-: (define-key global-map [noname] 'ignore) RET
> This is not a new thing - I have seen it before on Vista, Win 7, and another Windows 10 system. I've never
> been able to figure out what is going on - instead I've just installed XEmacs and used that.
If you see this since Vista, it would mean you are aware of the
problem for at least 10 years, maybe longer. I can only say it's a
pity you didn't report this earlier. Please in the future try to
report problems with smaller delays, thanks in advance.
[Message part 2 (text/html, inline)]
This bug report was last modified 5 years and 350 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.