From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 24774@debbugs.gnu.org
Subject: bug#24774: 26.0.50; Menu display navigation commands
Date: Wed, 18 Nov 2020 15:16:04 -0800 (PST) [thread overview]
Message-ID: <411796bc-6901-4d3a-b1f5-cc220169803d@default> (raw)
In-Reply-To: <CADwFkmnaa2qqT4fSZLBNRrLz48PsvkpPjpk0usT_gY0sQP9X4g@mail.gmail.com>
> >> So rewriting the emacs-lisp menus using easymenu should be
> >> uncontroversial.
> >
> > Really? _Why_ rewrite them?
>
> They would be easier to read, understand and change.
Easier for whom?
I don't find maintenance easier with easy-menu. I find
it harder. Of course my "maintenance" of existing Emacs
menus means adding to, or otherwise changing, them.
(How do you do the equivalent of a `define-key-after',
for example? Oh, or is there no equivalent?)
next prev parent reply other threads:[~2020-11-18 23:16 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 16:28 bug#24774: 26.0.50; Menu display navigation commands Andreas Röhler
2019-07-27 13:18 ` Lars Ingebrigtsen
2019-07-30 7:54 ` Andreas Röhler
2019-07-30 10:25 ` Lars Ingebrigtsen
2020-11-18 15:34 ` Stefan Kangas
2020-11-18 21:09 ` Lars Ingebrigtsen
2020-11-18 22:01 ` Drew Adams
2020-11-18 22:16 ` Stefan Kangas
2020-11-18 23:16 ` Drew Adams [this message]
2020-11-19 1:10 ` Stefan Kangas
2021-02-23 15:19 ` Stefan Kangas
2021-02-23 15:29 ` Lars Ingebrigtsen
2021-02-23 15:57 ` Eli Zaretskii
2021-02-23 16:02 ` Lars Ingebrigtsen
2021-02-23 16:14 ` Lars Ingebrigtsen
2021-02-23 16:16 ` Eli Zaretskii
2021-02-23 16:37 ` Stefan Kangas
2021-02-23 16:44 ` Eli Zaretskii
2021-02-25 1:25 ` Stefan Kangas
2021-02-25 9:04 ` Stephen Berman
2021-02-25 9:24 ` Eli Zaretskii
2021-02-25 15:09 ` Lars Ingebrigtsen
2021-02-25 15:27 ` Eli Zaretskii
2021-02-25 15:52 ` Lars Ingebrigtsen
2021-02-25 18:18 ` Eli Zaretskii
2021-02-25 19:20 ` Eli Zaretskii
2021-02-26 8:48 ` Lars Ingebrigtsen
2021-02-26 12:04 ` Eli Zaretskii
2021-02-26 12:07 ` Lars Ingebrigtsen
2021-02-26 12:27 ` Eli Zaretskii
2021-02-27 4:30 ` Lars Ingebrigtsen
2021-02-27 5:27 ` Lars Ingebrigtsen
2021-02-27 6:14 ` bug#24774: [External] : " Drew Adams
2021-02-27 7:43 ` Eli Zaretskii
2021-02-27 11:50 ` Lars Ingebrigtsen
2021-02-27 12:56 ` Eli Zaretskii
2021-02-27 13:25 ` Lars Ingebrigtsen
2021-02-27 13:32 ` Eli Zaretskii
2021-02-27 13:49 ` Lars Ingebrigtsen
2021-02-27 13:58 ` Eli Zaretskii
2021-02-27 14:24 ` Lars Ingebrigtsen
2021-02-26 16:04 ` bug#24774: [External] : " Drew Adams
2021-02-23 16:50 ` Basil L. Contovounesios
2021-02-23 17:10 ` Eli Zaretskii
2021-02-23 17:24 ` Gregory Heytings
2021-02-23 17:37 ` Eli Zaretskii
2021-02-24 15:12 ` Lars Ingebrigtsen
2021-02-24 16:01 ` Stephen Berman
2021-02-24 16:06 ` Lars Ingebrigtsen
2021-02-27 14:58 ` Lars Ingebrigtsen
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=411796bc-6901-4d3a-b1f5-cc220169803d@default \
--to=drew.adams@oracle.com \
--cc=24774@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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).