GNU bug report logs - #75852
[PATCH] ; (let-alist): Document double-dot escape syntax.

Previous Next

Package: emacs;

Reported by: Eshel Yaron <me <at> eshelyaron.com>

Date: Sun, 26 Jan 2025 08:06:02 UTC

Severity: normal

Tags: patch

Fixed in version 30.1

Done: Eshel Yaron <me <at> eshelyaron.com>

Bug is archived. No further changes may be made.

Full log


Message #11 received at 75852 <at> debbugs.gnu.org (full text, mbox):

From: Artur Malabarba <arturmalabarba <at> gmail.com>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: 75852 <at> debbugs.gnu.org, Eshel Yaron <me <at> eshelyaron.com>
Subject: Re: bug#75852: [PATCH] ;
 (let-alist): Document double-dot escape syntax.
Date: Sun, 26 Jan 2025 11:22:22 -0300
[Message part 1 (text/plain, inline)]
Looks good to me!

Em dom., 26 de jan. de 2025, 11:08, Stefan Kangas <stefankangas <at> gmail.com>
escreveu:

> Eshel Yaron via "Bug reports for GNU Emacs, the Swiss army knife of text
> editors" <bug-gnu-emacs <at> gnu.org> writes:
>
> > Tags: patch
> >
> > Document a "hidden" let-alist feature.
>
> Artur, any comments?
>
> > From 286f79bf5768fb093f0a044084a83a89fffe111f Mon Sep 17 00:00:00 2001
> > From: Eshel Yaron <me <at> eshelyaron.com>
> > Date: Sun, 26 Jan 2025 08:56:15 +0100
> > Subject: [PATCH] ; (let-alist): Document double-dot escape syntax.
> >
> > ---
> >  lisp/emacs-lisp/let-alist.el | 6 ++++++
> >  1 file changed, 6 insertions(+)
> >
> > diff --git a/lisp/emacs-lisp/let-alist.el b/lisp/emacs-lisp/let-alist.el
> > index 239a4ad69eb..b79c2e51de9 100644
> > --- a/lisp/emacs-lisp/let-alist.el
> > +++ b/lisp/emacs-lisp/let-alist.el
> > @@ -146,6 +146,12 @@ let-alist
> >  inside the original alist by using dots inside the symbol, as
> >  displayed in the example above.
> >
> > +To refer to a non-`let-alist' variable starting with a dot in BODY, use
> > +two dots instead of one.  For example, in the following form `..foo'
> > +refers to the variable `.foo' bound outside of the `let-alist':
> > +
> > +    (let ((.foo 42)) (let-alist \\='((foo . nil)) ..foo))
> > +
> >  Note that there is no way to differentiate the case where a key
> >  is missing from when it is present, but its value is nil.  Thus,
> >  the following form evaluates to nil:
> > --
> > 2.46.2
>
[Message part 2 (text/html, inline)]

This bug report was last modified 167 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.