unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56744@debbugs.gnu.org
Subject: bug#56744: 29.0.50; "Autoloaded" information lost in native compilation?
Date: Sun, 20 Aug 2023 16:45:51 -0400	[thread overview]
Message-ID: <yp1cyzh8mtc.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83ttsuykzd.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 19 Aug 2023 20:56:22 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Andrea,
>
> Could you please take a look at this year-old bug report?
>
>> Date: Sun, 24 Jul 2022 19:10:03 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> 
>> 
>> To reproduce:
>> 
>>   emacs -Q
>>   C-h f rmail-movemail-variant-p RET
>> 
>> (or any other autoloaded function).  Assuming that the function's .el
>> file was already natively compiled to produce a .eln file, the
>> "autoloaded" part will not be shown in the *Help* buffer, Emacs will
>> only say that this is a native-compiled function.

On current master before requiring rmail on C-h f
rmail-movemail-variant-p RET I get:

===
rmail-movemail-variant-p is an autoloaded byte-compiled Lisp function
in ‘rmail.el’.

(rmail-movemail-variant-p &rest VARIANTS)
===

After requiring rmail (and having it native compiled) I get:

===
rmail-movemail-variant-p is an autoloaded native-compiled Lisp
function in ‘rmail.el’.

(rmail-movemail-variant-p &rest VARIANTS)

Inferred type: (function (&rest t) boolean)
===

So I guess the issue has already been fixed (or I'm not reproducing it
correctly)?

Best Regards

  Andrea





  parent reply	other threads:[~2023-08-20 20:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-24 16:10 bug#56744: 29.0.50; "Autoloaded" information lost in native compilation? Eli Zaretskii
2023-08-19 17:56 ` Eli Zaretskii
2023-08-20 10:16   ` Andrea Corallo
2023-08-20 20:45   ` Andrea Corallo [this message]
2023-08-21 12:06     ` Eli Zaretskii
2023-08-21 14:25       ` Andrea Corallo

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=yp1cyzh8mtc.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=56744@debbugs.gnu.org \
    --cc=eliz@gnu.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).