From: Sebastian Rose <sebastian_rose@gmx.de>
To: Nathan Neff <nathan.neff@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Org-jekyll - org-publish-initialize-files-alist
Date: Wed, 30 Jun 2010 13:45:57 +0200 [thread overview]
Message-ID: <87bpas7ngq.fsf@gmx.de> (raw)
In-Reply-To: <AANLkTim6trg8dkOrJKlcLMyLB0CABjqo5g6Whf7H4wFM@mail.gmail.com> (Nathan Neff's message of "Tue, 29 Jun 2010 17:45:39 -0500")
Nathan Neff <nathan.neff@gmail.com> writes:
> Some time ago, I set up a blog using org-jekyll. I recently tried
> to publish my blog, but when I run:
>
> org-jekyll-export-blog
>
> I get the message: Symbol's function definition is void:
> org-publish-initialize-files-alist
>
> I grepped for this function, and noticed that it is now defined in
> org-protocol.el
> using (declare-function org-publish-initilialize-files-alist "org-publish"),
> whereas before, the function was declared in org-publish.el
>
> Can anyone help with this problem?
>
> I tried putting this in my emacs, but it didn't work:
> (require 'org-protocol.el)
> (require 'org-publish)
> (require 'org-jekyll)
>
> Thanks,
> --Nate
Nathan,
I cannot find a file named org-jekyll.el or similar.
But I guess `org-publish-initialize-files-alist' is just called to find
a project the current files belongs to.
If that is the case, you simply remove the call to that function and use
(let ((project
(org-publish-get-project-from-filename buffer-file-name)))
....
If you encounter any problems, I'll be glad to help.
Sebastian
next prev parent reply other threads:[~2010-06-30 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 22:45 Org-jekyll - org-publish-initialize-files-alist Nathan Neff
2010-06-30 3:27 ` Puneeth
2010-06-30 3:49 ` Nick Dokos
2010-06-30 11:32 ` Sebastian Rose
2010-06-30 11:45 ` Sebastian Rose [this message]
2010-06-30 14:27 ` Nathan Neff
2010-06-30 19:04 ` Sebastian Rose
2010-07-02 14:25 ` Juan Reyero
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=87bpas7ngq.fsf@gmx.de \
--to=sebastian_rose@gmx.de \
--cc=emacs-orgmode@gnu.org \
--cc=nathan.neff@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 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).