From: Bastien <bzg@altern.org>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Spelled out example of org-latex-format-headline-function customization?
Date: Tue, 19 Mar 2013 17:37:12 +0100 [thread overview]
Message-ID: <87a9pzz6pz.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CA+M2ft_=Vau46G97tnkkBrbDY8wwRUTSdSHLDBRoMexH0sk24A@mail.gmail.com> (John Hendy's message of "Tue, 19 Mar 2013 11:18:37 -0500")
John Hendy <jw.hendy@gmail.com> writes:
> So the docstring is just the documentation definition? (In this case
> "Documentation: Function for formatting the headline's text..."?)
Yes.
>> C-h f org-latex-format-headline-default-function RET
>>
>> will show you the docstring of the function.
>
> And in this case: "(org-latex-format-headline-default-function TODO
> TODO-TYPE PRIORITY TEXT TAGS)"?
Not exactly... Emacs display the documentation after the definition of
the function and its arguments.
The definition here is:
Default format function for a headline.
See `org-latex-format-headline-function' for details.
> Good to know. It seems that variables *could* be passed to the format
> function. After all, the function takes five arguments which are all
> either strings or nil... so it would seem that one could have a
> variable like:
>
> (setq org-latex-headline-format ("string" "string" "string" "string"
> "string")) which would feed into the default-headline-function
> function.
>
> Or splitting out into separate variables. Seems like the tension is
> between minimizing locations to make all of these settings and ease of
> use (for noobs).
This is what our discussion with Nicolas is really about.
There are problems with tags, though: you need to handle them
one by one, not as a string.
I'll send news if any!
--
Bastien
prev parent reply other threads:[~2013-03-19 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 2:56 Spelled out example of org-latex-format-headline-function customization? John Hendy
2013-03-19 15:51 ` Bastien
2013-03-19 16:18 ` John Hendy
2013-03-19 16:30 ` Charles Berry
2013-03-19 16:37 ` Bastien [this message]
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=87a9pzz6pz.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@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).