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: Sun, 16 Oct 2022 04:30:51 +0000 [thread overview]
Message-ID: <Bd1U7E8eAo2WoCmucY2LJgeD_klfVZkDxdxZs3VGDc8NpjTQmGkXfizT8s7CqkAf_51sFJ8EDnbcepR4gojpVrMTFJFvbkQgSazhF6lGLNU=@protonmail.com> (raw)
In-Reply-To: <87a65wz9sn.fsf@web.de>
------- Original Message -------
On Sunday, October 16th, 2022 at 4:12 AM, Michael Heerdegen <michael_heerdegen@web.de> wrote:
> Heime heimeborgia@protonmail.com writes:
>
> > Yielded the following. That's it right ?
>
>
> Depends on where you put the missing closing paren. In the correct
> version the `put' statement is not part of the defun.
I actually introduced the "put" command inside the function after the
initial docstring. And it did work.
> > But I see that the original docstring gets deleted. Any way to avoid
> > this and be able to append to the initial docstring?
>
>
> Yes - see `pcase' for example, but that requires a bit of work - and
> that stuff is also not documented. One can learn it by reading the
> examples in the sources. Not totally trivial, unfortunately.
>
> Or maybe someone has added some nicer solution in the meantime? - I
> don't recall.
>
> Michael.
It would be useful to append another string variable to the initial
docstring inside the function. Avoids functions with long docstring
parts.
You were correct about the lexical binding part.
I had
;; file.el
;; -*- lexical-binding: t; -*-
Does not seem the right way to call "lexical-binding".
Putting on the first line got the documentation correct.
;; -*- lexical-binding: t; -*-
But, perhaps it is not so good to include this undocumented feature.
next prev parent reply other threads:[~2022-10-16 4:30 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 [this message]
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
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='Bd1U7E8eAo2WoCmucY2LJgeD_klfVZkDxdxZs3VGDc8NpjTQmGkXfizT8s7CqkAf_51sFJ8EDnbcepR4gojpVrMTFJFvbkQgSazhF6lGLNU=@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).