From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [PATCH] ox.el: Define subtitle macro Date: Fri, 17 Nov 2017 23:47:17 +0100 Message-ID: <87lgj4tte2.fsf@nicolasgoaziou.fr> References: <87tvxub9jj.fsf@wi.uni-muenster.de> <87375dsspo.fsf@gmx.us> <87375ds50i.fsf@wi.uni-muenster.de> 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]:45413) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eFpPx-00019R-64 for emacs-orgmode@gnu.org; Fri, 17 Nov 2017 17:47:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eFpPs-0005lc-B6 for emacs-orgmode@gnu.org; Fri, 17 Nov 2017 17:47:25 -0500 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:35864) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eFpPs-0005kd-5k for emacs-orgmode@gnu.org; Fri, 17 Nov 2017 17:47:20 -0500 In-Reply-To: <87375ds50i.fsf@wi.uni-muenster.de> (Jens Lechtenboerger's message of "Fri, 17 Nov 2017 09:06:53 +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" To: Rasmus Cc: emacs-orgmode@gnu.org Hello, Jens Lechtenboerger writes: > On 2017-11-17, Rasmus wrote: > >> Jens Lechtenboerger writes: >> >>> the attached patch adds a subtitle macro with documentation. >> >> AFAIK it=E2=80=99s already added to the backends where it makes sense. = It=E2=80=99s not a >> basic keyword like "#+author". It should be documented under the releva= nt >> backends that support it. > > Sorry, I don't understand your suggestion. I'm interested in > org-reveal [1], which is based on ox-html.el. In ox-html.el, > subtitles are used at some hardcoded positions (preamble, postamble, > template), but I need access to the subtitle elsewhere. > > What should I document where? SUBTITLE keyword may not be supported in every back-end. As a consequence, supporting a global {{{subtitle}}} macro sounds presumptuous. Anyway, it begs for generalisation. The same problem is going to arise for CREATOR, KEYWORDS, and WHATNOT. Instead of {{{subtitle}}}, we could implement {{{option(KWD)}}}. Basically, {{{option(SUBTITLE)}}} =3D> (org-element-interpret-data (plist-get info = :subtitle)) Options with a `split' behaviour would need a special treatment, however. WDYT? Do you want to have a stab at it? Regards, --=20 Nicolas Goaziou