From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ox.el: Define subtitle macro
Date: Fri, 17 Nov 2017 23:47:17 +0100 [thread overview]
Message-ID: <87lgj4tte2.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87375ds50i.fsf@wi.uni-muenster.de> (Jens Lechtenboerger's message of "Fri, 17 Nov 2017 09:06:53 +0100")
Hello,
Jens Lechtenboerger <lechten@wi.uni-muenster.de> writes:
> On 2017-11-17, Rasmus wrote:
>
>> Jens Lechtenboerger <lechten@wi.uni-muenster.de> writes:
>>
>>> the attached patch adds a subtitle macro with documentation.
>>
>> AFAIK it’s already added to the backends where it makes sense. It’s not a
>> basic keyword like "#+author". It should be documented under the relevant
>> 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)}}} => (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,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-11-17 22:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 14:08 [PATCH] ox.el: Define subtitle macro Jens Lechtenboerger
2017-11-16 23:34 ` Rasmus
2017-11-17 8:06 ` Jens Lechtenboerger
2017-11-17 22:47 ` Nicolas Goaziou [this message]
2017-11-19 12:27 ` Jens Lechtenboerger
2017-11-21 22:46 ` Nicolas Goaziou
2017-11-23 9:29 ` Jens Lechtenboerger
2018-12-11 9:51 ` Jens Lechtenboerger
2018-12-11 16:28 ` Nicolas Goaziou
2018-12-12 18:56 ` Kaushal Modi
2018-12-13 11:52 ` Bastien
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=87lgj4tte2.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).