From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Subversion of user chosen major mode by Emacs. Date: Wed, 29 May 2024 11:04:39 -0400 Message-ID: References: <86r0dmtbk2.fsf@gnu.org> <86y17sssc6.fsf@gnu.org> <86v82wsnsf.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8504"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Alan Mackenzie , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 29 17:05:40 2024 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 1sCKrz-0001vE-AA for ged-emacs-devel@m.gmane-mx.org; Wed, 29 May 2024 17:05:39 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sCKrA-0000gz-3b; Wed, 29 May 2024 11:04:48 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sCKr9-0000gZ-0p for emacs-devel@gnu.org; Wed, 29 May 2024 11:04:47 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sCKr7-00073J-4K; Wed, 29 May 2024 11:04:46 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id A53D880A68; Wed, 29 May 2024 11:04:42 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1716995081; bh=W9Os9oRAl0iDOUm4EgbIdB/RKjRrf9vtsQGAgre7sCY=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=SKzfdc6sYlhLtfRdEx+4WlTkjFhjJ0UugrFKtXMmcCP+j40gA7TxSmReWDf76SdSe 1rzT0oGQZAYtvWivAinYsE9S/nbCZi8fghHnKrq0pzODmYpeEVY+QIstO/HhsWwRSl +EU1trh+WHBZPVsLFMz0gSBqeJOdIy+QwGqAs5HTUWXDaBxtjazZCbGciISUOTchW0 XxrZsXOSpZVKd3/cOrMqqQr0cZYdBifL9R0OvR5sq4w8JcQ4uzR+YTX2d+IlVVl9mZ c/vLrXhIQ0MAcQmLVaXyfGvXndob86Hix9JX9AlHAyRKnBrDowtiI0Jk2LEWS9eIPn iHjP3Ve8PGizA== Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id A2DCA808EE; Wed, 29 May 2024 11:04:41 -0400 (EDT) Original-Received: from lechazo (lechon.iro.umontreal.ca [132.204.27.242]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 8FA26120635; Wed, 29 May 2024 11:04:41 -0400 (EDT) In-Reply-To: <86v82wsnsf.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 29 May 2024 17:20:00 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:319692 Archived-At: > But anyway, why do you consider the above kludges wrt auto-mode-alist > more "kosher" and worthy of our support than the similar kludge you > could do with major-mode-remap-defaults for Emacs 30 and later? > They are both kludges one isn't supposed to do. The "official" way to do it not is by customizing `major-mode-remap-alist`, e.g. (push '(c-mode . c-mode) major-mode-remap-alist) or do the same via Custom. And you don't need to do that in a `with-eval-after-load`. Stefan