unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 58314@debbugs.gnu.org
Subject: bug#58314: 29.0.50; C-h k with native compilation not conclusive
Date: Wed, 05 Oct 2022 22:45:41 +0300	[thread overview]
Message-ID: <83bkqqrr4q.fsf@gnu.org> (raw)
In-Reply-To: <86czb65axv.fsf@protected.rcdrun.com> (message from Jean Louis on Wed, 05 Oct 2022 22:26:20 +0300)

> From: Jean Louis <bugs@gnu.support>
> Date: Wed, 05 Oct 2022 22:26:20 +0300
> 
> 
> I remember with byte compiling I was never lead to go into byte compiled
> file when I was inspecting commands with C-h k
> 
> With native compilation, I do: C-h k and I get this:
> 
> v n runs the command cf-people-view-notes (found in
> rcd-db-people-mode-map), which is an interactive native-compiled Lisp
> function in
> ‘../eln-cache/29.0.50-44cd31c8/rcd-cf-a9476332-a313d4ff.eln’.
> 
> It is bound to v n.

I cannot reproduce this.  I don't have rcd-cf.el here, of course, but
I tested with "C-h k n" in Help mode, and I see the expected:

  n runs the command help-goto-next-page (found in help-mode-map), which
  is an interactive native-compiled Lisp function in ‘help-mode.el’.

So this is somehow related to your own files.  Maybe it's because how
we store the doc strings or something?  Stefan, any ideas?





  reply	other threads:[~2022-10-05 19:45 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 [this message]
2022-10-05 19:50   ` Jean Louis
2022-10-06 12:29     ` Lars Ingebrigtsen
2022-10-06 14:28       ` Eli Zaretskii
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=83bkqqrr4q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58314@debbugs.gnu.org \
    --cc=bugs@gnu.support \
    --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).