From: Dmitry Gutov <dgutov@yandex.ru>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] master 5e43955 1/2: Don't declare vc-exec-after anymore
Date: Thu, 22 Oct 2015 15:08:37 +0300 [thread overview]
Message-ID: <5628D1C5.4070300@yandex.ru> (raw)
In-Reply-To: <CAAeL0STEg9P4GgT_XFJh_J0SexBnoT_Vh_=muMxsQYVBoNW-xA@mail.gmail.com>
Hi Juanma,
On 10/22/2015 11:05 AM, Juanma Barranquero wrote:
> > branch: master
> > commit 5e4395544c184d9a8702cf05c7aee9329b0b9482
> > Author: Dmitry Gutov <dgutov@yandex.ru <mailto:dgutov@yandex.ru>>
> > Commit: Dmitry Gutov <dgutov@yandex.ru <mailto:dgutov@yandex.ru>>
> >
> > Don't declare vc-exec-after anymore
...
> After this change, compiling vc-mtn.el, vc-git.el and vc-bzr.el give
> warnings (the other three don't):
Thank you for pointing that out. Any idea why that happens?
> trunk@C:\...\vc> for %i in (svn mtn hg cvs git bzr) do emacs -batch -Q
> -f batch-byte-compile vc-%i.el
>
> In end of data:
> vc-mtn.el:378:1:Warning: the function `vc-exec-after' might not be
> defined at
> runtime.
No direct calls to vc-exec-after appear in any of these files anymore.
All of them call vc-run-delayed, yet, as you say, the warning is
displayed only when compiling some of them.
I'd think that if the compiler has gotten around to expanding
vc-run-delayed, it must have already loaded vc-dispatcher. And then it
also knows there vc-exec-after is defined.
next parent reply other threads:[~2015-10-22 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151020190758.14547.6515@vcs.savannah.gnu.org>
[not found] ` <E1ZocGN-0003nd-DB@vcs.savannah.gnu.org>
[not found] ` <CAAeL0STEg9P4GgT_XFJh_J0SexBnoT_Vh_=muMxsQYVBoNW-xA@mail.gmail.com>
2015-10-22 12:08 ` Dmitry Gutov [this message]
2015-10-22 12:25 ` [Emacs-diffs] master 5e43955 1/2: Don't declare vc-exec-after anymore Juanma Barranquero
2015-10-22 15:04 ` Eli Zaretskii
2015-10-23 7:29 ` Eli Zaretskii
2015-10-23 13:38 ` Dmitry Gutov
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=5628D1C5.4070300@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
/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.