From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "8951@debbugs.gnu.org" <8951@debbugs.gnu.org>
Subject: bug#8951: [External] : Re: bug#8951: 24.0.50; [PATCH] enhancement request: buttonize key names
Date: Sun, 24 Oct 2021 16:15:41 -0700 [thread overview]
Message-ID: <CADwFkmmyoLyNPPLD1fvrn7n2mxjFU5ZYbrp4nPRzJ_ycdz+mbA@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR10MB5488DE960876FD00DB505DBAF3829@SJ0PR10MB5488.namprd10.prod.outlook.com>
Drew Adams <drew.adams@oracle.com> writes:
> Grep even just the vanilla Emacs-Lisp sources for
> `substitute-command-keys'. It's not used only for
> *Help*. And then think about uses by other code,
> besides vanilla Emacs.
I only see a lot of places where we want whatever the user has
configured, none where we need an optional argument.
> What's the reason you prefer not to? I don't
> understand. Maybe you have a good reason, but
> I don't think you gave any (?).
I'm repeating myself here: I'm actually happy to add it, if we have a
use-case. How about we try this for a start, and once users start using
this in the wild, they'll come back to us and say: hey I really want an
optional parameter here. Then we think about if that makes sense for
their use-case, maybe it will, maybe it won't. But at least we know
what we are trying to do.
The alternative is that we add stuff just because "maybe someone will
need it". That leads to feature creep, bloat, and is just not a good
way to develop software.
next prev parent reply other threads:[~2021-10-24 23:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 19:13 bug#44909: Hyperlinks gone for first story of two-storied *Help* buffers 積丹尼 Dan Jacobson
2020-11-28 7:39 ` Eli Zaretskii
2020-11-28 7:56 ` Stefan Kangas
2011-06-28 16:38 ` bug#8951: 24.0.50; [PATCH] enhancement request: buttonize key names Drew Adams
2011-07-04 20:28 ` Stefan Monnier
2011-07-04 21:08 ` Drew Adams
2011-07-06 18:49 ` Stefan Monnier
2011-07-06 19:55 ` Drew Adams
2011-07-08 19:07 ` Stefan Monnier
2011-07-08 19:20 ` Drew Adams
2019-06-27 16:35 ` Lars Ingebrigtsen
2021-10-23 0:46 ` Stefan Kangas
2021-10-24 13:36 ` Lars Ingebrigtsen
2021-10-24 13:54 ` Stefan Kangas
2021-10-24 14:15 ` Lars Ingebrigtsen
2021-10-24 14:56 ` Stefan Kangas
2021-10-24 21:07 ` bug#8951: [External] : " Drew Adams
2021-10-24 21:37 ` Stefan Kangas
2021-10-24 22:05 ` Drew Adams
2021-10-24 22:24 ` Stefan Kangas
2021-10-24 22:47 ` Drew Adams
2021-10-24 23:15 ` Stefan Kangas [this message]
2021-10-25 1:32 ` Drew Adams
2021-10-25 2:37 ` Stefan Kangas
2020-11-28 20:45 ` bug#8951: bug#44909: Hyperlinks gone for first story of two-storied *Help* buffers 積丹尼 Dan Jacobson
2020-11-29 10:25 ` 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=CADwFkmmyoLyNPPLD1fvrn7n2mxjFU5ZYbrp4nPRzJ_ycdz+mbA@mail.gmail.com \
--to=stefan@marxist.se \
--cc=8951@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=monnier@iro.umontreal.ca \
/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).