emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: emacs-orgmode@gnu.org
Subject: Re: org-capture with org-contacts template causing problems
Date: Mon, 04 Mar 2013 11:40:15 +0100	[thread overview]
Message-ID: <8762171m9c.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <87vc98fkku.fsf@ft.bewatermyfriend.org> (Frank Terbeck's message of "Sun, 03 Mar 2013 18:40:33 +0100")

Frank Terbeck wrote:
[...]
> When using `org-capture' (and then selecting "c" in the menu window), I
> get the following error message in the "CAPTURE-contacts.org" buffer:
>
> * %![Error: (invalid-function gnus-with-article-headers)]
> :PROPERTIES:
> :EMAIL: %![Error: (invalid-function gnus-with-article-headers)]
> :END:
[...]

Turns out, this problem is triggered when I byte-compile org-contacts.el
inside my .emacs.d directory. The compilation process yields the
following warnings:

Compiling /home/hawk/.emacs.d/vendor/org-contacts.el...

In org-contacts-db-need-update-p:
vendor/org-contacts.el:169:14:Warning: function `some' from cl package called
    at runtime

In org-contacts-filter:
vendor/org-contacts.el:211:37:Warning: function `some' from cl package called
    at runtime

In org-contacts-test-completion-prefix:
vendor/org-contacts.el:373:12:Warning: function `find-if' from cl package
    called at runtime

In org-contacts-complete-name:
vendor/org-contacts.el:445:71:Warning: function `remove-duplicates' from cl
    package called at runtime

In org-contacts-gnus-insinuate:
vendor/org-contacts.el:646:15:Warning: reference to free variable
    `gnus-summary-mode-map'

In end of data:
vendor/org-contacts.el:870:1:Warning: the following functions might not be
    defined at runtime: some, find-if, remove-duplicates
vendor/org-contacts.el:870:1:Warning: the following functions are not known to
    be defined: org-reverse-string, mail-abbrev-in-expansion-header-p,
    gnus-with-article-headers, diary-ordinal-suffix, gnus-with-article-buffer,
    elmo-message-field, std11-narrow-to-header, std11-fetch-field,
    erc-get-channel-user-list, org-install-letbind, google-maps-static-show
Wrote /home/hawk/.emacs.d/vendor/org-contacts.elc


`org-capture' with the `org-contacts' template works fine if I move the
corresponding .elc file out of the way.

My guess is, that there are a few `requires' missing in the
`eval-and-compile' form on top of `org-contacts.el'. Maybe someone with
more intimate knowledge of the involved code than myself has an idea as
to how to fix this?


Regards, Frank

  reply	other threads:[~2013-03-04 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-03 17:40 org-capture with org-contacts template causing problems Frank Terbeck
2013-03-04 10:40 ` Frank Terbeck [this message]
2013-03-04 13:12   ` Frank Terbeck
2013-03-04 19:42     ` Bastien

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8762171m9c.fsf@ft.bewatermyfriend.org \
    --to=ft@bewatermyfriend.org \
    --cc=emacs-orgmode@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).