From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: master 0161c9d 1/2: Load all generic-x.el modes unconditionally Date: Thu, 11 Feb 2021 19:12:05 +0200 Message-ID: <83k0reh6l6.fsf@gnu.org> References: <20210209160550.18823.10795@vcs0.savannah.gnu.org> <20210209160551.832FB20AD1@vcs0.savannah.gnu.org> <87o8gti2ln.fsf@gnus.org> <83sg65jffx.fsf@gnu.org> <83im71j96z.fsf@gnu.org> <83czx8k3gn.fsf@gnu.org> <83sg64hqzj.fsf@gnu.org> <83im6zj1bo.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7514"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Feb 11 18:20:00 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lAFdH-0001qX-OS for ged-emacs-devel@m.gmane-mx.org; Thu, 11 Feb 2021 18:19:59 +0100 Original-Received: from localhost ([::1]:34572 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lAFdF-0005OC-4r for ged-emacs-devel@m.gmane-mx.org; Thu, 11 Feb 2021 12:19:57 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52088) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lAFVd-00085e-03 for emacs-devel@gnu.org; Thu, 11 Feb 2021 12:12:05 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46365) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lAFVb-0001pL-Jd; Thu, 11 Feb 2021 12:12:03 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1499 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lAFVa-0008HD-Fx; Thu, 11 Feb 2021 12:12:02 -0500 In-Reply-To: (message from Stefan Kangas on Thu, 11 Feb 2021 11:02:23 -0600) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:264411 Archived-At: > From: Stefan Kangas > Date: Thu, 11 Feb 2021 11:02:23 -0600 > Cc: Eli Zaretskii , 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.