From: Thibaut Verron <thibaut.verron@gmail.com>
To: uzibalqa <uzibalqa@proton.me>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Interactive function
Date: Mon, 10 Oct 2022 16:46:40 +0200 [thread overview]
Message-ID: <a4711ecf-93d6-badb-3c29-9072e583d0f7@gmail.com> (raw)
In-Reply-To: <fLg9yZsDn2RR2LBVlwjLk2YuBuX9yCDFYCbknB3GrrE1EWfBK3iGJ0nxVKpfLT9Nw7sq7oheDeG_lMiRQHkSsrjIA6ej5qD5nKEdsLYjrss=@proton.me>
On 10/10/2022 16:23, uzibalqa wrote:
> ------- Original Message -------
> On Monday, October 10th, 2022 at 1:43 PM, <thibaut.verron@gmail.com> wrote:
>
>
>> Something like that?
>>
>> (defun function (args)
>> "Docstring"
>> (describe-function #'function))
>>
>> You should probably not show this to the compiler though.
> I do not understand the "not show to the compiler" part.
I was thinking that the compiler might take offense at the use of the
function before it is properly defined. But on second thought, it
shouldn't really be different from resolving a recursive call.
>
>
>> On 10/10/2022 15:24, uzibalqa uzibalqa@proton.me wrote:
>>
>>> I have the following function that prints some information about Emacs Init.
>>> The messages for the user are included in the function documentation part.
>>> Thusly, I would like that when the user calls "M-x emacs-init", I show the
>>> docstring. How can I implement such feature in the body of the function to
>>> call the docstring?
>>>
>>> (defun emacs-init ()
>>>
>>> "TODO.
>>>
>>> Emacs packages write their caches, histories, etc. into ~/.emacs.d/.
>>>
>>> See directory '.emacs.d' in directory
>>>
>>> ${HOME}/xepty/"
>>>
>>> (interactive)
>>>
>>> (message "See C-h f emacs-init") )
next prev parent reply other threads:[~2022-10-10 14:46 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 [this message]
2022-10-10 15:46 ` uzibalqa
2022-10-10 23:54 ` Emanuel Berg
2022-10-11 15:01 ` Michael Heerdegen
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=a4711ecf-93d6-badb-3c29-9072e583d0f7@gmail.com \
--to=thibaut.verron@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=uzibalqa@proton.me \
/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).