From: Lars Ingebrigtsen <larsi@gnus.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 33164@debbugs.gnu.org
Subject: bug#33164: Compiled function value information in *Help*
Date: Wed, 23 Jun 2021 16:05:17 +0200 [thread overview]
Message-ID: <87bl7wllr6.fsf_-_@gnus.org> (raw)
In-Reply-To: <877ei2jj5a.fsf@gmail.com> (Noam Postavsky's message of "Sun, 28 Oct 2018 09:27:45 -0400")
Noam Postavsky <npostavs@gmail.com> writes:
>> But it is less helpful than what we had back in Emacs 23, which printed
>> the name or the lambda expression of the function that is the value of
>> the variable. Examples:
>>
>> comment-line-break-function is a variable defined in `simple.el'.
>> Its value is comment-indent-new-line
>
> This one is still the same in newer Emacs versions.
>
>> But just showing the byte code, even disassembled, is not so helpful.
>> What if a user wants to go to the function definition, to use it as a
>> model for defining a new value for the variable or just to study it?
>
> Similarly, C-h v float-pi tells me
>
> float-pi is a variable defined in ‘float-sup.el’.
> Its value is 3.141592653589793
>
> It doesn't show me (* 4 (atan 1)) for study.
The help buffer shows the actual value of the variable, which may be
set somewhere else than it has been defined. It's not feasible for the
Emacs help system to take you to all locations a variable has been
changed, so I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-06-23 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 15:05 bug#33164: 26.1; Compiled function information in *Help* Drew Adams
2018-10-28 13:27 ` Noam Postavsky
2018-10-28 14:17 ` Drew Adams
2021-06-23 14:05 ` Lars Ingebrigtsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bl7wllr6.fsf_-_@gnus.org \
--to=larsi@gnus.org \
--cc=33164@debbugs.gnu.org \
--cc=npostavs@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).