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: Tracing changes to elisp manual Date: Sat, 14 Sep 2024 17:12:47 +0300 Message-ID: <86plp6fhnk.fsf@gnu.org> References: 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="15612"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: "Abraham S.A.H." Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 14 16:13:08 2024 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 1spTWN-0003rV-OV for ged-emacs-devel@m.gmane-mx.org; Sat, 14 Sep 2024 16:13:08 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1spTW9-0006hH-5v; Sat, 14 Sep 2024 10:12:53 -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 1spTW7-0006gy-W5 for emacs-devel@gnu.org; Sat, 14 Sep 2024 10:12:52 -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 1spTW6-0001ML-DP; Sat, 14 Sep 2024 10:12:50 -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=Og7j62w370Ad/YNzeYTOlCnSolaE2QomxT4api8IHXo=; b=n/xlokq2d1EDIy1fuSZY gUYtNBJoiAL/IubRG8D3E8Aul8Ui7D+DPMcR11DGLLUsdTtOnnzoXD3OsEbOHVmoqDpl4/eU51woQ PK0N3Bu/KRkfoSTyEL+7nETzDJ9RsBhtUsYDytVkthHO2XL1Z4+6Nr0fsJqmpBZFcWZlp5JleFjbm XPju59TalVCTzCe/65vmCwEm/hkW/AMS0XihP+vViDy2HBDRdmDULUo6dQJNXdtlyFOmxC+GxBFPY T3aCaZKdXHQEYHlrBWQp4Uri/usxFVZ4JC3a49eRMAvIPXTOc2RvnMJ4ykGvk/0UX8KUCbqz+9VeJ qf6oKgvBR0q2RQ==; In-Reply-To: (emacs-devel@gnu.org) 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:323614 Archived-At: > Date: Sat, 14 Sep 2024 15:42:53 +0200 (CEST) > From: "Abraham S.A.H." via "Emacs development discussions." > > I didn't get any respond in emacs-user list. Stefan replied to you there. > I have noticed a new closure section in elisp manual's “lisp data types section”. > > “(elisp) Top > Lisp Data Types > Programming Types > Closure Type” > > (replaced byte-compiled functions) > And I wonder, how can someone find out what are the new additions/removals/changes to elisp manual from the previous version? > > For instance, when using Emacs 30.1 I want to know what have been changed in Emacs Lisp Reference Manual since version 29.4. > > I have checked “view-emacs-news” (C-h n); it does show latest changes into Emacs Lisp, but not current version's major changes to Elisp manual. > > Is there any changelog or news for elisp manual? We no longer maintain ChangeLog files, we generate them from Git log. You could grep for "lispref" in the latest top-level ChangeLog.N file in the tree created by unpacking the tarball, which will show the log of changes to that manual. But the description of the changes is very terse in the logs. If you want to see the changes in the text, you will have to use Git in the clone of the Emacs repository. Alternatively, run Diff on the old and the new version of elisp.info. More generally, we describe the changes in NEWS, and not on any lower levels, because doing that would be a significant maintenance burden, and we don't consider that as an efficient investment of our resources. May I ask why you are interested in the changes on such a low level? Basically, every change in wording or punctuation are technically "changes in the manual", but I very much doubt that it could be of any practical interest.