emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ox-reveal cannot export
Date: Thu, 07 Aug 2014 14:22:03 +0200	[thread overview]
Message-ID: <87wqakmqvo.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87mwbgzevu.fsf@gmail.com> (Nick Dokos's message of "Thu, 07 Aug 2014 08:02:45 -0400")

Hello,

Nick Dokos <ndokos@gmail.com> writes:

> Tyler van Hensbergen <tyler@mainstreetgenome.com> writes:
>
>> Robert Eckl <eckl.r <at> gmx.de> writes:
>>
>>> While exporting to reveal i get 
>>> 
>>>       Symbol's function definition is void: org-html-format-headline--wrap
>>> 
>>> What i'm missing?
>>
>>
>> That function's name was changed. I made a temporary fix on
>> a forked branch on github and submitted a pull request
>> today (warning I'm new to elisp so I may have missed
>> something).
>>
>> https://github.com/yjwen/org-reveal/pull/69
>>
>> Not sure if it fixes everything but it is working for me know
>> and I am no longer receiving that error.
>>
>
> I haven't read things carefully, so take this with a large grain
> of salt, but I think it should read:
>
>          ...
>      	 (full-text (org-html-headline headline contents info)))
>          ...
>
> instead of passing a nil for contents.

It should not use `org-html-headline' anyway, as there is no guarantee
that this is the right function for headlines.

To "export like html back-end", there are `org-export-data-with-backend'
and `org-export-with-backend' functions, which doesn't require to know
the original function.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2014-08-07 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 14:45 ox-reveal cannot export Robert Eckl
2014-08-05 16:04 ` Nick Dokos
2014-08-07 10:30 ` Tyler van Hensbergen
2014-08-07 12:02   ` Nick Dokos
2014-08-07 12:22     ` Nicolas Goaziou [this message]
2014-08-08 13:53       ` Yujie Wen

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=87wqakmqvo.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@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).