all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Abraham S.A.H." <arash.sah@tuta.io>
Cc: emacs-devel@gnu.org
Subject: Re: Tracing changes to elisp manual
Date: Sat, 14 Sep 2024 17:12:47 +0300	[thread overview]
Message-ID: <86plp6fhnk.fsf@gnu.org> (raw)
In-Reply-To: <O6klPoH--B-9@tuta.io> (emacs-devel@gnu.org)

> Date: Sat, 14 Sep 2024 15:42:53 +0200 (CEST)
> From:  "Abraham S.A.H." via "Emacs development discussions." <emacs-devel@gnu.org>
> 
> 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.



  parent reply	other threads:[~2024-09-14 14:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-14 13:42 Tracing changes to elisp manual Abraham S.A.H. via Emacs development discussions.
2024-09-14 14:12 ` Stefan Kangas
2024-09-14 14:12 ` Eli Zaretskii [this message]
2024-09-14 14:47   ` Abraham S.A.H. via Emacs development discussions.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86plp6fhnk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=arash.sah@tuta.io \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.