unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Heime <heimeborgia@protonmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Lisp error on function :documentation
Date: Mon, 17 Oct 2022 02:08:42 +0000	[thread overview]
Message-ID: <4djjljp3BAf2wR6MFQoPwYsnn7HyCtOAPniR0TesASPSNVsicnY7bkdfh1SAU9VAUHYaEIv2520ShBW2NnVtoJrl_B4YAjZ3Ha6fX10vR14=@protonmail.com> (raw)
In-Reply-To: <877d0zckgu.fsf@web.de>


------- Original Message -------
On Monday, October 17th, 2022 at 1:22 AM, Michael Heerdegen <michael_heerdegen@web.de> wrote:


> Stefan Monnier via Users list for the GNU Emacs text editor
> help-gnu-emacs@gnu.org writes:
> 
> > If `:documentation` does what he needs, it's a much simpler solution.
> > 
> > Stefan "to be blamed for both `:documentation` and OClosures"
> 
> 
> To be blamed to show up too late here, first and foremost.
> 
> Ok, so the argument of :documentation is a form that is eval'led
> dynamically, and not only when the definition is evaluated, is that
> correct? Then it would be the simplest solution by far indeed.
> 
> Michael.

That was my implementation.  After all, I did do my homework.  If the
emacs maintainers can clear up recommendations against using undocumented
features (allowing use of :documentation it a defun as acceptable, or providing
alternative that is acceptable and does the equivalent), life would be good.



  parent reply	other threads:[~2022-10-17  2:08 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 [this message]
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
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='4djjljp3BAf2wR6MFQoPwYsnn7HyCtOAPniR0TesASPSNVsicnY7bkdfh1SAU9VAUHYaEIv2520ShBW2NnVtoJrl_B4YAjZ3Ha6fX10vR14=@protonmail.com' \
    --to=heimeborgia@protonmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).