all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Mastro <john.b.mastro@gmail.com>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Cc: hector <hectorlahoz@gmail.com>
Subject: Re: unexpected byte-compiler behaviour
Date: Thu, 9 Mar 2017 15:28:50 -0800	[thread overview]
Message-ID: <CAOj2CQSv=T_bWhDciddo_JJHuwA6PYsMmfZ7X8RBk=aaHcG3RA@mail.gmail.com> (raw)
In-Reply-To: <20170309224944.GA3148@workstation>

hector <hectorlahoz@gmail.com> wrote:
> So basically linking is done, not at compilation like in C, but
> dynamically at run time. I think I get it. Thanks a lot.

Yeah, I think that's a fair description.

> Could it be that my environment (loaded libraries) is affecting
> compilation? Is it advisable to run Emacs with -Q?

Emacs's state can definitely affect compilation, and when macros are
involved it can get a little subtle/confusing.

It's not necessary to use "emacs -Q" on a regular basis (I suspect most
people only do that when debugging a specific problem in a minimal
environment), but it can definitely be helpful to use it for compilation
sometimes (especially after large changes, especially involving macros
used in different files than where they were defined).

To do that, you could either launch an "emacs -Q" and then use e.g.
byte-recompile-directory, or install the async package and call
async-byte-recompile-directory, which will launch an "emacs -Q" in the
background.

        John



      reply	other threads:[~2017-03-09 23:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 17:46 unexpected byte-compiler behaviour hector
2017-03-09 18:18 ` John Mastro
2017-03-09 18:20   ` John Mastro
2017-03-09 19:17     ` hector
2017-03-09 19:25   ` hector
2017-03-09 21:55     ` John Mastro
2017-03-09 22:49       ` hector
2017-03-09 23:28         ` John Mastro [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOj2CQSv=T_bWhDciddo_JJHuwA6PYsMmfZ7X8RBk=aaHcG3RA@mail.gmail.com' \
    --to=john.b.mastro@gmail.com \
    --cc=hectorlahoz@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.