emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#58602: closed (29.0.50; Please document (:documentation FORM) spec f


From: GNU bug Tracking System
Subject: bug#58602: closed (29.0.50; Please document (:documentation FORM) spec for closures )
Date: Wed, 19 Oct 2022 23:24:02 +0000

Your message dated Thu, 20 Oct 2022 01:23:38 +0200
with message-id <87y1tb75z9.fsf@web.de>
and subject line Re: bug#58602: 29.0.50; Please document (:documentation FORM) 
spec for closures
has caused the debbugs.gnu.org bug report #58602,
regarding 29.0.50; Please document (:documentation FORM) spec for closures 
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
58602: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58602
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 29.0.50; Please document (:documentation FORM) spec for closures Date: Tue, 18 Oct 2022 02:46:00 +0200 User-agent: Gnus/5.13 (Gnus v5.13)
Hello,

I think we need to document this new feature described in etc/NEWS.25:

| ** Lexical closures can use '(:documentation FORM)' to build their docstring.
| It should be placed right where the docstring would be, and FORM is then
| evaluated (and should return a string) when the closure is built.

at least in the ELisp reference manual (dunno, maybe also in the
docstring of `lambda' and `defun'?).

Thanks,

Michael.





--- End Message ---
--- Begin Message --- Subject: Re: bug#58602: 29.0.50; Please document (:documentation FORM) spec for closures Date: Thu, 20 Oct 2022 01:23:38 +0200 User-agent: Gnus/5.13 (Gnus v5.13)
Michael Heerdegen <michael_heerdegen@web.de> writes:

> > [...] I noticed that `i :documentation RET` doesn't bring me to this
> > text, instead it just looks for "documentation"

> `Info-index':
>   ;; Strip leading colon in topic; index format does not allow them.
>   (if (and (stringp topic)
>          (> (length topic) 0)
>          (= (aref topic 0) ?:))
>       (setq topic (substring topic 1)))

Yes, deleting that part breaks the i command, so I guess we have to live
with this restriction or find a way to filter out the wanted matches.

Anyway, I think we are done here.  Thanks to all, and especially Stefan.

Michael.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]