From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: larsi@gnus.org, stefan@marxist.se, emacs-devel@gnu.org
Subject: Re: master 0161c9d 1/2: Load all generic-x.el modes unconditionally
Date: Fri, 12 Feb 2021 17:41:06 +0200 [thread overview]
Message-ID: <831rdlfg4t.fsf@gnu.org> (raw)
In-Reply-To: <jwv4kihfh2w.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 12 Feb 2021 10:23:39 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: stefan@marxist.se, larsi@gnus.org, emacs-devel@gnu.org
> Date: Fri, 12 Feb 2021 10:23:39 -0500
>
> >> Nothing terrible. The question for me was rather "what's the benefit?".
> >> But among the disadvantages, the most obvious one is that you can't rely on
> >> (require 'generic-x) to define your function.
> > Yes, but the docs of the package explicitly documents this, so this is
> > intended behavior. Like I said, the package is a bit unusual; but
> > being unusual doesn't mean it's bad. It gets the job done.
>
> I think unusual is bad unless there's some clear benefit.
This could be a valid argument 20+ years ago, when the package was
added to Emacs. But that ship has sailed.
> Having control over which modes are auto-activated via `auto-mode-alist`
> is good, so it's a part we can keep.
>
> Having control over which functions are defined doesn't seem to offer
> any benefit, so I'd rather get rid of this unusual aspect.
Didn't I say that I'm okay with the former? It's fun to argue, I
know, but since we agree, do we have to continue?
I only mentioned reverting the whole changeset because I sensed Stefan
Kangas was leaning towards it.
next prev parent reply other threads:[~2021-02-12 15:41 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210209160550.18823.10795@vcs0.savannah.gnu.org>
[not found] ` <20210209160551.832FB20AD1@vcs0.savannah.gnu.org>
2021-02-09 17:16 ` master 0161c9d 1/2: Load all generic-x.el modes unconditionally Lars Ingebrigtsen
2021-02-09 17:53 ` Eli Zaretskii
2021-02-09 19:45 ` Stefan Kangas
2021-02-09 20:08 ` Eli Zaretskii
2021-02-09 20:47 ` Stefan Kangas
2021-02-09 21:08 ` Eli Zaretskii
2021-02-09 21:51 ` Stefan Kangas
2021-02-09 22:00 ` Stefan Monnier
2021-02-10 3:26 ` Eli Zaretskii
2021-02-10 14:00 ` Stefan Monnier
2021-02-10 15:39 ` Eli Zaretskii
2021-02-10 16:44 ` Stefan Kangas
2021-02-10 17:07 ` Stefan Monnier
2021-02-10 17:31 ` Eli Zaretskii
2021-02-10 17:10 ` Eli Zaretskii
2021-02-10 17:45 ` Stefan Monnier
2021-02-10 18:29 ` Matt Armstrong
2021-02-10 19:14 ` Eli Zaretskii
2021-02-11 14:06 ` Stefan Kangas
2021-02-11 14:22 ` Stefan Kangas
2021-02-11 14:47 ` Eli Zaretskii
2021-02-11 15:10 ` Stefan Kangas
2021-02-11 14:38 ` Stefan Kangas
2021-02-11 15:07 ` Stefan Monnier
2021-02-11 17:02 ` Stefan Kangas
2021-02-11 17:12 ` Eli Zaretskii
2021-02-11 18:00 ` Stefan Kangas
2021-02-11 19:29 ` Eli Zaretskii
2021-02-11 21:28 ` Stefan Kangas
2021-02-12 6:55 ` Eli Zaretskii
2021-02-12 13:43 ` Stefan Monnier
2021-02-12 14:40 ` Eli Zaretskii
2021-02-12 14:46 ` Stefan Monnier
2021-02-12 15:07 ` Eli Zaretskii
2021-02-12 15:23 ` Stefan Monnier
2021-02-12 15:41 ` Eli Zaretskii [this message]
2021-02-12 16:17 ` Stefan Monnier
2021-02-10 16:50 ` Stefan Monnier
2021-02-10 17:22 ` Eli Zaretskii
2021-02-10 19:22 ` Matt Armstrong
2021-02-09 19:00 ` Stefan Monnier
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=831rdlfg4t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--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).