unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: simplifying cond*
Date: Mon, 30 Dec 2024 15:27:07 +0200	[thread overview]
Message-ID: <868qrxpahg.fsf@gnu.org> (raw)
In-Reply-To: <E1tS6xH-0003E2-0q@fencepost.gnu.org> (message from Richard Stallman on Sun, 29 Dec 2024 23:00:35 -0500)

> From: Richard Stallman <rms@gnu.org>
> Date: Sun, 29 Dec 2024 23:00:35 -0500
> 
> In writing text about cond* for the ELisp Reference Manual, I realized that
> I can simplify its usage conventions with no change in the code.
> Only the doc-string will change.
> 
> The change would document that all non-exit clauses are one-element clauses
> and all one-element clauses are non-exit clauses.  That would be true,
> for all the clauses that will remain documented as acceptable
> after this change.
> 
> The doc string would recommend
> 
>    ((progn BODY...))
> 
> instead of
> 
>    (t BODY...)
> 
> and
> 
>    ((when COND BODY...))
> 
> instead of
> 
>    (COND BODY... :non-exit)
> 
> WDYT?
> 
> Eli, I would like to put this change into version 30.
> It can't break anything.

Documentation changes are always okay on the release branch.  However,
in this case, cond* is not in Emacs 30, only in Emacs 31.  So you can
install any changes for it on the master branch without limitations,
but there's no cond* documentation to fix on the emacs-30 release
branch.



      reply	other threads:[~2024-12-30 13:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-30  4:00 simplifying cond* Richard Stallman
2024-12-30 13:27 ` Eli Zaretskii [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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=868qrxpahg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).