From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: # of parameters of `org-latex-format-headline-function'
Date: Fri, 17 Oct 2014 11:21:53 -0400 [thread overview]
Message-ID: <87vbniafhq.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: 86mw8vw04q.fsf@example.com
Sebastien Vauban <sva-news@mygooglest.com>
writes:
> Hello,
>
> During the summer, the number of parameters of the
> `org-latex-format-headline-function' changed from 5 to 6: addition of
> `info'.
>
> The new version of my private formatting function is:
>
> ;; function for formatting the headline's text
> (setq org-latex-format-headline-function
> 'my/org-latex-format-headline)
>
> ;; markup for TODO keywords and for tags, as a printf format
> (defun my/org-latex-format-headline (todo todo-type priority text tags info)
> "Default function for formatting the headline's text."
> (concat (when todo
> (format "{%s\\textbf{\\textsc{\\textsf{%s}}}} "
> (cond ((equal todo-type 'todo) "\\color{red}")
> ((equal todo-type 'done) "\\color{teal}")
> (t "\\color{gray}"))
> todo))
> (when priority
> (format "\\framebox{\\#%c} " priority))
> text
> (when tags
> (format "\\hfill{}\\fbox{\\textsc{%s}}"
> (mapconcat 'identity tags ":")))))
>
> That works on `master', but not on Org from ELPA (`maint').
>
> As parts of my config file are shared between my coworkers, and as some
> of them don't have Git Org but the ELPA package, how can I support both
> versions of Org?
>
> Do I have to test the Org version number, or is there a more clever way?
>
Make info an &optional parameter in your function: recent org will call
it with a non-nil info, old org will call it without an info parameter
(which I believe will make it nil inside your function).
Untested.
Nick
next prev parent reply other threads:[~2014-10-17 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 8:50 # of parameters of `org-latex-format-headline-function' Sebastien Vauban
2014-10-17 15:21 ` Nick Dokos [this message]
2014-10-21 7:30 ` Sebastien Vauban
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=87vbniafhq.fsf@alphaville.bos.redhat.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).