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: Call for volunteers: add tree-sitter support to major modes Date: Tue, 11 Oct 2022 17:38:18 -0400 Message-ID: References: <83czb1jrm3.fsf@gnu.org> <878rlo7on0.fsf@thornhill.no> <83o7uki5ol.fsf@gnu.org> <87tu4c5g9j.fsf@thornhill.no> <835ygshz6k.fsf@gnu.org> <87ilks59t6.fsf@thornhill.no> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17846"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Eli Zaretskii , acm@muc.de, emacs-devel@gnu.org, jostein@kjonigsen.net To: Theodor Thornhill Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 11 23:55:45 2022 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 1oiNE0-0004Pc-Q4 for ged-emacs-devel@m.gmane-mx.org; Tue, 11 Oct 2022 23:55:45 +0200 Original-Received: from localhost ([::1]:50432 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oiNDz-0000Pq-Bm for ged-emacs-devel@m.gmane-mx.org; Tue, 11 Oct 2022 17:55:43 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53464) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oiN4t-0002Dn-Oy for emacs-devel@gnu.org; Tue, 11 Oct 2022 17:46:25 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:48646) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oiN4p-0001hG-NA; Tue, 11 Oct 2022 17:46:18 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 249898027D; Tue, 11 Oct 2022 17:38:21 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 818B580091; Tue, 11 Oct 2022 17:38:19 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1665524299; bh=hdYPMPGhucpRGJp5MK9dk2vSyi8dWpIgzo+1zbYiJk0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=Hw3TN8Y3JsLJ9qWi2qY0FdjBXsVFPK9zKMuqHjiFeAv3n4g4YbNO89AbhTbvehfZF iE5wVaC9Q6N71F/USdOP/8+XgyIfbvPx2qc/n/+TXiJ0+8Pta00KPXCa9ehhrHErpr rPQCMZ3JrcH5CBaGcpZ9cBIez6EpMcmmega6PnUNDpY14qVjOanVvgdP3pZ1YHSLx0 lriAcNVoH0XYsabUdGY5ZHHjI7GD389amoKNxEvy1z60avXvyusiIpulxyKKDdsIPG jeY/zOila6cnzeAWSQ7ie5PSLOyo8Pmqlngc/qu0QXhc4bDJeGPQMubXmD+IKbinhN QvLNmZVDQiRWA== Original-Received: from alfajor (modemcable047.72-202-24.mc.videotron.ca [24.202.72.47]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 4FE4F120F42; Tue, 11 Oct 2022 17:38:19 -0400 (EDT) In-Reply-To: <87ilks59t6.fsf@thornhill.no> (Theodor Thornhill's message of "Mon, 10 Oct 2022 11:04:21 +0200") 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 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" Xref: news.gmane.io gmane.emacs.devel:297553 Archived-At: > In some cases, such as the two I mentioned, nothing. With others, such > as go-mode, something. This could be some integration with package > managers, documentation lookup functions, etc. In most cases, but not > all this is solved by LSP. In the cases where there are benefits in the > original mode that needs to be handled case by case. "Solve by LSP" will only solve it for some users. To best server the users, we still need to actively make efforts to integrate the old and the new modes, such as by making the old mode into a derived mode of the new mode, and then move missing features from the old mode to the new one. Experience tells me that if there's a builtin mode and a third-party mode, their natural course is to diverging. That results in more work, worse modes, and a poor user experience (silly choice between two similar contenders, confusing info on the web, ...). It's very hard to integrate two different modes after the fact, so we should make sure the new mode is integrated with the old one from the start (usually by making the old mode a derived mode of the new one), and work together with the old mode's maintainer to keep them in-sync and reduce the differences over time. Stefan