From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Interactive function
Date: Tue, 11 Oct 2022 17:01:23 +0200 [thread overview]
Message-ID: <874jwao14s.fsf@web.de> (raw)
In-Reply-To: 87fsfvz132.fsf@dataswamp.org
Emanuel Berg <incal@dataswamp.org> writes:
> But it seems you cannot do
>
> (describe-function #'#')
So to say, the reader macro #' requires an argument (i.e. the following
form), and the inner one above doesn't provide one, so you get a read
error.
Michael.
next prev parent reply other threads:[~2022-10-11 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 13:24 Interactive function uzibalqa
2022-10-10 13:43 ` thibaut.verron
2022-10-10 14:23 ` uzibalqa
2022-10-10 14:46 ` Thibaut Verron
2022-10-10 15:46 ` uzibalqa
2022-10-10 23:54 ` Emanuel Berg
2022-10-11 15:01 ` Michael Heerdegen [this message]
2022-10-10 23:42 ` Emanuel Berg
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=874jwao14s.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).