Re: [O] [Exporter] Why is :author a list in the communication channel?

2013-11-04 Thread Thorsten Jolitz
Aaron Ecay aarone...@gmail.com writes: Hi Aaron, I would have expected multiple author lines to have this effect, so that your desired list of two authors would be generated by: , | #+author: Thorsten Jolitz | #+author: Thomas Mueller ` But it seems that only the last #+author

Re: [O] [Exporter] Why is :author a list in the communication channel?

2013-11-04 Thread Nicolas Goaziou
Hello, Thorsten Jolitz tjol...@gmail.com writes: Aaron Ecay aarone...@gmail.com writes: Hi Aaron, I would have expected multiple author lines to have this effect, so that your desired list of two authors would be generated by: , | #+author: Thorsten Jolitz | #+author: Thomas Mueller

Re: [O] [Exporter] Why is :author a list in the communication channel?

2013-11-04 Thread Thorsten Jolitz
Hello, Nicolas Goaziou n.goaz...@gmail.com writes: Thorsten Jolitz tjol...@gmail.com writes: Aaron Ecay aarone...@gmail.com writes: Hi Aaron, I would have expected multiple author lines to have this effect, so that your desired list of two authors would be generated by: , |

Re: [O] [Exporter] Why is :author a list in the communication channel?

2013-11-04 Thread Nicolas Goaziou
Thorsten Jolitz tjol...@gmail.com writes: 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

Re: [O] [Exporter] Why is :author a list in the communication channel?

2013-11-04 Thread Nick Dokos
Thorsten Jolitz tjol...@gmail.com writes: Nicolas Goaziou n.goaz...@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

Re: [O] [Exporter] Why is :author a list in the communication channel?

2013-11-04 Thread Marcin Borkowski
Dnia 2013-11-04, o godz. 20:30:24 Nicolas Goaziou n.goaz...@gmail.com napisał(a): Thorsten Jolitz tjol...@gmail.com writes: Ok, I understand, so this is all working fine just as intended. For multiple authors one could use a workaround/convention like

[O] [Exporter] Why is :author a list in the communication channel?

2013-11-02 Thread Thorsten Jolitz
Hi List, I wonder why the :author attribute in INFO is a list (while :email, :creator and others are not)? It would make sense if several authors would be collected as a list of strings, like e.g. ,- | (Thorsten Jolitz Thomas Mueller)

Re: [O] [Exporter] Why is :author a list in the communication channel?

2013-11-02 Thread Nicolas Goaziou
Hello, Thorsten Jolitz tjol...@gmail.com writes: I wonder why the :author attribute in INFO is a list (while :email, :creator and others are not)? :author's value is parsed, as all keywords in `org-element-document-properties'. So its value is a secondary string, i.e. an element without type.

Re: [O] [Exporter] Why is :author a list in the communication channel?

2013-11-02 Thread Thorsten Jolitz
Nicolas Goaziou n.goaz...@gmail.com writes: Hello, Thorsten Jolitz tjol...@gmail.com writes: I wonder why the :author attribute in INFO is a list (while :email, :creator and others are not)? :author's value is parsed, as all keywords in `org-element-document-properties'. So its value is

Re: [O] [Exporter] Why is :author a list in the communication channel?

2013-11-02 Thread Aaron Ecay
Hi Thorsten, I would have expected multiple author lines to have this effect, so that your desired list of two authors would be generated by: , | #+author: Thorsten Jolitz | #+author: Thomas Mueller ` But it seems that only the last #+author line is used; previous ones are discarded.