From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: larsi@gnus.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: master 0161c9d 1/2: Load all generic-x.el modes unconditionally
Date: Thu, 11 Feb 2021 19:12:05 +0200 [thread overview]
Message-ID: <83k0reh6l6.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=4vL4ZKgW-Vap3R=7ppYWaB0z00iCqPjEZrpS-RE=5mw@mail.gmail.com> (message from Stefan Kangas on Thu, 11 Feb 2021 11:02:23 -0600)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Thu, 11 Feb 2021 11:02:23 -0600
> Cc: Eli Zaretskii <eliz@gnu.org>, larsi@gnus.org, emacs-devel@gnu.org
>
> > So, maybe a better solution is to make sure the entries are added to the
> > *end* of `auto-mode-alist`, which should make them harmless enough.
>
> That sounds good to me: we would then use them only as a last resort.
>
> Is it true that any `auto-mode-alist' entries by third-party packages
> installed by package.el are autoloaded before the user can require
> generic-x from their init file? Or did I misunderstand the package
> loading mechanism?
>
> If it is true, I think that the above mostly solves the conflict with
> third-party packages, even in the case when it is added to
> `auto-mode-alist' using `add-to-list' instead of `push'.
>
> And would the above solution be acceptable to you, Eli?
The "above" being that generic-x will add to the end of
auto-mode-alist? That's better than nothing, although it is still a
backward-incompatible change. You assume that having some font-lock
cannot hurt, but that isn't necessarily what users will think, because
someone might _want_ to have certain files edited in Fundamental mode,
and adding font-lock could therefore be an unexpected annoyance.
next prev parent reply other threads:[~2021-02-11 17:12 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 [this message]
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
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=83k0reh6l6.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).