From: dal-blazej--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 54656@debbugs.gnu.org
Subject: bug#54656: 29.0.50; [menu] key is not read anymore
Date: Thu, 31 Mar 2022 21:41:56 +0200 [thread overview]
Message-ID: <87r16h9aez.fsf@onenetbeyond.org> (raw)
Hi,
After compiling from master I found my [menu] key not usable anymore
within emacs.
It don't show with C-h c
It show in xev
In GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, cairo version 1.16.0)
of 2022-03-31 built on localhost
Repository revision: 948181df9cbdcc8845fc3662e2007d8e09f48c71
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12011000
System Description: Debian GNU/Linux 11 (bullseye)
Configured using:
'configure --build x86_64-linux-gnu --prefix=/opt/emacs
--with-mailutils --with-sound=yes --without-gconf --without-gsettings
--with-x=yes --without-toolkit-scroll-bars --with-x-toolkit=gtk3
--with-json --with-native-compilation --with-xwidgets
build_alias=x86_64-linux-gnu 'CFLAGS=-O2 -Wall ''
Configured features:
CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS HARFBUZZ JPEG JSON LIBSELINUX
LIBXML2 MODULES NATIVE_COMP NOTIFY INOTIFY PDUMPER PNG SECCOMP SOUND
SQLITE3 THREADS TIFF X11 XDBE XIM XPM XWIDGETS GTK3 ZLIB
Important settings:
value of $LANG: en_US
locale-coding-system: utf-8
Load-path shadows:
/home/user/.emacs.d/elpa/transient-0.3.7/transient hides /opt/emacs/share/emacs/29.0.50/lisp/transient
next reply other threads:[~2022-03-31 19:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 19:41 dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-04-01 1:20 ` bug#54656: 29.0.50; [menu] key is not read anymore Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-01 21:34 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-02 1:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-02 15:51 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-03 0:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-04 0:03 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-04 0:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-04 9:31 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-04 11:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-21 14:18 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-22 0:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-22 13:57 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-23 0:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-24 19:25 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-25 2:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-02 23:39 ` dal-blazej--- 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=87r16h9aez.fsf@onenetbeyond.org \
--to=bug-gnu-emacs@gnu.org \
--cc=54656@debbugs.gnu.org \
--cc=dal-blazej@onenetbeyond.org \
/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).