From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#60568: [FR] 30.0.50; Help buffers and function bodies for generated functions Date: Sat, 07 Jan 2023 17:23:01 +0200 Message-ID: <831qo6s71m.fsf@gnu.org> References: <87fscpifdw.fsf@localhost> <83wn61w7lc.fsf@gnu.org> <8dea9f3e0e7865d8f3c6@heytings.org> <83r0w9vzgy.fsf@gnu.org> <8dea9f3e0e8e6114ffc3@heytings.org> <83pmbtvwyr.fsf@gnu.org> <8dea9f3e0e160e17818f@heytings.org> <83mt6xvsct.fsf@gnu.org> <8dea9f3e0ea1de84c49a@heytings.org> <83cz7sw4q1.fsf@gnu.org> <371ba1d0beb0ed44a9a6@heytings.org> <371ba1d0be96347bdf60@heytings.org> <83k01yu93p.fsf@gnu.org> <6538f58eb5cc153a2250@heytings.org> <874jt2lb1t.fsf@localhost> <6538f58eb5857d2eb07b@heytings.org> <87sfgmjscq.fsf@localhost> <83358ms7gl.fsf@gnu.org> <87mt6ujrtb.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22291"; mail-complaints-to="usenet@ciao.gmane.io" Cc: gregory@heytings.org, mardani29@yahoo.es, monnier@iro.umontreal.ca, 60568@debbugs.gnu.org To: Ihor Radchenko Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jan 07 16:23:15 2023 Return-path: Envelope-to: geb-bug-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 1pEB2Q-0005bG-SG for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 07 Jan 2023 16:23:15 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pEB2I-0000zN-Ay; Sat, 07 Jan 2023 10:23:06 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pEB2E-0000yI-N7 for bug-gnu-emacs@gnu.org; Sat, 07 Jan 2023 10:23:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pEB2E-0004Pg-Es for bug-gnu-emacs@gnu.org; Sat, 07 Jan 2023 10:23:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pEB2E-0005Ro-AF for bug-gnu-emacs@gnu.org; Sat, 07 Jan 2023 10:23:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 07 Jan 2023 15:23:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 60568 X-GNU-PR-Package: emacs Original-Received: via spool by 60568-submit@debbugs.gnu.org id=B60568.167310497020902 (code B ref 60568); Sat, 07 Jan 2023 15:23:02 +0000 Original-Received: (at 60568) by debbugs.gnu.org; 7 Jan 2023 15:22:50 +0000 Original-Received: from localhost ([127.0.0.1]:58732 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pEB21-0005R4-Ht for submit@debbugs.gnu.org; Sat, 07 Jan 2023 10:22:49 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:37258) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pEB1z-0005Qr-Py for 60568@debbugs.gnu.org; Sat, 07 Jan 2023 10:22:48 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pEB1u-0004M3-FW; Sat, 07 Jan 2023 10:22:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=HUTp2s3+62hHoDhlUE968mRprR42yk4Kqn0ualP2njE=; b=Rfb9rRVAJCBHxhjQYxlH J8+aEnhfzoqJPTrjnn3DGdg0/msUE+yE8oTcoH7Gsz/XmvsVUAJvFZ5lbcpu2tFNKuTRAJaCLI15J odCpxHAlQ0H59b4T0ZfzLQIQk+ZyPdlzZwSEWm18RelR/jY3XopF5vwqBtfeN7mWgLXeCMafruJbF tFw1S3q6AWUGObkuHeSmpYrS2DMaG3ZjIKnK+4iCyCOpGIHgzIwVUINqYXZwdlEZO6NViGD9MoGMP +z3gXCLF7jaKR8zjCY0O3pxUrPB1dO9jLeAh5ArAKN+EuXrI24OJ4AENdhYSYY5N+WJC4aXQy5YvK 0zH8ijAivCbaOA==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pEB1t-00052U-Lh; Sat, 07 Jan 2023 10:22:41 -0500 In-Reply-To: <87mt6ujrtb.fsf@localhost> (message from Ihor Radchenko on Sat, 07 Jan 2023 15:19:12 +0000) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:252812 Archived-At: > From: Ihor Radchenko > Cc: gregory@heytings.org, monnier@iro.umontreal.ca, 60568@debbugs.gnu.org, > mardani29@yahoo.es > Date: Sat, 07 Jan 2023 15:19:12 +0000 > > Eli Zaretskii writes: > > >> Then, may "13.4 Defining Functions" be a good place to link to this > >> subtlety? > >> > >> The documentation for `defalias' is not really very clear, even now, > >> when I am aware about the issue herein: > >> > >> The proper place to use ‘defalias’ is where a specific function or > >> macro name is being defined—especially where that name appears > >> explicitly in the source file being loaded. This is because > >> ‘defalias’ records which file defined the function, just like > >> ‘defun’ (*note Unloading::). > >> > >> By contrast, in programs that manipulate function definitions for > >> other purposes, it is better to use ‘fset’, which does not keep > >> such records. *Note Function Cells::. > > > > FWIW, I don't see anything unclear here. Moreover, what does defalias > > have to do with the issue of links to code of generated functions? > > The above says that `defalias' "records which file defined the > function". It appears to be related to what we are discussing here - > locating the function definition. Tangentially at best. > However, the present manual description does not talk what "records" > refers to. I presume that the records are to be used by *Help* system. > If so, it also makes sense to elaborate. Either here, or in other node > linked from here. We must find a better place. And the main problem is not where to document this (its natural place is where all the standard properties are described), the main problem is how to index it so that people could easily find it. Also, where else to mention that property in the manual, in related context. We don't seem to have anything about generating code...