* On cl-print and help-fns
@ 2017-06-30 2:10 Mark Oteiza
2017-06-30 6:11 ` Stefan Monnier
0 siblings, 1 reply; 3+ messages in thread
From: Mark Oteiza @ 2017-06-30 2:10 UTC (permalink / raw)
To: emacs-devel; +Cc: Stefan Monnier
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: On cl-print and help-fns
2017-06-30 2:10 On cl-print and help-fns Mark Oteiza
@ 2017-06-30 6:11 ` Stefan Monnier
2017-07-01 3:29 ` Noam Postavsky
0 siblings, 1 reply; 3+ messages in thread
From: Stefan Monnier @ 2017-06-30 6:11 UTC (permalink / raw)
To: emacs-devel
> 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: On cl-print and help-fns
2017-06-30 6:11 ` Stefan Monnier
@ 2017-07-01 3:29 ` Noam Postavsky
0 siblings, 0 replies; 3+ messages in thread
From: Noam Postavsky @ 2017-07-01 3:29 UTC (permalink / raw)
To: Stefan Monnier; +Cc: Emacs developers
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-07-01 3:29 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-06-30 2:10 On cl-print and help-fns Mark Oteiza
2017-06-30 6:11 ` Stefan Monnier
2017-07-01 3:29 ` Noam Postavsky
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).