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: Brand new clojure support in Emacs ;-) Date: Sat, 02 Sep 2023 09:04:26 +0300 Message-ID: <834jkdaz6d.fsf@gnu.org> References: <87il9kksqz.fsf@dfreeman.email> <87wmy080kn.fsf@posteo.net> <83v8djcydl.fsf@gnu.org> <87350ndquw.fsf@dfreeman.email> <83350ncbns.fsf@gnu.org> <87cyzrjbd8.fsf@dfreeman.email> <83zg2vav46.fsf@gnu.org> <87o7j99304.fsf@dfreeman.email> <87zg2hsyrd.fsf@dfreeman.email> <87h6ontwfv.fsf@posteo.net> <835y4ucrz3.fsf@gnu.org> <831qficgin.fsf@gnu.org> <87ttsehwab.fsf@dfreeman.email> <87fs3x6ge7.fsf@gmail.com> <87v8cthmzl.fsf@dfreeman.email> <87a5u56atj.fsf@gmail.com> <87r0nhhgb5.fsf@dfreeman.email> 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="9185"; mail-complaints-to="usenet@ciao.gmane.io" Cc: danny@dfreeman.email, joaotavora@gmail.com, dmitry@gutov.dev, rms@gnu.org, emacs-devel@gnu.org To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 02 08:05:56 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 1qcJlc-00029W-5h for ged-emacs-devel@m.gmane-mx.org; Sat, 02 Sep 2023 08:05:56 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qcJka-0001P4-MY; Sat, 02 Sep 2023 02:04:52 -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 1qcJkY-0001Os-FD for emacs-devel@gnu.org; Sat, 02 Sep 2023 02:04:50 -0400 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 1qcJkX-0002mb-0b; Sat, 02 Sep 2023 02:04:49 -0400 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=K72rDhYHrcq67KrFTbdkbMCXO9bT5b9ymuUUNUa3kDA=; b=BYqO6IFdT6bxhSycRkYz KOnE7XAmeSl6VTckc/pizhna8WPTrwFqgonk31MlH40PnjlRxzp1f2Uxjy9ufFxCdIsW6MDn1Yz/b F0RHCxYuDNlKkh2WNzVzPnPQFX0xvje/feXTGwvC8aSUxgGoDiAkQlCdveyHWaZJ8EfnyGTPkBPMM F8C74LfKZ3DIciTvql7IklvfOoaA8AJtafaGBercoM1I6dO8cxRy4MVTVg3K09pachWao1sI5+wcD 5nnKayOhQ//1PdecgJiXuzB9jhr5sxbXa5vjaMcI+vT/ncvDsx+EnBGotsVjbLNOcoyWZBnU/1opq g2mT5caBgS7aEg==; In-Reply-To: (message from Stefan Kangas on Fri, 1 Sep 2023 21:25:06 +0200) 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:309849 Archived-At: > From: Stefan Kangas > Date: Fri, 1 Sep 2023 21:25:06 +0200 > Cc: João Távora , > Eli Zaretskii , Dmitry Gutov , rms@gnu.org, emacs-devel@gnu.org > > Danny Freeman writes: > > > You will also see a later > > message where I said once clojure-ts-mode is in a more "done" state I > > will revisit the question of inclusion here with other clojure-mode > > devs. Until then I will continue to develop clojure-ts-mode in the > > clojure-emacs github organization with the intention of integrating it > > with the rest of the clojure-emacs tooling. > > Thanks again for being willing to revisit this decision. Emacs 30 is > still at least a year away, so I think late spring or early summer > 2024 could be a good time to do it. If this will be a package that's not bundled with Emacs, its development and release schedule doesn't have to be synchronized with Emacs, unless the package needs some features not currently available in Emacs 29 or earlier. But if there's intent to perhaps include this package with Emacs, then for that to happen in Emacs 30.1, the decision should be earlier, perhaps within the next 4-5 months. Because, though the _release_ of Emacs 30 is probably a year or so away, we might decide to cut the emacs-30 release branch before the end of 2023, and any additional new features after that would be harder to get into the release branch.