emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [Exporter] Why is :author a list in the communication channel?
Date: Mon, 04 Nov 2013 14:45:55 -0500	[thread overview]
Message-ID: <87fvrcymq4.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: 871u2wj9eu.fsf@gmail.com

Thorsten Jolitz <tjolitz@gmail.com> writes:

> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> ...
>> This is orthogonal to the fact that multiple lines are not allowed. For
>> that, see BEHAVIOUR item in `org-export-options-alist'. In particular,
>> you can compare "TITLE" and "AUTHOR" entries.
>
> Ok, I understand, so this is all working fine just as intended. For
> multiple authors one could use a workaround/convention like 
>
>  ,------------------------------------------
>  | #+author: Thorsten_Jolitz Thomas_Mueller
>  `------------------------------------------
>
> and then split the string two times (first blanks, then underscores). 

... or you could modify org-export-options-alist, e.g.:

  (setcar org-export-options-alist '(:author "AUTHOR" nil user-full-name space))

This is a bit too fragile as a general solution: it assumes that the
:author entry is the car of org-export-options-alist which happens to be
the case in my setup, but if you rearrange things, it might not be the
case in your setup. Doing list surgery in the general case is left as
an exercise.

Nick

      parent reply	other threads:[~2013-11-04 19:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-02 20:40 [Exporter] Why is :author a list in the communication channel? Thorsten Jolitz
2013-11-02 21:33 ` Nicolas Goaziou
2013-11-02 21:48   ` Thorsten Jolitz
2013-11-02 22:30 ` Aaron Ecay
2013-11-04 18:10   ` Thorsten Jolitz
2013-11-04 18:20     ` Nicolas Goaziou
2013-11-04 18:42       ` Thorsten Jolitz
2013-11-04 19:30         ` Nicolas Goaziou
2013-11-04 20:07           ` Marcin Borkowski
2013-11-04 19:45         ` Nick Dokos [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=87fvrcymq4.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).