From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.bugs Subject: bug#33164: 26.1; Compiled function information in *Help* Date: Sun, 28 Oct 2018 07:17:29 -0700 (PDT) Message-ID: <0e796704-669a-4c58-9530-cd810d56494e@default> References: <877ei2jj5a.fsf@gmail.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1540736175 21411 195.159.176.226 (28 Oct 2018 14:16:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 28 Oct 2018 14:16:15 +0000 (UTC) Cc: 33164@debbugs.gnu.org To: Noam Postavsky Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Oct 28 15:16:10 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gGlrO-0005U6-AE for geb-bug-gnu-emacs@m.gmane.org; Sun, 28 Oct 2018 15:16:10 +0100 Original-Received: from localhost ([::1]:40299 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gGltU-0002eq-Jp for geb-bug-gnu-emacs@m.gmane.org; Sun, 28 Oct 2018 10:18:20 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43508) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gGltI-0002el-CR for bug-gnu-emacs@gnu.org; Sun, 28 Oct 2018 10:18:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gGltC-0002Zc-RX for bug-gnu-emacs@gnu.org; Sun, 28 Oct 2018 10:18:08 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:44911) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gGltC-0002ZI-Aa for bug-gnu-emacs@gnu.org; Sun, 28 Oct 2018 10:18:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gGltC-0005wm-0D for bug-gnu-emacs@gnu.org; Sun, 28 Oct 2018 10:18:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Drew Adams Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 28 Oct 2018 14:18:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 33164 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 33164-submit@debbugs.gnu.org id=B33164.154073626222833 (code B ref 33164); Sun, 28 Oct 2018 14:18:01 +0000 Original-Received: (at 33164) by debbugs.gnu.org; 28 Oct 2018 14:17:42 +0000 Original-Received: from localhost ([127.0.0.1]:49169 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gGlss-0005wD-JG for submit@debbugs.gnu.org; Sun, 28 Oct 2018 10:17:42 -0400 Original-Received: from userp2120.oracle.com ([156.151.31.85]:43488) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gGlso-0005vv-8A for 33164@debbugs.gnu.org; Sun, 28 Oct 2018 10:17:38 -0400 Original-Received: from pps.filterd (userp2120.oracle.com [127.0.0.1]) by userp2120.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w9SE8cuK064117; Sun, 28 Oct 2018 14:17:32 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : cc : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2018-07-02; bh=i/4MYclhERilBgXYuparIM1jmlAojEupJmPspsJLTRA=; b=bDm2QOGyEKS0edXQAqYQss9WDRByx7Vr7TRncB18YNVh1CqurQ5dhePEco2TAtoEsX3w z7pJZRzDPtoABsRZNL3Kd9RFdp80BWskP/OGsbuQI7lxFZKhG/5PQwrONJJ0IR8oErBD JgMyEH63vTmTrvrn2Tkya1YzPqgBoRxYMvWwuMhJudmKBuJ+wN55kTtthVGlnDPirFoj OQXb0D/2gpIjkJujAhNNqmtG5afWPRwntHExmiGHeeDiOEn3mpVDQXO+jYd80Hl2zps2 ioA0kx32MFTA0rwVKE5FlqeoVz9lWzWTN2/gZdbYd2ZNnh1kyfTeOKqOTxOuVrgtdVJc 8g== Original-Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by userp2120.oracle.com with ESMTP id 2ncgnqj8jm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sun, 28 Oct 2018 14:17:32 +0000 Original-Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id w9SEHVlq015592 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sun, 28 Oct 2018 14:17:31 GMT Original-Received: from abhmp0012.oracle.com (abhmp0012.oracle.com [141.146.116.18]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id w9SEHUO9012740; Sun, 28 Oct 2018 14:17:31 GMT In-Reply-To: <877ei2jj5a.fsf@gmail.com> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.4756.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9059 signatures=668683 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=854 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810280133 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:151744 Archived-At: > In this case, the link to `simple.el' takes you there because it's the > default value. But in general, no, that information is not saved > anywhere. Yes, what you say makes sense. I guess I am wondering whether the byte-compiler might (be made to) record the source in the byte-compiled function definition. A byte-compiled file records the absolute name of the source file, as well as the Emacs release/build and the time of the compilation (creation of the .elc). Perhaps some "source" location information could be recorded in the byte-code, and be retrievable by a help function? In the case of a source definition in a file, the info could be similar to what we record in a .elc. But perhaps even if the source code were in a buffer, or even via `M-:', perhaps some textual indication/description of that source could be recorded, along with the date & time. Just a thought. Yes, that would increase byte-code size, and it should anyway be optional I guess. But it might allow for a little more introspection than what we can get now (disassembled code). If you want to recast this bug report as an enhancement request along those lines, perhaps (again) retitling, please do so. > The easiest fix is to say we should never assign anonymous functions to > variables (there have already been a couple of cases where some > anonymous function values were given names), so then they would all show > a symbol like comment-line-break-function. That would not be something I'd ask for or appreciate. I want to be able to get more info about existing function values, not reduce the types of function values we can assign to variables. It can be helpful for help functions if someone uses a symbol (providing a name and perhaps a source location), but users need to be able to define and assign code as values on the fly. The idea of this report is to ask for possible improvement in the introspection of byte-code values - specifically time and location of definition.