On cl-print and help-fns

On cl-print and help-fns

[Mark Oteiza]

Hi,

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 () #<bytecode>)", 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.

Re: On cl-print and help-fns

[Stefan Monnier]

> 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 () #<bytecode>)", 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 #<bytecode> to see a disassembly of the code.

Re: On cl-print and help-fns

[Noam Postavsky]

On Fri, Jun 30, 2017 at 2:11 AM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
> PS: Oh, and IIUC in the latest version of the code, you might be
> able to click on the #<bytecode> to see a disassembly of the code.

You can now.

[1: 23ff664fd2]: 2017-06-30 23:30:07 -0400
  * lisp/help-fns.el (describe-variable): Let-bind cl-print-compiled-button.
  http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=23ff664fd24dbdd8cc5b9d1fb68423fe6592b0a0