From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-publish parameters mismatch → cannot publish to HTML
Date: Wed, 27 Nov 2013 08:49:06 -0500 [thread overview]
Message-ID: <87siuikl9p.fsf@gmail.com> (raw)
In-Reply-To: 8738miv3sg.wl%n142857@gmail.com
Daniel Clemente <n142857@gmail.com> writes:
> Hi, in ox-publish.el I see in line 555:
>
> (defun org-publish-org-to (backend filename extension plist &optional pub-dir)
> …
>
> org-publish-org-to-html seems to have its parameters in the same
> order (filename, extension, plist). Correct me if I'm wrong.
>
> But then in same file, line 654:
> (when (org-publish-needed-p
> filename pub-dir f tmp-pub-dir base-dir)
> (funcall f project-plist filename tmp-pub-dir)
> …
>
> With the default setting f == org-publish-org-to-html, the funcall
> passes parameters in the wrong order: plist filename. It should be:
> filename extension plist
>
> Later I see org trying to open the „filename“ variable which is not
> a file name but a plist: (wrong-type-argument stringp (:base-directory
> "~/repoweb/ofinial…" …) …) file-truename((:base-directory
> "~/repoweb/ofinial/hacer/" :publishing-directory …) …)
>
>
> Maybe my setup is wrong (I'm confused with the org-publish /
> ox-publish mix) but the org-publish-project-alist seems safe; the
> stranges thing is: :publishing-function org-publish-org-to-html
>
>
> Does org-publish work for someone else? Why do I see new problems
> each time I try to publish…?
>
If you are using org8.X, then org-publish-org-to-html no longer
exists. If it does, you are picking up old org bits from somewhere.
See http://orgmode.org/worg/org-8.0.html for some tips, but bear in mind
that it's probably incomplete.
--
Nick
next prev parent reply other threads:[~2013-11-27 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 4:58 org-publish parameters mismatch → cannot publish to HTML Daniel Clemente
2013-11-27 13:49 ` Nick Dokos [this message]
2013-11-28 6:19 ` Daniel Clemente
2014-01-03 15:40 ` 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=87siuikl9p.fsf@gmail.com \
--to=ndokos@gmail.com \
--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).