From: Carsten Dominik <carsten.dominik@gmail.com>
To: Sebastian Hofer <sebhofer@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Problem with sectioning function for LaTeX export
Date: Tue, 27 Apr 2010 17:44:07 +0200 [thread overview]
Message-ID: <674C0E7F-4F3D-40A8-A2A5-BFBA28F27C68@gmail.com> (raw)
In-Reply-To: <hqelh5$dvu$1@dough.gmane.org>
On Apr 18, 2010, at 12:05 PM, Sebastian Hofer wrote:
> Hi all,
> I'm trying to write my own sectioning function for latex export of
> my CV. What it does is to read out some property of the given
> headline and pass it to a latex command:
>
> (defun my-org-cv-sectioning (lvl heading)
> (let ((year)
> (formatlist)
> (cleanheading (substring-no-properties heading 1)))
> (with-current-buffer (org-find-base-buffer-visiting "cv.org")
> (let ((headingpoint (find-custom-id cleanheading)))
> (if headingpoint
> (progn
> (goto-char headingpoint)
> (setq year (org-entry-get nil "YEAR"))))))
> (setq formatlist (nth (- 1 lvl) my-org-cv-sectioning-list))
> (list cleanheading
> (format (car formatlist) (if year year "") cleanheading)
> (format (car (cdr formatlist)) (if year year "")
> cleanheading))))
>
> The function find-custom-id returns the point of the heading, my-org-
> cv-sectioning list contains the customized latex commands. As you
> may see, I'm an elisp newbie, so excuse the coding style, or even
> better, make suggestions for improvements! There might be a much
> nicer way to read out the wanted properties (also cf. point 2
> below), so if you have any suggestions on that, I would be glad to
> hear them!
>
> Anyway, there are currently two problems:
>
> - The function reads out the properties correctly, but the export
> command throws an error. So I guess I'm not getting the format of
> the output right, but I can't really make sense of the description
> in the org-export-latex-classes docstring. Currently the function is
> returning something like this: ("Heading" ("\section[year]{Heading}"
> "\section*[year]{Heading}")). Isn't this what it's supposed to look
> like? The error message is the following:
I think it must be
("Heading" "\section[year]{%s}" "\section*[year]{%s}")
Note the %s for the heading, and also it i just one flat list of 3
items.
And yes, this is not too well documented.
>
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> format(nil "Heading" "")
> org-export-latex-subcontent(<snipped>)
> org-export-latex-sub(<snipped>)
> org-export-latex-global(((<snipped>))))
> org-export-as-latex(nil nil nil "*Org LaTeX Export*")
> org-export-as-latex-to-buffer(nil)
> call-interactively(org-export-as-latex-to-buffer)
> org-export(nil)
> call-interactively(org-export nil nil)
>
> - As you can see I am using org-find-base-buffer-visiting find the
> buffer of the org file, but of course its argument can't stay
> hardcoded like this. I could also use the org mapping function, but
> still I would need filename. Can someone give me a hint how to solve
> this in a nice way?
Use
(org-find-base-buffer-visiting org-current-export-file)
HTH
- Carsten
next prev parent reply other threads:[~2010-04-27 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 10:05 Problem with sectioning function for LaTeX export Sebastian Hofer
2010-04-27 15:44 ` Carsten Dominik [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-29 12:10 Sebastian Hofer
2010-04-29 23:05 ` Sebastian Hofer
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=674C0E7F-4F3D-40A8-A2A5-BFBA28F27C68@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sebhofer@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).