unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Theodor Thornhill <theo@thornhill.no>
Cc: 53062@debbugs.gnu.org
Subject: bug#53062: 29.0.50; Inserting charger causes keyboard event <dead-circumflex>
Date: Fri, 07 Jan 2022 08:48:18 +0200	[thread overview]
Message-ID: <838rvs6nyl.fsf@gnu.org> (raw)
In-Reply-To: <87iluw8ri2.fsf@thornhill.no> (bug-gnu-emacs@gnu.org)

> Date: Thu, 06 Jan 2022 22:48:53 +0100
> From:  Theodor Thornhill via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> 
> So, I noticed that everytime I insert my charger the echo area echos
> "dead-circumflex-".  Obviously I:
> 
> (global-set-key (kbd "<dead-circumflex>") 'save-buffers-kill-emacs)
> 
> Now everytime I insert my laptop charger emacs is killed.
> 
> Is this expected?  I pulled and built emacs from source just now, and
> still get that behavior.

Is what expected?  If you bind that function key to
save-buffers-kill-emacs, it is expected that whenever that function
key is "pressed", Emacs will exit, yes.

If you were asking about the dead-circumflex function key event being
generated when you plug your charger, I think it's something that
is local to your system -- some piece of software generates key input
event when you do that.  Emacs just responds to the input events it
receives from the OS.

If you cannot figure out how to disable that "feature", you could
perhaps bind that key to 'ignore', then Emacs will process and ignore
that key.





  reply	other threads:[~2022-01-07  6:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 21:48 bug#53062: 29.0.50; Inserting charger causes keyboard event <dead-circumflex> Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-07  6:48 ` Eli Zaretskii [this message]
2022-01-07  7:27   ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-10 21:20   ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14  8:09     ` Lars Ingebrigtsen
2022-01-14  9:33       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 12:18         ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 12:29           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 12:53             ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 13:06               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 13:12                 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=838rvs6nyl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53062@debbugs.gnu.org \
    --cc=theo@thornhill.no \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).