From: Heime <heimeborgia@protonmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Lisp error on function :documentation
Date: Mon, 17 Oct 2022 01:55:11 +0000 [thread overview]
Message-ID: <JqeojZqTVJm4UxtRJeUs35cPAqnYnQ5II-LM28n-wlIc2bXSodNd934TBKfHGBSBoPMJtEHv0bbkFZP4ImCZGTmRzq2lVdLsdug1QxLwG0s=@protonmail.com> (raw)
In-Reply-To: <jwv1qr7feue.fsf-monnier+emacs@gnu.org>
------- Original Message -------
On Monday, October 17th, 2022 at 1:00 AM, Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> Heime [2022-10-16 23:09:08] wrote:
>
> > You all seem more interested in trying to satisfy your intellect than
> > helping out on the actual question by the OP.
>
>
> I'm definitely here to satisfy my intellect: guilty as charged.
>
> But as for the OP, I showed how I tried to reproduce it, and how
> `:documentation` worked for me. I'm not sure what more I can do at that
> point: I'm just waiting for a description of the OP that's precise
> enough to be reproduced.
Was able to get it work with the lexical binding setup, which was not working
as expected. I had no criticisms about your response. My only difficulty
is whether you recommend using such undocumented feature (commonly people vote
against using them). Being able to append to the documentation part a details
string is very strong programmatically. I would like that an equivalent
implementation be done and documented for public use. Otherwise I would continue
having to delay the addition until after the function definition.
> And in the mean time, I'm promoting OClosures :-)
>
> Stefan
As for closures, the recommendation against examining and altering the
structure of closure objects indicates that something very wrong in going
on.
next prev parent reply other threads:[~2022-10-17 1:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 23:48 Lisp error on function :documentation Heime via Users list for the GNU Emacs text editor
2022-10-16 2:48 ` Michael Heerdegen
2022-10-16 2:59 ` Heime
2022-10-16 3:37 ` Michael Heerdegen
2022-10-16 3:50 ` Heime
2022-10-16 4:12 ` Michael Heerdegen
2022-10-16 4:30 ` Heime
2022-10-16 22:53 ` Michael Heerdegen
2022-10-16 23:08 ` Heime
2022-10-16 23:23 ` Michael Heerdegen
2022-10-16 15:23 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-16 22:58 ` Michael Heerdegen
2022-10-16 23:09 ` Heime
2022-10-16 23:25 ` Michael Heerdegen
2022-10-16 23:39 ` Heime
2022-10-16 23:43 ` Michael Heerdegen
2022-10-17 0:07 ` Heime
2022-10-17 0:15 ` Michael Heerdegen
2022-10-17 1:01 ` Heime
2022-10-17 1:15 ` Michael Heerdegen
2022-10-17 1:01 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-17 1:22 ` Michael Heerdegen
2022-10-17 1:27 ` Michael Heerdegen
2022-10-17 2:08 ` Heime
2022-10-17 2:42 ` Michael Heerdegen
2022-10-17 3:03 ` Heime
2022-10-17 3:19 ` Emanuel Berg
2022-10-17 1:00 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-17 1:55 ` Heime [this message]
2022-10-17 12:28 ` Stefan Monnier
2022-10-17 13:15 ` Emanuel Berg
2022-10-17 19:27 ` tomas
2022-10-17 21:32 ` Emanuel Berg
2022-10-18 0:51 ` Michael Heerdegen
2022-10-18 1:05 ` Emanuel Berg
2022-10-16 3:56 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-16 4:00 ` Heime
2022-10-16 4:05 ` Michael Heerdegen
2022-10-16 4:07 ` Stefan Monnier
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='JqeojZqTVJm4UxtRJeUs35cPAqnYnQ5II-LM28n-wlIc2bXSodNd934TBKfHGBSBoPMJtEHv0bbkFZP4ImCZGTmRzq2lVdLsdug1QxLwG0s=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
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).