From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Theodor Thornhill via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#60376: 29.0.60; Standardize csharp-ts-mode's font-lock features Date: Fri, 30 Dec 2022 15:40:49 +0100 Message-ID: References: <7A5618C7-25D7-4B52-8D16-5C54F09FA4CA@gmail.com> <83lemp717m.fsf@gnu.org> <4bb171b5-71d8-d265-0bf6-d688b5146603@secure.kjonigsen.net> <838rip6kq3.fsf@gnu.org> Reply-To: Theodor Thornhill Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23752"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 60376@debbugs.gnu.org, casouri@gmail.com To: Eli Zaretskii , jostein@kjonigsen.net Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Dec 30 15:41:34 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1pBGZi-0005zl-3Y for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 30 Dec 2022 15:41:34 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pBGZX-0003Ae-2j; Fri, 30 Dec 2022 09:41:23 -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 1pBGZS-0003AJ-Gs for bug-gnu-emacs@gnu.org; Fri, 30 Dec 2022 09:41:19 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pBGZC-0005Cn-JC for bug-gnu-emacs@gnu.org; Fri, 30 Dec 2022 09:41:17 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pBGZC-0006Ox-F2 for bug-gnu-emacs@gnu.org; Fri, 30 Dec 2022 09:41:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Theodor Thornhill Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 30 Dec 2022 14:41:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 60376 X-GNU-PR-Package: emacs Original-Received: via spool by 60376-submit@debbugs.gnu.org id=B60376.167241125324583 (code B ref 60376); Fri, 30 Dec 2022 14:41:02 +0000 Original-Received: (at 60376) by debbugs.gnu.org; 30 Dec 2022 14:40:53 +0000 Original-Received: from localhost ([127.0.0.1]:33807 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pBGZ3-0006OR-Ax for submit@debbugs.gnu.org; Fri, 30 Dec 2022 09:40:53 -0500 Original-Received: from out-223.mta0.migadu.com ([91.218.175.223]:47826) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pBGZ1-0006OJ-8T for 60376@debbugs.gnu.org; Fri, 30 Dec 2022 09:40:52 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thornhill.no; s=key1; t=1672411249; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=uV0l2NrLE2bmtjkq6+O9imH55SVzZtplqI3yeocgTlM=; b=pom0n2vFDEVuH5JTcAikJa+Mi80aXIjIHmZ8Nz73vA0OTiDe6+LHE5HVKhoDWVfGKP9Rtl ZiS0vwaAppSb4/pe+OQ4Uij431NtUdQI9QNYE5U51ie2k17dtNPJZ8wHIf3SDmk+hXtvaD evmnGrXR9yeHJUXniinydfGZIwbFCSWYZfxacb/u0pixiGsEtXY5d+iF5mY5JLTw43hWhW 879GNf2eK80ToggvnwiHKRLLTvVMhKMpA+cq4d5JS9oW73JzfmAk2A4bn6JGNGh2OqNHUy UbuscwrGgj/p1xYw24l9cKyBZsPx0VFl6Ms+spzMKXyVXpKxmIAlFbigLWBW6w== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. In-Reply-To: <838rip6kq3.fsf@gnu.org> X-Migadu-Flow: FLOW_OUT X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:252124 Archived-At: On 30 December 2022 15:15:48 CET, Eli Zaretskii wrote: >> Date: Fri, 30 Dec 2022 14:35:46 +0100 >> Cc: 60376@debbugs=2Egnu=2Eorg, jostein@kjonigsen=2Enet, theo@thornhill= =2Eno >> From: Jostein Kj=C3=B8nigsen >>=20 >> Cc: 60376@debbugs=2Egnu=2Eorg, jostein@kjonigsen=2Enet, theo@thornhill= =2Eno >> >> From: Yuan Fu >> >> Date: Thu, 29 Dec 2022 14:16:13 -0800 >> >> >> >>> So a "complete feature freeze" is approaching=2E That makes complet= e sense, and I respect that=2E Are there any exact >> >>> deadlines or dates we'd like to stay ahead of, or is this more an a= bstract thing, until Emacs 29 is eventually deemed ready >> >>> for release? >> >> I heard that it=E2=80=99s in a few days (from Eli)=2E >> > That was a few days ago ;-) So now it's "any day now"=2E >>=20 >> Ok=2E That's unfortunate timing=2E >>=20 >> To be clear, I think it's absolutely realistic to get csharp-ts-mode to= =20 >> adhere to some of the guidelines outlined in the=20 >> tree-sitter-standardization thread=2E >>=20 >> But it's completely unrealistic (at least on my part) to get any=20 >> well-crafted and well-tested changes into csharp-ts-mode until after=20 >> new-years=2E > >If you can come up with a 85% correct code soon, and leave the rest >for bug-fixing, that's also acceptable=2E > >Otherwise, please understand my POV: we do want to release Emacs 29 >soon=2E The tree-sitter related features already got a full month of >slack, whereby new features were acceptable on the release branch=2E If >we keep delaying the freeze, we will not release Emacs 29 any time >soon=2E You have all been here for the past month, and I announced the >rules loud and clear, so if some modes are still not up to speed with >the latest treesit=2Eel changes, then it's too bad, but we will have to >wait for Emacs 30 with those=2E I'm sorry, but we do need to draw the >line in the sand at some point: people are waiting for Emacs 29, and >we cannot disappoint them=2E I agree, but I'll see what I can do this evening=2E=20 Jostein, if you can take the patch I concoct for a spin I'm sure we can re= ach that 85% mark ;) Theo