unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 58314@debbugs.gnu.org, monnier@iro.umontreal.ca,
	bugs@gnu.support, akrl@sdf.org
Subject: bug#58314: 29.0.50; C-h k with native compilation not conclusive
Date: Thu, 06 Oct 2022 17:28:00 +0300	[thread overview]
Message-ID: <83o7upowlr.fsf@gnu.org> (raw)
In-Reply-To: <874jwhyw1n.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu,  06 Oct 2022 14:29:56 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Eli Zaretskii <eliz@gnu.org>,  58314@debbugs.gnu.org,  Stefan Monnier
>  <monnier@iro.umontreal.ca>, Andrea Corallo <akrl@sdf.org>
> Date: Thu, 06 Oct 2022 14:29:56 +0200
> 
> Jean Louis <bugs@gnu.support> writes:
> 
> > 1. emacs -Q
> >
> > 2. {C-x C-f my-file.el RET}
> >
> > 3. write in my-file.el:
> >
> >   (defun my-function ()
> >   (message "Hello"))
> >
> > 4. {M-x emacs-lisp-native-compile-and-load RET}
> >
> > 5. {C-h f my-function RET}
> >
> > 6. Then I see:
> >
> > my-function is a native-compiled Lisp function in
> > ‘~/.emacs.d/eln-cache/29.0.50-44cd31c8/my-file-fb862712-14785989.eln’.
> 
> Thanks for the recipe -- I can reproduce this issue, too.
> 
> We could fix this in help-fns, but I wonder whether there's something
> that should be fixed on the nativecomp side -- in this case, it appears
> to not set up...  something...  that allows you to find my-file.el.
> I.e., `symbol-file' isn't able to find my-file.el, and it probably
> should be?

It is also interesting that help-fns does find the .el file for the
files that are part of Emacs.  So something works differently when the
compiled file is not part of the Emacs build.





  reply	other threads:[~2022-10-06 14:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 19:26 bug#58314: 29.0.50; C-h k with native compilation not conclusive Jean Louis
2022-10-05 19:45 ` Eli Zaretskii
2022-10-05 19:50   ` Jean Louis
2022-10-06 12:29     ` Lars Ingebrigtsen
2022-10-06 14:28       ` Eli Zaretskii [this message]
2023-06-05 22:49         ` Andrea Corallo
2023-06-06 10:24           ` Andrea Corallo
2022-10-05 19:55 ` Jean Louis

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=83o7upowlr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58314@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=bugs@gnu.support \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).