From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-export-section-number-format does not work
Date: Tue, 09 Jul 2013 00:22:09 -0400 [thread overview]
Message-ID: <87y59g2wi6.fsf@gmail.com> (raw)
In-Reply-To: CADtzDwbRCb-KTjkvgCGDj+mdkyFzbQhL5ZzDZ7ZCZsLT=mY87A@mail.gmail.com
Jisang Yoo <jisang.yoo.ac+org@gmail.com> writes:
> On Mon, Jul 8, 2013 at 5:21 PM, Bastien <bzg@gnu.org> wrote:
>> Hi Jisang,
>>
>> Jisang Yoo <jisang.yoo.ac+org@gmail.com> writes:
>>
>>> There seems no new option that can be found from exploring
>>> customization group org-export.
>>
>> You can check `org-html-format-headline-function' and its docstring
>> as an example on how to customize the display of headlines in HTML.
>> There are similar variables for other backends.
>>
>> HTH,
>>
>> --
>> Bastien
>
> (setq org-html-format-headline-function 'my-org-html-format-headline)
> (defun my-org-html-format-headline (todo todo-type priority text tags)
> "Returns foo."
> "foo")
>
> results in wrong-number-of-arguments error when I export to html.
>
> (setq org-html-format-headline-function 'org-html-format-headline)
>
> also results in the same kind of error.
>
>
I think all that's needed is to add an explicit nil at the end of the
apply call in ox-html.el:org-html-format-headline--wrap, line 2246, like
this:
--8<---------------cut here---------------start------------->8---
...
(apply format-function
todo todo-type priority text tags
:headline-label headline-label :level level
:section-number section-number extra-keys nil)))
--8<---------------cut here---------------end--------------->8---
I'm not 100% sure about that but it seems to work for me both in the
default case and also with Jisang's setting - can somebody verify?
But getting there was not trivial: the CL-isms certainly do not help,
primarily because I had to understand them to figure out what was going
on, but also because they obscured the problem: when I tried to edebug
org-html-format-headline--wrap I get
,----
| edebug-syntax-error: Invalid read syntax: "Failed matching", ([&rest
| arg] [&optional ["&optional" cl-&optional-arg &rest cl-&optional-arg]]
| [&optional ["&rest" arg]] [&optional ["&key" [cl-&key-arg &rest
| cl-&key-arg] &optional "&allow-other-keys"]] [&optional ["&aux" &rest
| &or (symbolp &optional def-form) symbolp]])
`----
and the cursor is left at the ampersand of &allow-other-keys. OTOH,
when I try to edebug org-html-inlinetask which contains a similar
CL-ism, there is no problem. So something is tripping edebug up
but it's not clear what.
--
Nick
next prev parent reply other threads:[~2013-07-09 4:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 19:40 org-export-section-number-format does not work Jisang Yoo
2013-07-08 8:05 ` Bastien
2013-07-08 8:19 ` Jisang Yoo
2013-07-08 8:21 ` Bastien
2013-07-08 19:57 ` Jisang Yoo
2013-07-08 20:31 ` Bastien
2013-07-08 20:35 ` Nicolas Goaziou
2013-08-24 6:55 ` Jisang Yoo
2013-07-09 4:22 ` Nick Dokos [this message]
2013-07-09 11:15 ` 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=87y59g2wi6.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).