From: Visuwesh <visuweshm@gmail.com>
To: emacs-devel@gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>
Subject: Re: master 12f63c18f6 1/2: Add new macro 'while-let'
Date: Wed, 28 Sep 2022 17:34:19 +0530 [thread overview]
Message-ID: <87czbfbt8c.fsf@gmail.com> (raw)
>branch: master
>commit 12f63c18f6d5a886f62f10b4c8de8de3509e52df
>Author: Lars Ingebrigtsen <larsi@gnus.org>
>Commit: Lars Ingebrigtsen <larsi@gnus.org>
>
> Add new macro 'while-let'
>
> * doc/lispref/control.texi (Conditionals): Document
> when-let/if-let/while-let.
> * lisp/subr.el (while-let): New macro.
>---
> doc/lispref/control.texi | 42 ++++++++++++++++++++++++++++++++++++++++++
> etc/NEWS | 4 ++++
> lisp/subr.el | 13 +++++++++++++
> 3 files changed, 59 insertions(+)
>
>diff --git a/doc/lispref/control.texi b/doc/lispref/control.texi
>index ee2acdb002..9635b335bc 100644
>--- a/doc/lispref/control.texi
>+++ b/doc/lispref/control.texi
>@@ -294,6 +294,48 @@ For example:
> @end group
> @end example
>
>+If can be convenient to bind variables in conjunction with using a
^^
Typo: this should be "It".
>+conditional. It's often the case that you do a computation, and then
>+want to do something with that computation if it's non-@code{nil}.
>+The straightforward way to do that is to just write, for instance:
next reply other threads:[~2022-09-28 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 12:04 Visuwesh [this message]
[not found] <166436449368.11560.17915607619196292155@vcs2.savannah.gnu.org>
[not found] ` <20220928112814.B0924C12D9B@vcs2.savannah.gnu.org>
2022-09-28 15:25 ` master 12f63c18f6 1/2: Add new macro 'while-let' Philip Kaludercic
2022-09-29 10:29 ` Lars Ingebrigtsen
2022-09-29 11:42 ` Philip Kaludercic
2022-09-29 11:48 ` Lars Ingebrigtsen
2022-10-15 14:12 ` Philip Kaludercic
2022-10-16 7:45 ` Lars Ingebrigtsen
2022-10-16 9:26 ` Philip Kaludercic
2022-10-16 22:59 ` Sean Whitton
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=87czbfbt8c.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).