all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 08:08:32 +0000	[thread overview]
Message-ID: <wmlW7tci6JZjnkPk9P1PNAHNxaS9lt-lbZmt1PF_b0HOpOD4x6MdYnS1OmIiK70PYefDoVn63M9HS5NonxQbFp_j1AyazQECyj_Z2Kva_mk=@proton.me> (raw)
In-Reply-To: <83ilag63ji.fsf@gnu.org>






Sent with Proton Mail secure email.

------- Original Message -------
On Wednesday, July 19th, 2023 at 2:25 PM, Eli Zaretskii <eliz@gnu.org> wrote:


> > Date: Tue, 18 Jul 2023 19:26:01 +0000
> > From: uzibalqa uzibalqa@proton.me
> > Cc: help-gnu-emacs@gnu.org
> > 
> > > If you want examples of how this is done, there are a lot of them in
> > > the Emacs source tree.
> > 
> > Are they using the new 'keymap-set-after' and 'keymap-set' ?
> 
> 
> Many of them do.  

I have seen that 

(defvar mcp-kdf (make-sparse-keymap "MCP"))
(keymap-set-after global-map
   "<menu-bar> <mcp-topm>" (cons "MCP" mcp-kdf) 'tools)

complains about 'tools




  reply	other threads:[~2023-07-19  8:08 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 [this message]
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
2023-07-18 20:42             ` [External] : " 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

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

  git send-email \
    --in-reply-to='wmlW7tci6JZjnkPk9P1PNAHNxaS9lt-lbZmt1PF_b0HOpOD4x6MdYnS1OmIiK70PYefDoVn63M9HS5NonxQbFp_j1AyazQECyj_Z2Kva_mk=@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.
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.