From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: [ox, patch] Keywords & what should go in ox? Date: Sat, 28 Mar 2015 16:50:29 +0100 Message-ID: <87oandqfy2.fsf@gmx.us> References: <871tkrsmxh.fsf@gmx.us> <87a8ze3bsa.fsf@nicolasgoaziou.fr> <87egobtv98.fsf@gmx.us> <87d23vlclb.fsf@nicolasgoaziou.fr> <87a8yywqo4.fsf@gmx.us> <87ego9i1w5.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39794) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ybt0R-0004Fe-0T for emacs-orgmode@gnu.org; Sat, 28 Mar 2015 11:50:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ybt0M-0001TE-TU for emacs-orgmode@gnu.org; Sat, 28 Mar 2015 11:50:38 -0400 Received: from mout.gmx.net ([212.227.15.15]:62671) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ybt0M-0001Qe-Bs for emacs-orgmode@gnu.org; Sat, 28 Mar 2015 11:50:34 -0400 In-Reply-To: <87ego9i1w5.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sat, 28 Mar 2015 16:21:14 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Cc: marc@ihm.name Nicolas Goaziou writes: > Rasmus writes: > >> By this logic we'd have to add *every* "global" keyword, no? Does it ma= ke >> sense? > > Every global (as in "ox.el") keyword should be documented there, indeed. OK. Marc: you expressed a desire to fix some bugs. I don't know if you like documentation bugs, or whether you are more into code bugs. If you like documentation, would that be something you'd want to do? >>>> At least SUBTITLE for ox-texinfo in not documented here. >>> >>> That's also a documentation bug. Note that it should probably >>> be :texinfo-subtitle (and :texinfo-subauthor). >> >> Unless we add a #+SUBTITLE... > > It depends. Adding a prefix allows to specify a subtitle per back-end > when publishing through multiple back-ends. Not a big deal, tho. It would make it hard to set *a* subtitle through publishing. As a user I don't care about the implementation detail and I would prefer :subtitle (should I ever need to specify a subtitle via publishing). =E2=80=94Rasmus --=20 Slowly unravels in a ball of yarn and the devil collects it