From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Heime <heimeborgia@protonmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Lisp error on function :documentation
Date: Sun, 16 Oct 2022 00:07:18 -0400 [thread overview]
Message-ID: <jwv4jw4ifdd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <Y625MB7x-XZplkMooaI97spqTe_l4jKBS5Y4qyU2t4bABYQBDIUiyN18r8ZSThisMvjHTBnx-bBVBamLGMHytk0VsyAOIg9k2JPO8jWOYaQ=@protonmail.com> (Heime's message of "Sun, 16 Oct 2022 04:00:01 +0000")
>> > (defun ivy-config ()
>> > (:documentation (concat "Ivy completion.\n\n" ivy-details))
>> > (add-to-list 'load-path "~/contrib/ivy"))
>>
>>
>> Works for me. Is your Emacs simply too old?
>
> Would not think so. Emacs 29.0.50 actually.
Than you might want to give more details about what you've done since
what I understood of what you've done does not result in the error
you showed.
/usr/bin/emacs -Q
M-x ielm RET
(defun ivy-config ()
(:documentation (concat "Ivy completion.\n\n" ivy-details))
(add-to-list 'load-path "~/contrib/ivy"))
RET
complains that "Symbol’s value as variable is void: ivy-details", which
indicates that it understood `:documentation` correctly (i.e. it
processed it when creating the function rather than later when we call
it).
Stefan
prev parent reply other threads:[~2022-10-16 4:07 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
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 [this message]
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=jwv4jw4ifdd.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.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.
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).