[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: pacifying "might not be defined at runtime" warning

From: Paul Eggert
Subject: Re: pacifying "might not be defined at runtime" warning
Date: Mon, 9 May 2016 09:35:41 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0

On 05/09/2016 05:20 AM, Stefan Monnier wrote:
vc-<backend>.el is autoloaded as soon as you visit
a file that's managed by <backend>, even if you never have and never
will use VC, so a (require 'vc) in those files would load VC
too eagerly.

Thanks for explaining. What is the recommended way to pacify the byte compiler in this situation? I tried prepending (eval-when-compile (require 'vc)) to vc-bzr.el, but that doesn’t suffice, as the byte-compiler still complains “vc/vc-bzr.el:1337:1:Warning: the function ‘vc-deduce-fileset’ might not be defined at runtime.”

reply via email to

[Prev in Thread] Current Thread [Next in Thread]