From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: pogonyshev@gmail.com, 38072@debbugs.gnu.org
Subject: bug#38072: when `byte-compile-file' finds out that a file is `no-byte-compile', it ignores `load' parameter
Date: Sat, 05 Sep 2020 09:21:02 +0300 [thread overview]
Message-ID: <834kocrbg1.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnXBW5i5WNAtvLWRDG=gwujNRW9JwLXVZ+7Y+QZ=Yae+Q@mail.gmail.com> (message from Stefan Kangas on Sat, 5 Sep 2020 00:30:38 +0000)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 5 Sep 2020 00:30:38 +0000
> Cc: 38072@debbugs.gnu.org
>
> Compile a file of Lisp code named FILENAME into a file of byte code.
> The output file’s name is generated by passing FILENAME to the
> function ‘byte-compile-dest-file’ (which see).
> With prefix arg (noninteractively: 2nd arg), LOAD the file after compiling.
> ^^^^^^^^^^^^^^^
>
> So should we load the file if we did not compile the file? I'm thinking
> yes, and I don't see what it could hurt to change it to load the file.
> If the user uses a prefix arg or the LOAD argument from Lisp, surely
> that was the intention.
>
> But on the other hand the text above seems deliberate, somehow? (And
> AFAICT the behavior has been not to load the file since pretty much
> forever, possibly since byte-compilation was first added.)
I'm indeed bothered by backward incompatibility of such a change.
Paul expected the file to be loaded unconditionally, but how do we
know someone else isn't expecting the opposite in this case? Also, do
we want the same behavior in the interactive case?
At the very least, if we decide to install this, the change in
behavior should be in NEWS.
Stefan, any comments on this?
next prev parent reply other threads:[~2020-09-05 6:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 20:58 bug#38072: when `byte-compile-file' finds out that a file is `no-byte-compile', it ignores `load' parameter Paul Pogonyshev
2020-09-05 0:30 ` Stefan Kangas
2020-09-05 6:21 ` Eli Zaretskii [this message]
2020-09-05 15:26 ` Stefan Monnier
2020-09-07 16:37 ` Stefan Kangas
2020-09-07 16:44 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-13 13:06 ` Stefan Kangas
2020-09-13 14:52 ` Eli Zaretskii
2020-09-21 22:30 ` Stefan Kangas
2020-09-22 2:28 ` Eli Zaretskii
2020-10-20 16:56 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834kocrbg1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38072@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=pogonyshev@gmail.com \
--cc=stefan@marxist.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.