From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: New Eglot release Date: Mon, 06 Mar 2023 17:33:36 +0000 Message-ID: <87jzztzswf.fsf@posteo.net> References: <87a60sjneo.fsf@gmail.com> <87v8jfw5si.fsf@posteo.net> <87cz5mhmku.fsf@gmail.com> 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="18762"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Mar 06 18:34:35 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 1pZEjK-0004iY-UF for ged-emacs-devel@m.gmane-mx.org; Mon, 06 Mar 2023 18:34:35 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pZEiM-0007xp-W8; Mon, 06 Mar 2023 12:33:35 -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 1pZEiC-0007tX-Du for emacs-devel@gnu.org; Mon, 06 Mar 2023 12:33:27 -0500 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pZEi9-0003Cf-Ar for emacs-devel@gnu.org; Mon, 06 Mar 2023 12:33:24 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 84C43240251 for ; Mon, 6 Mar 2023 18:33:17 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1678123997; bh=79pzF4luReOKQbCh61p0LjHgbwmAXpGtEQLeZwDExPg=; h=From:To:Cc:Subject:Date:From; b=d9UdyArXPffozfVHkNGvNkJ0lGPeZQvGEyeJ7yxj0rxmpEAjSjaBDYfaLVcbExs/4 bm0Ts1+akKrYzjol/riU0pBa8YW45MlHdDxuJ5ESunqJp+8uwjI+fnMZSvNoj3f9l1 +EEn+pX9sz06TadZ+AakXqpOYM+ZKjLzftHNcbJ0rGJ6UQK+lThp/a8p/jGlDMe3J1 kJ4fTp8yeIqUc911w11nKIuROW9sxhEGYaPK8/oNre20ME94coVfjfaST2YCcHvKIm el+tpkFvYF6G5yVB3wEMvAiAlnXHFaLqPjarZ99myaU2e1YQ+E1fxiobjMOBYeg6rJ iAz1u49ZyN3+w== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4PVlzH3RwQz6tmS; Mon, 6 Mar 2023 18:33:15 +0100 (CET) In-Reply-To: <87cz5mhmku.fsf@gmail.com> (=?utf-8?Q?=22Jo=C3=A3o_T=C3=A1vor?= =?utf-8?Q?a=22's?= message of "Sun, 05 Mar 2023 22:15:13 +0000") Received-SPF: pass client-ip=185.67.36.65; envelope-from=philipk@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:304056 Archived-At: Jo=C3=A3o T=C3=A1vora writes: > Philip Kaludercic writes: > >> Jo=C3=A3o T=C3=A1vora writes: >> >>> Hello, >>> >>> After some significant work done to Eglot in emacs-29 the last few >>> weeks, I'd like to make the 1.12 release so people can use it from GNU >>> ELPA in older Emacs versions. >>> >>> However, one question remains from the merge: where to put >>> Eglot-specific NEWS describing the latest user-visible changes?? >>> >>> I'm not opposed to putting them in Emacs's own NEWS file, except that >>> for this Emacs 29 version it'd be a bit akward, since Eglot just made it >>> in, so the existing NEWS is about Eglot's appearance, not about what >>> changed recently. >>> >>> I think, someone suggested /etc/EGLOT-NEWS at the time. That could >>> work, I guess. But would anyone read it? >> >> Would using a "News" section in eglot.el (along the same lines of the >> "Commentary" section) make sense here? elpa-admin.el should pick this >> up when generating news for elpa.gnu.org. > > Thanks for the suggestion. It would make sense, but has the drawback > that it makes a file grow a bit too much for my personal taste.=20=20 Depending on what your standards are, I think that if the news section only contained information about the latest revision (or the development revision), that the file size would be fine. > Do you > know if elpa-admin.el can pick up etc/EGLOT-NEWS? If not, I think I'll > go with Emacs's etc/NEWS, which is the most visible anyway. Maybe one > day there will be way for elpa-admin.el to pick up the Eglot-relevant > section there. No, to my knowledge none of the core packages don't use etc/NEWS or any other NEWS file. Not that this shouldn't be possible -- I don't imagine it should be too difficult to hack up something like that if there is a need for something like that, especially since Emacs 29 has brought along at least two larger packages (use-package and Eglot) into the core, that might have their own separate audiences. > Jo=C3=A3o