From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Heime Newsgroups: gmane.emacs.help Subject: Re: Lisp error on function :documentation Date: Mon, 17 Oct 2022 01:01:01 +0000 Message-ID: References: <87czarfka0.fsf@web.de> <87lepfe4gr.fsf@web.de> <877d0ze3mc.fsf@web.de> <87y1tfcnkm.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26021"; mail-complaints-to="usenet@ciao.gmane.io" Cc: help-gnu-emacs@gnu.org To: Michael Heerdegen Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Mon Oct 17 03:09:18 2022 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1okEd2-0006Yj-S2 for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 17 Oct 2022 03:09:16 +0200 Original-Received: from localhost ([::1]:53000 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1okEd1-00009x-Tj for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 16 Oct 2022 21:09:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41156) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1okEVK-0001tK-7s for help-gnu-emacs@gnu.org; Sun, 16 Oct 2022 21:01:21 -0400 Original-Received: from mail-40141.protonmail.ch ([185.70.40.141]:35367) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1okEVH-0005aw-M2 for help-gnu-emacs@gnu.org; Sun, 16 Oct 2022 21:01:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1665968471; x=1666227671; bh=FJbuNxnZHWJkEXgzSzCGdJGJVWUljoHu1K2P3/hh7lA=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID; b=McLdF5tB8DmVZJSTnrPYJ/qqgPrxKCzAIN7LvoFl3ssuYX6oyZjbdY8jDBUFGz/Bo XyDl/mripIs9nw0qfOEa3tcEvzhvpZYByYobHq3ycmLN+Y6M7d14QK0ALDtP0Urq9u Os7WywKNElcQnd1KXT++FgUrre8P+iO3BER6/EI3qvNSqrnwaTt6KGE/h2jXeSE0cN SNgTDF8r0rfvigtPQMLYAohb1iltwql94L7jHTqq9byvflR3th1HH6qVkxjRMxPs8r FI4agHDYMs9Sqwxe+OQukJc/i0P4d/5kcxDiIxNNuNac+FwQiEzonGZzJ2E5Kcvri4 PsXDyQq2aJXyQ== In-Reply-To: <87y1tfcnkm.fsf@web.de> Feedback-ID: 57735886:user:proton Received-SPF: pass client-ip=185.70.40.141; envelope-from=heimeborgia@protonmail.com; helo=mail-40141.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:140043 Archived-At: ------- Original Message ------- On Monday, October 17th, 2022 at 12:15 AM, Michael Heerdegen wrote: > Heime heimeborgia@protonmail.com writes: >=20 > > Then let us hope some genius crops up and writes a solution that solves > > the impasse. >=20 >=20 > BTW, what Stefan had sent was more or less the most perfect example one > can give. You can use it as a template. You would have to get familiar > with generic functions, however. >=20 > Michael. Yes. Still, someone commented that being undocumented, it is not really suitable for use. =20 Then I started doing (defvar details "Some details here") (defun navscan () (put 'navscan 'function-documentation (concat "Set style about possible.\n\n" details)) Which seems not good either, as I picked up from the discussion. Thusly the only real solution is to call the "(put" part after defining the function. Would appreciate if people answer clearly. Being able to append a details string to the function documentation at the position where the documentation is supposed to be located (after the function name declaration), would be valuable in following the code bet= ter. =20 =20