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

> 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.

You are right.  God bless you.
> 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.

I think, I didn't express myself well.  I was to know the major elisp documentation changes.  Not every change.  

After reading venerable "An Introduction to Programming in Emacs Lisp" of Robert J. Chassell, and a few online materials, I am on elisp manual now; updating to Emcs 30.91 and seeing noticable changes, I fear to miss anything added to or changed in chapters I have already read and passed.

But:
> Alternatively, run Diff on the old and the new version of elisp.info.

This will work best for me.

Besides, seems NEWS already does cover any important changes into elisp.

Thanks
--
Best Regards,
Abraham
Sent with Tutanota; https://tuta.com



      reply	other threads:[~2024-09-14 14:47 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
2024-09-14 14:47   ` Abraham S.A.H. via Emacs development discussions. [this message]

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=O6l-86O--F-9@tuta.io \
    --to=emacs-devel@gnu.org \
    --cc=arash.sah@tuta.io \
    --cc=eliz@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.