From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: "55853@debbugs.gnu.org" <55853@debbugs.gnu.org>,
Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#55853: 28.1; Please document f#(...) syntax in Elisp manual
Date: Tue, 5 Jul 2022 19:06:46 +0000 [thread overview]
Message-ID: <SJ0PR10MB54885A6CE13C0012A99D9B16F3819@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87o7y3s82o.fsf@web.de>
> > Maybe instead of (or in addition to) a disassembly, a
> > user could be pointed - a least in some cases - to the
> > original source code (Lisp or C)?
>
> Are there such cases? The place is not always well defined.
>
> In the cited original thread, when you see
>
> org-file-apps-windowsnt is a variable defined in `org.el'.
>
> in the C-h v popup you just click on the "org.el" button and are
> directly guided to the source of the byte-code function. We can't get
> much better I guess since we don't save the exact position of every
> lambda expression when compiling.
>
> If the byte-code function is named, you can click on the name that will
> likely be around. And if it has not, it's probably not trivial to find
> a related place of a definition (if there is one).
>
> So, hard to answer without a real-life example where this would
> actually be a real improvement.
Certainly there are cases where there's no reasonable
way to locate where the thing was defined. But when
there is a reasonable way it's good to point to the
definition/source code.
For cases where the name is displayed and you can
click it to go to some text with a link to the source,
there's no great problem (but perhaps getting there
could be more direct).
My point was that getting to the source code is what
a user wants more often than getting a disassembled
representation.
prev parent reply other threads:[~2022-07-05 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 16:56 bug#55853: 28.1; Please document f#(...) syntax in Elisp manual Drew Adams
2022-06-09 13:22 ` Lars Ingebrigtsen
2022-06-09 14:04 ` Drew Adams
2022-07-05 15:11 ` Michael Heerdegen
2022-07-05 15:23 ` Drew Adams
2022-07-05 18:55 ` Michael Heerdegen
2022-07-05 19:06 ` Drew Adams [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=SJ0PR10MB54885A6CE13C0012A99D9B16F3819@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=55853@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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).