From: David Masterson <dsmasterson@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Warning (bytecomp): reference to free variable ‘inherit’
Date: Mon, 17 Oct 2022 21:14:24 -0700 [thread overview]
Message-ID: <SJ0PR03MB5455FD0A80EBA631C034FE2DA2289@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <87wn8z2ihx.fsf@dataswamp.org> (Emanuel Berg's message of "Mon, 17 Oct 2022 06:15:22 +0200")
Emanuel Berg <incal@dataswamp.org> writes:
> David Masterson wrote:
>
>>>> It's a warning, but the buffer pop to the front at the end
>>>> of my Emacs startup and I'd like to fix that. The problem
>>>> is that the message isn't giving me a clue on what was
>>>> being byte compiled.
>>>
>>> Okey, but why are there byte-compilation at all?
>>
>> You got me. I don't see a way to trace it. Is it possible to
>> hook into byte-compile and have it print out what file it is
>> working on?
>
> Wait, the new warning pop-up buffer, I also had that, it was
> related to Tramp but that same warning exactly, and it
> disappeared when I upgraded Emacs.
>
> I have no idea what that is but maybe it isn't that byte
> compilation really occurs on startup, maybe it's just some new
> way of telling us stuff that we haven't been ... told about.
Hmm. I'll look into an upgrade.
--
David Masterson
prev parent reply other threads:[~2022-10-18 4:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 4:02 Warning (bytecomp): reference to free variable ‘inherit’ David Masterson
2022-10-14 21:01 ` Emanuel Berg
2022-10-16 18:53 ` David Masterson
2022-10-17 4:15 ` Emanuel Berg
2022-10-18 4:14 ` David Masterson [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
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=SJ0PR03MB5455FD0A80EBA631C034FE2DA2289@SJ0PR03MB5455.namprd03.prod.outlook.com \
--to=dsmasterson@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.
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).