unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Drew Adams <drew.adams@oracle.com>
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, 05 Jul 2022 20:55:27 +0200	[thread overview]
Message-ID: <87o7y3s82o.fsf@web.de> (raw)
In-Reply-To: <SJ0PR10MB54882ECC0190A87BE582C541F3819@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Tue, 5 Jul 2022 15:23:06 +0000")

Drew Adams <drew.adams@oracle.com> writes:

> 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.

Michael.





  reply	other threads:[~2022-07-05 18:55 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 [this message]
2022-07-05 19:06           ` Drew Adams

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=87o7y3s82o.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=55853@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=larsi@gnus.org \
    /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).