From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.bugs Subject: bug#60568: [FR] 30.0.50; Help buffers and function bodies for generated functions Date: Thu, 5 Jan 2023 20:04:40 +0300 Message-ID: References: <87fscpifdw.fsf@localhost> <83a62xxuzs.fsf@gnu.org> <877cy1ie9m.fsf@localhost> <835ydlxtyy.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5732"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.2.9+54 (af2080d) (2022-11-21) Cc: Ihor Radchenko , 60568@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jan 05 18:28:39 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 1pDU2h-0001HC-Ee for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 05 Jan 2023 18:28:39 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pDThv-0007dU-OH; Thu, 05 Jan 2023 12:07:11 -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 1pDTho-0007Vv-AZ for bug-gnu-emacs@gnu.org; Thu, 05 Jan 2023 12:07: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 1pDThn-0006W7-C7 for bug-gnu-emacs@gnu.org; Thu, 05 Jan 2023 12:07:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pDThn-0006t2-6v for bug-gnu-emacs@gnu.org; Thu, 05 Jan 2023 12:07:03 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Jean Louis Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 05 Jan 2023 17:07:03 +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.167293839526418 (code B ref 60568); Thu, 05 Jan 2023 17:07:03 +0000 Original-Received: (at 60568) by debbugs.gnu.org; 5 Jan 2023 17:06:35 +0000 Original-Received: from localhost ([127.0.0.1]:52724 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pDThK-0006s1-SZ for submit@debbugs.gnu.org; Thu, 05 Jan 2023 12:06:35 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:46419) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pDThJ-0006rA-84 for 60568@debbugs.gnu.org; Thu, 05 Jan 2023 12:06:33 -0500 Original-Received: from localhost ([::ffff:102.85.153.82]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 0000000000055EB5.0000000063B7039B.00002222; Thu, 05 Jan 2023 10:06:35 -0700 Content-Disposition: inline In-Reply-To: <835ydlxtyy.fsf@gnu.org> 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:252616 Archived-At: * Eli Zaretskii [2023-01-05 11:33]: > > From: Ihor Radchenko > > Cc: 60568@debbugs.gnu.org > > Date: Thu, 05 Jan 2023 08:20:21 +0000 > > > > Eli Zaretskii writes: > > > > >> Would it be possible to provide function body info via *Help* system in > > >> Emacs? > > > > > > Provide how? > > > > For example, clicking source code link for function without definition > > may display a new separate buffer with function body stored in the > > function symbol. > > That is less desirable, IMO, then teaching Help commands to be smarter > with showing the source code. One of the main reasons to go to the > source code is to examine the surrounding code, and consider the > function in its context. This will be impossible with your proposal. It would be better to find the place where generated functions have been generated. But not bad, to show how function looks like in same time. 1. Help buffer, with button link 2. Link goes to source, but if it does not find function, it shows where it was generated and pops up temporary buffer with function definition using `symbol-function' -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/