From: David Vanderschel <DJV5@Austin.RR.com>
To: help-gnu-emacs@gnu.org
Subject: byte-compile making erroneous *Compile Log*
Date: Fri, 29 May 2009 20:43:05 +0000 (UTC) [thread overview]
Message-ID: <loom.20090529T202456-949@post.gmane.org> (raw)
The typical message looks like the following:
eemacs.el:233:25:Warning: assignment to free variable `w32-lwindow-modifier'
The first part is a link into the file and that works fine. However, if the
'error' is found in a defun, I get something like the following:
In dv-java-keys: eemacs.el:223:9:Warning: assignment to free variable
`c-basic-offset'
and then the link does not work, because the follower logic believes that the
"In <defun-name>" is part of the file name.
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 the extra defun
identifier to appear. I thought maybe the "verbose" option for the bytecomp
group might be relevant, but no joy there. Checking other things that I thought
might be relevant, I am failing to find it. My initialization is a bit too
large to try to narrow it down by partial execution; so I am hoping that someone
has enough insight into this behaviour to point me to something that could be
causing it.
Emacs version: GNU Emacs 22.2.1 (i486-pc-linux-gnu, GTK+ Version 2.14.1) of
2008-09-05 on vernadsky, modified by Ubuntu
Running under Ubuntu 9.04.
next reply other threads:[~2009-05-29 20:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 20:43 David Vanderschel [this message]
2009-05-29 21:09 ` byte-compile making erroneous *Compile Log* Drew Adams
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
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=loom.20090529T202456-949@post.gmane.org \
--to=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.
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).