all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Heime <heimeborgia@protonmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Lisp error on function :documentation
Date: Mon, 17 Oct 2022 01:43:39 +0200	[thread overview]
Message-ID: <877d0ze3mc.fsf@web.de> (raw)
In-Reply-To: <uushyaQMae-aYEMJRwVFr81sNKZK2tAlk5SgdI-tiOk7AushcnbRCdfviYKcsTC7HC0UyqcZZkQo_XSMNK_5K9BWZ6GV2nKp6-9jyHNstKA=@protonmail.com> (Heime's message of "Sun, 16 Oct 2022 23:39:03 +0000")

Heime <heimeborgia@protonmail.com> writes:

> Anyway.  There is no easy and straightforward way to add a predefined
> string to a brief documentation string which is documented.  It seems.

Exactly that.  And what would it help if we send you some code you would
not understand?  You don't want or don't have time learn that all, and I
don't have time to work that all out.

Michael.



  reply	other threads:[~2022-10-16 23:43 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877d0ze3mc.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.