emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Cc: marc@ihm.name
Subject: Re: [ox, patch] Keywords & what should go in ox?
Date: Sat, 28 Mar 2015 16:50:29 +0100	[thread overview]
Message-ID: <87oandqfy2.fsf@gmx.us> (raw)
In-Reply-To: <87ego9i1w5.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sat, 28 Mar 2015 16:21:14 +0100")

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Rasmus <rasmus@gmx.us> writes:
>> By this logic we'd have to add *every* "global" keyword, no?  Does it make
>> sense?
> Every global (as in "ox.el") keyword should be documented there, indeed.


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).


Slowly unravels in a ball of yarn and the devil collects it

  reply	other threads:[~2015-03-28 15:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-14 13:55 Rasmus
2015-03-15  8:28 ` Nicolas Goaziou
2015-03-17 15:37   ` Rasmus
2015-03-17 15:46     ` Nicolas Goaziou
2015-03-18 16:47       ` Rasmus
2015-03-19  7:36         ` Nicolas Goaziou
2015-03-19 10:19           ` Rasmus
2015-03-21  8:50             ` Nicolas Goaziou
2015-03-26 19:31   ` Rasmus
2015-03-26 20:37     ` Nicolas Goaziou
2015-03-27 12:50       ` Rasmus
2015-03-28 15:21         ` Nicolas Goaziou
2015-03-28 15:50           ` Rasmus [this message]
2015-03-29 12:16           ` Rasmus

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:

  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=87oandqfy2.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \
    --cc=marc@ihm.name \


* 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


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).