From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 21724@debbugs.gnu.org
Subject: bug#21724: 25.0.50; (void-function (setf epg-context-armor))
Date: Fri, 23 Oct 2015 11:40:09 +0900 [thread overview]
Message-ID: <b4my4eutiie.fsf@jpl.org> (raw)
In-Reply-To: <b4mbnbslhjp.fsf@jpl.org>
On Thu, 22 Oct 2015 20:27:16 -0400, Glenn Morris wrote:
> Katsumi Yamaoka wrote:
>> So, I'm not quite sure why it helps, but I wrapped the existing
>> autoload settings for those functions with `eval-and-compile':
> IMO it is better to move the epg autoloads after the epg eval-when-compile.
Thanks. I see why adding (eval-when-compile (require 'epg))
caused a new warning. It marked all the epg functions including
those autoloads maybe non-existent at the run-time, didn't it?
Committed.
next prev parent reply other threads:[~2015-10-23 2:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151011210306.16935.15935@vcs.savannah.gnu.org>
[not found] ` <E1ZlNlr-0004QG-3U@vcs.savannah.gnu.org>
2015-10-13 0:36 ` master 644d31a 2/2: Replace the usage of an obsolete function in auth-source.el Katsumi Yamaoka
2015-10-21 9:03 ` bug#21724: 25.0.50; (void-function (setf epg-context-armor)) Katsumi Yamaoka
2015-10-22 23:57 ` Katsumi Yamaoka
2015-10-23 0:27 ` Glenn Morris
2015-10-23 2:40 ` Katsumi Yamaoka [this message]
2015-10-23 4:05 ` Glenn Morris
2015-11-05 20:03 ` master 644d31a 2/2: Replace the usage of an obsolete function in auth-source.el Ted Zlatanov
2015-11-06 2:22 ` Katsumi Yamaoka
2015-11-06 9:41 ` David Kastrup
2015-11-06 15:18 ` dropping support for old Emacsen (was: master 644d31a 2/2: Replace the usage of an obsolete function in auth-source.el) Ted Zlatanov
2015-11-08 15:33 ` dropping support for old Emacsen Uwe Brauer
2015-11-06 21:40 ` master 644d31a 2/2: Replace the usage of an obsolete function in auth-source.el Richard Stallman
2015-11-06 22:48 ` David Kastrup
2015-11-07 13:26 ` Richard Stallman
2015-11-07 13:43 ` David Kastrup
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=b4my4eutiie.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=21724@debbugs.gnu.org \
--cc=rgm@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.