From: Stefan Kangas <stefan@marxist.se>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>
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: Mon, 7 Sep 2020 09:37:29 -0700 [thread overview]
Message-ID: <CADwFkm=ZxM_uDxXXfcmh+eAgyPqch5+SRoz79fQGX1VJpcP0xw@mail.gmail.com> (raw)
In-Reply-To: <jwvblikdzb5.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> FWIW, I find the "and load" feature to be a mistake: the function should
> return whether or not it successfully compiled the file, but shouldn't
> offer to load the result, since the callers can just as easily do
> it themselves (and then they can easily control what happens when
> compilation did not succeed).
> So, I'd suggest we deprecate that "feature" rather than try and decide
> which behavior is better.
It's pretty convenient when running interactively though. I've tried
using `C-u M-x byte-compile-file' (instead of my usual eval-buffer) for
the last couple of days, and I kind of like getting both
byte-compilation and load-file in one command.
But if we do deprecate this, is there a better alternative that we can
point users to? Should we just tell them to run two commands?
next prev parent reply other threads:[~2020-09-07 16:37 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
2020-09-05 15:26 ` Stefan Monnier
2020-09-07 16:37 ` Stefan Kangas [this message]
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
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='CADwFkm=ZxM_uDxXXfcmh+eAgyPqch5+SRoz79fQGX1VJpcP0xw@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=38072@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=pogonyshev@gmail.com \
/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).