From: Jake <jake.waksbaum@gmail.com>
To: "monnier@iro.umontreal.ca" <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Changing a cl-defstruct definition in a published package
Date: Thu, 19 Jul 2018 16:27:19 -0400 [thread overview]
Message-ID: <CAAE4Qitj2KnWqpAiKNsGo1w699dDd8vD3GcWPZPr4uxgSx4XeA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
I've seen another work around to detect whether or not a file is being
byte-compiled in use-package
<https://github.com/jwiegley/use-package/blob/master/use-package-ensure.el#L192-L197>:
(bound-and-true-p byte-compile-current-file).
It seems to work, as illustrated by this example:
(message
(eval-when-compile
(if (bound-and-true-p byte-compile-current-file)
"I'm being byte-compiled!"
"I'm being evaluated :(")))
When I byte compile that and then evaluate
(progn
(load-file "~/byte-compile-test.elc")
(load-file "~/byte-compile-test.el"))
It prints out
Loading /Users/jake.waksbaum/byte-compile-test.elc...
I’m being byte-compiled!
Loading /Users/jake.waksbaum/byte-compile-test.elc...done
Loading /Users/jake.waksbaum/byte-compile-test.el (source)...
I’m being evaluated :(
Loading /Users/jake.waksbaum/byte-compile-test.el (source)...done
t
[-- Attachment #2: Type: text/html, Size: 1805 bytes --]
next reply other threads:[~2018-07-19 20:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 20:27 Jake [this message]
2018-07-19 21:10 ` Changing a cl-defstruct definition in a published package Stefan Monnier
2018-07-19 21:34 ` Jake
-- strict thread matches above, loose matches on Subject: below --
2018-07-12 20:12 Clément Pit-Claudel
2018-07-13 17:01 ` João Távora
2018-07-13 17:38 ` Basil L. Contovounesios
2018-07-13 18:21 ` Clément Pit-Claudel
2018-07-13 18:26 ` Clément Pit-Claudel
2018-07-13 19:38 ` João Távora
2018-07-13 19:52 ` Clément Pit-Claudel
2018-07-13 20:40 ` Stefan Monnier
2018-07-13 21:07 ` Clément Pit-Claudel
2018-07-14 3:36 ` Stefan Monnier
2018-07-15 4:25 ` Clément Pit-Claudel
2018-07-15 13:11 ` Stefan Monnier
2018-07-15 13:25 ` Clément Pit-Claudel
2018-07-16 1:51 ` Stefan Monnier
2018-07-30 21:52 ` Clément Pit-Claudel
2018-07-30 22:49 ` Stefan Monnier
2018-07-31 3:28 ` Clément Pit-Claudel
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=CAAE4Qitj2KnWqpAiKNsGo1w699dDd8vD3GcWPZPr4uxgSx4XeA@mail.gmail.com \
--to=jake.waksbaum@gmail.com \
--cc=emacs-devel@gnu.org \
--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).