unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 53562@debbugs.gnu.org
Subject: bug#53562: 28.0.90; Documentation of `load' and .eln files with native-compilation
Date: Thu, 27 Jan 2022 08:23:18 +0200	[thread overview]
Message-ID: <83lez1g0ix.fsf@gnu.org> (raw)
In-Reply-To: <9676e13f03287c3890d77117a7823246@webmail.orcon.net.nz> (message from Phil Sainty on Thu, 27 Jan 2022 12:25:43 +1300)

> Date: Thu, 27 Jan 2022 12:25:43 +1300
> From: Phil Sainty <psainty@orcon.net.nz>
> 
> I've noticed that the docstrings for `load' and `load-suffixes' make no
> mention of native-compilation, and it feels to me like they should do.
> 
> `load' says:
> > First try FILE with `.elc' appended, then try with `.el', then try
> > with a system-dependent suffix of dynamic modules (see `load-suffixes')
> 
> `load-suffixes' says:
> > Its value is (".so" ".elc" ".el")
> > 
> > List of suffixes for Emacs Lisp files and dynamic modules.
> > This list includes suffixes for both compiled and source Emacs Lisp 
> > files.
> 
> IIUC the switch to .eln happens only if the .elc file was selected, in
> which case the above is all true in a strict sense; but I feel that the
> .eln case warrants a mention in the text as something which further
> affects the outcome if Emacs was built --with-native-compilation.
> 
> I think `load-no-native' should be referenced as part of that, too.
> (Attempting to find that variable name was the reason for this bug
> report, and apropos-documentation suggests that nothing mentions it.)

Feel free to suggest changes to the documentation, and thanks.





      reply	other threads:[~2022-01-27  6:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 23:25 bug#53562: 28.0.90; Documentation of `load' and .eln files with native-compilation Phil Sainty
2022-01-27  6:23 ` Eli Zaretskii [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=83lez1g0ix.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53562@debbugs.gnu.org \
    --cc=psainty@orcon.net.nz \
    /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).