From: "Drew Adams" <drew.adams@oracle.com>
To: "'David Vanderschel'" <DJV5@Austin.RR.com>, <help-gnu-emacs@gnu.org>
Subject: RE: byte-compile making erroneous *Compile Log*
Date: Fri, 29 May 2009 14:09:32 -0700 [thread overview]
Message-ID: <FAC05AFA990D43B2B08129789D0CC2AC@us.oracle.com> (raw)
In-Reply-To: <loom.20090529T202456-949@post.gmane.org>
> Now this does not happen when I start Emacs with "emacs -Q".
> So I am trying without luck to figure out what in my
> initialization is causing...
> My initialization is a bit too large to try to narrow it down
> by partial execution...
No, it's not too large. What you need to do (unless someone here has a direct
answer for your problem) is to look for the problem using _binary_ search.
This a very quick way to locate the problem. Remember the story of the King's
agreement to give a bargainer one grain of rice for the first square of a
checkerboard, 2 grains for the second square, 4 grains for the third square, and
so on. Doubling or halving something picks up steam very quickly
(exponentially!).
By commenting out sections of your init file (use `M-x comment-region', which
you might want to bind to a key - I use `C-x C-:') and uncommenting them (just
use `C-u' with `comment-region'), split your init file up, in effect, to find
the problem. Split it in two. Then split the problematic half in two. Then split
the problematic quarter in two. Then the problematic eigth. And so on.
In no time at all, you will locate the specific part in your init file that
leads to your problem - no matter how big the file is. When you start doing
this, it might seem primitive, but it soon takes off. The key is to have a quick
way to comment out and uncomment a section of code. (Alternatively, you can use
`eval-region'.)
next prev parent reply other threads:[~2009-05-29 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 20:43 byte-compile making erroneous *Compile Log* David Vanderschel
2009-05-29 21:09 ` Drew Adams [this message]
2009-05-29 22:50 ` David Vanderschel
-- strict thread matches above, loose matches on Subject: below --
2009-05-30 9:52 martin rudalics
2009-05-31 5:17 ` David Vanderschel
2009-05-31 11:40 martin rudalics
2009-06-02 0:36 ` David Vanderschel
2009-06-02 6:23 martin rudalics
[not found] ` <000401c9e4da$2e106680$650aa8c0@austin.rr.com>
[not found] ` <4A2773E2.9030001@gmx.at>
2009-06-05 8:16 ` David Vanderschel
2009-06-05 9:26 ` martin rudalics
2009-06-06 0:02 ` David Vanderschel
2009-06-06 8:21 ` martin rudalics
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=FAC05AFA990D43B2B08129789D0CC2AC@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=DJV5@Austin.RR.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.