From: uzibalqa <uzibalqa@proton.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Making new menu after Tools using keymap-set-after
Date: Wed, 19 Jul 2023 21:00:22 +0000 [thread overview]
Message-ID: <LVOV4pYKWSuKcT1hskvtlNwktOCwJN8xdFV_W8E-jyUiu7Q8EzNlKD-nG7z8Ojg79HgSQIQnPyq1fohbDi6yfV4XImAdxQaAcuE3fkiZ880=@proton.me> (raw)
In-Reply-To: <83ilaf509w.fsf@gnu.org>
------- Original Message -------
On Thursday, July 20th, 2023 at 4:33 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Wed, 19 Jul 2023 15:58:10 +0000
> > From: uzibalqa uzibalqa@proton.me
> >
> > On Wednesday, July 19th, 2023 at 9:10 PM, Robert Pluim rpluim@gmail.com wrote:
> >
> > > > > > > > On Wed, 19 Jul 2023 08:08:32 +0000, uzibalqa uzibalqa@proton.me said:
> > >
> > > uzibalqa> (defvar mcp-kdf (make-sparse-keymap "MCP"))
> > >
> > > uzibalqa> (keymap-set-after global-map
> > >
> > > uzibalqa> "<menu-bar> <mcp-topm>" (cons "MCP" mcp-kdf) 'tools)
> > >
> > > uzibalqa> complains about 'tools
> > >
> > > Works for me in emacs-30, it gives me an 'MCP' menu just after
> > > Tools. What error are you seeing?
> > >
> > > Robert
> > > --
> >
> > With GNU Emacs 29.0.50, I get
> >
> > Debugger entered--Lisp error: (error "tools is not a valid key definition; see ‘key-valid-p’")
>
>
> If this is in "emacs -Q", you probably have a broken snapshot of Emacs
> 29, the above works with the current emacs-29 branch. If "emacs -Q"
> does work, then maybe some of your customizations cause the problem.
Got the function to work by installing emacs-30.0.50.1
next prev parent reply other threads:[~2023-07-19 21:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 16:04 Making new menu after Tools using keymap-set-after uzibalqa
2023-07-18 16:29 ` Eli Zaretskii
2023-07-18 16:56 ` uzibalqa
2023-07-18 17:12 ` Eli Zaretskii
2023-07-18 17:29 ` uzibalqa
2023-07-18 18:28 ` Eli Zaretskii
2023-07-18 18:45 ` uzibalqa
2023-07-18 19:02 ` Eli Zaretskii
2023-07-18 19:26 ` uzibalqa
2023-07-19 2:25 ` Eli Zaretskii
2023-07-19 8:08 ` uzibalqa
2023-07-19 9:10 ` Robert Pluim
2023-07-19 15:58 ` uzibalqa
2023-07-19 16:33 ` Eli Zaretskii
2023-07-19 16:37 ` uzibalqa
2023-07-19 16:44 ` Robert Pluim
2023-07-19 16:54 ` uzibalqa
2023-07-19 17:07 ` Robert Pluim
2023-07-19 17:11 ` uzibalqa
2023-07-19 17:25 ` Platon Pronko
2023-07-19 17:34 ` uzibalqa
2023-07-20 3:17 ` Platon Pronko
2023-07-19 17:28 ` [External] : " Drew Adams
2023-07-19 17:37 ` uzibalqa
2023-07-19 19:00 ` Drew Adams
2023-07-19 19:08 ` uzibalqa
2023-07-20 3:32 ` Platon Pronko
2023-07-20 8:43 ` uzibalqa
2023-07-19 21:00 ` uzibalqa [this message]
2023-07-18 20:42 ` Drew Adams
2023-07-18 20:55 ` uzibalqa
2023-07-18 21:40 ` uzibalqa
2023-07-19 12:11 ` Eli Zaretskii
2023-07-19 11:58 ` Eli Zaretskii
2023-07-19 14:18 ` Drew Adams
2023-07-18 20:49 ` uzibalqa
2023-07-19 12:00 ` Eli Zaretskii
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='LVOV4pYKWSuKcT1hskvtlNwktOCwJN8xdFV_W8E-jyUiu7Q8EzNlKD-nG7z8Ojg79HgSQIQnPyq1fohbDi6yfV4XImAdxQaAcuE3fkiZ880=@proton.me' \
--to=uzibalqa@proton.me \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.
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).