From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Making new menu after Tools using keymap-set-after
Date: Tue, 18 Jul 2023 22:02:07 +0300 [thread overview]
Message-ID: <83jzux59hs.fsf@gnu.org> (raw)
In-Reply-To: <5CJ7IA6FUfpae6IJLkriZ9erzWkJP7y-GsJUYNBD1MXDgZG2q6Ho1gAxhmD_yf1fDZ9Ycw520lPskK17X77xwjM3n_VruWHV6kP7owNkWEo=@proton.me> (message from uzibalqa on Tue, 18 Jul 2023 18:45:15 +0000)
> Date: Tue, 18 Jul 2023 18:45:15 +0000
> From: uzibalqa <uzibalqa@proton.me>
> Cc: help-gnu-emacs@gnu.org
>
> > I don't know how many lines of code is that, because I don't know what
> > you want to do. And please don't expect me to "help" you by writing
> > your code instead of yourself.
>
> I knew I was right about this. You are not willing to write the code needed to
> make a new menu that I can use. You want me to bugger off and figure it out.
No, I want you to learn how to use the available documentation, and
also how to define a menu. You will never learn if people write the
code for you.
If you want examples of how this is done, there are a lot of them in
the Emacs source tree.
next prev parent reply other threads:[~2023-07-18 19:02 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 [this message]
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
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
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=83jzux59hs.fsf@gnu.org \
--to=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).