From: Phil Sainty <psainty@orcon.net.nz>
To: Robert Irelan <rirelan@gmail.com>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
Lars Ingebrigtsen <larsi@gnus.org>,
46958@debbugs.gnu.org
Subject: bug#46958: 28.0.50; invalid-function error for macros that have function bindings
Date: Mon, 8 Mar 2021 22:06:31 +1300 [thread overview]
Message-ID: <fc8c525b-5b80-413c-72d2-16524f256bc8@orcon.net.nz> (raw)
In-Reply-To: <CAJUyYjo4DF-toBadm-745b660hMSJTsSsjkbn4F-js6Xb24GNw@mail.gmail.com>
On 8/03/21 8:18 pm, Robert Irelan wrote:
> I extracted the macros into a separate library `org-fc-macs` and then
> called `(require 'org-fc-macs)` from the file where the error is
> occurring `org-fc-type-normal.el`. This seems to have fixed the issue.
Good to hear.
I'll just add that my suggestion wasn't quite optimal -- as this is
a macros-only library, a better way to require it is:
(eval-when-compile (require 'org-fc-macs))
This ensures that macros are loaded for byte-compilation, but means
that subsequently loading the byte-compiled .elc library does *not*
load org-fc-macs (which is not needed in this scenario as, in the
byte-compiled code, the macro calls have already been expanded).
-Phil
next prev parent reply other threads:[~2021-03-08 9:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 2:00 bug#46958: 28.0.50; invalid-function error for macros that have function bindings Robert Irelan
2021-03-06 12:55 ` Lars Ingebrigtsen
2021-03-06 14:24 ` Basil L. Contovounesios
2021-03-06 18:28 ` Robert Irelan
2021-03-06 22:39 ` Phil Sainty
2021-03-07 14:27 ` Basil L. Contovounesios
2021-03-07 21:38 ` Robert Irelan
2021-03-08 6:30 ` Phil Sainty
2021-03-08 7:18 ` Robert Irelan
2021-03-08 9:06 ` Phil Sainty [this message]
2022-06-20 1:10 ` Lars Ingebrigtsen
2021-03-07 14:33 ` Pip Cet
2021-03-07 15:58 ` Lars Ingebrigtsen
2021-03-07 18:06 ` Pip Cet
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=fc8c525b-5b80-413c-72d2-16524f256bc8@orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=46958@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=larsi@gnus.org \
--cc=rirelan@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).