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: Make all tree-sitter modes optional Date: Fri, 20 Jan 2023 21:13:26 +0200 Message-ID: <83o7qtm33d.fsf@gnu.org> References: <83a62dobfi.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27661"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Pedro Andres Aranda Gutierrez Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jan 20 20:14:21 2023 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 1pIwqC-00071P-B8 for ged-emacs-devel@m.gmane-mx.org; Fri, 20 Jan 2023 20:14:20 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pIwpP-0005un-Pc; Fri, 20 Jan 2023 14:13:31 -0500 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 1pIwpN-0005sp-2e for emacs-devel@gnu.org; Fri, 20 Jan 2023 14:13:29 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pIwpM-0001eY-Lb; Fri, 20 Jan 2023 14:13:28 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=1PV1RxP/2ggmrbEkkIAUozzMxNgor5ngFsx5mH8G3hE=; b=jVl/IVNLhk6YNJzymuVg 2NTDSZAESfae5SlLFtmTqDFpAQ1L+eE8T2TiHHGSNoLT7oW8I2DVZ5DKLBjfiPz8+4HuFPicSWXGR vVSq46EDIWvuU+IEEGJBUrpprXWZl5nX7U/Ru9fRCt69l8BISdKYW3u/3I4bGAWLZXG2UpnbcFNWZ zHKxAXLUCvt7DxD9sYzb9HyAnWnHPDMuaeuxUZge7zIGUiJgrkj6F/nHs9oHFHQttw3JZEWuW56Wo msP0zyRx4u7aWzD1lZJsMvY9tSOAv1ZDi51BREmko0COiYY5vgqwwFim0dWXnwweB3JZLXgReDbNO rVmYLF7ifIU/2g==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pIwpK-0001Ii-OC; Fri, 20 Jan 2023 14:13:27 -0500 In-Reply-To: (message from Pedro Andres Aranda Gutierrez on Fri, 20 Jan 2023 17:31:44 +0100) 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:302582 Archived-At: > From: Pedro Andres Aranda Gutierrez > Date: Fri, 20 Jan 2023 17:31:44 +0100 > Cc: emacs-devel@gnu.org > > Thanks for that :-) > It's a first step. However, the *-ts-mode.el files still go through the .el compilation, yielding error messages > during the compilation. What error messages? Please show them, we cannot possibly guess what messages do you see. And why is it a problem that the *.el files are being compiled as part of the build? A build compiles all the *.el files, including ones you will never use and ones that you cannot use (e.g., because they are for Emacs running on other OSes). That is never a problem. > Additionally, they get installed in the binary distribution: > > emacs-29 ➤ find Emacs.app -name \*-ts-\* > Emacs.app/Contents/Resources/lisp/progmodes/c-ts-mode.el.gz > Emacs.app/Contents/Resources/lisp/progmodes/c-ts-mode.elc > Emacs.app/Contents/Resources/lisp/progmodes/cmake-ts-mode.el.gz > Emacs.app/Contents/Resources/lisp/progmodes/cmake-ts-mode.elc > Emacs.app/Contents/Resources/lisp/progmodes/dockerfile-ts-mode.el.gz > Emacs.app/Contents/Resources/lisp/progmodes/dockerfile-ts-mode.elc > Emacs.app/Contents/Resources/lisp/progmodes/go-ts-mode.el.gz > Emacs.app/Contents/Resources/lisp/progmodes/go-ts-mode.elc > Emacs.app/Contents/Resources/lisp/progmodes/java-ts-mode.el.gz > Emacs.app/Contents/Resources/lisp/progmodes/java-ts-mode.elc > Emacs.app/Contents/Resources/lisp/progmodes/json-ts-mode.el.gz > Emacs.app/Contents/Resources/lisp/progmodes/json-ts-mode.elc > Emacs.app/Contents/Resources/lisp/progmodes/ruby-ts-mode.el.gz > Emacs.app/Contents/Resources/lisp/progmodes/ruby-ts-mode.elc > Emacs.app/Contents/Resources/lisp/progmodes/rust-ts-mode.el.gz > Emacs.app/Contents/Resources/lisp/progmodes/rust-ts-mode.elc > Emacs.app/Contents/Resources/lisp/progmodes/typescript-ts-mode.el.gz > Emacs.app/Contents/Resources/lisp/progmodes/typescript-ts-mode.elc > Emacs.app/Contents/Resources/lisp/textmodes/toml-ts-mode.el.gz > Emacs.app/Contents/Resources/lisp/textmodes/toml-ts-mode.elc > Emacs.app/Contents/Resources/lisp/textmodes/yaml-ts-mode.el.gz > Emacs.app/Contents/Resources/lisp/textmodes/yaml-ts-mode.elc > > That may be a source of confusion ... Why would it confuse? You also have there stuff like w32-win.el.gz, which is used only on MS-Windows, and other files that are not necessarily for your configuration. This is not a problem, and shouldn't be one.