From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: On cl-print and help-fns Date: Fri, 30 Jun 2017 02:11:55 -0400 Message-ID: References: <20170630021020.GA27460@holos.localdomain> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1498803142 11484 195.159.176.226 (30 Jun 2017 06:12:22 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 30 Jun 2017 06:12:22 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 30 08:12:17 2017 Return-path: Envelope-to: ged-emacs-devel@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 1dQpA8-0002fv-AZ for ged-emacs-devel@m.gmane.org; Fri, 30 Jun 2017 08:12:16 +0200 Original-Received: from localhost ([::1]:42677 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dQpAD-0007T1-En for ged-emacs-devel@m.gmane.org; Fri, 30 Jun 2017 02:12:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44035) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dQpA3-0007RT-HU for emacs-devel@gnu.org; Fri, 30 Jun 2017 02:12:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dQpA0-0002xQ-C7 for emacs-devel@gnu.org; Fri, 30 Jun 2017 02:12:11 -0400 Original-Received: from [195.159.176.226] (port=38916 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dQpA0-0002wT-5R for emacs-devel@gnu.org; Fri, 30 Jun 2017 02:12:08 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dQp9o-0001fX-WE for emacs-devel@gnu.org; Fri, 30 Jun 2017 08:11:56 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 18 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:P4Nr8O4NQ6m+4vcm/KnFCn3hJmI= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:216058 Archived-At: > While cl-print is a nice feature, I am puzzled why its use in the help > buffer is neither documented nor configurable. > https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=2c18969c8 > I think that "Its value is #f(compiled-function () #)", while > less messy, is less useful than just seeing the bytecode, as the bytecode > would at least give me a clue. The cl-prin1-to-string output is opaque. Maybe we should default cl-print-compiled to `static`, so as to hide the byte-code, but still show the constants used in the code? Stefan PS: Oh, and IIUC in the latest version of the code, you might be able to click on the # to see a disassembly of the code.