emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [ox, patch] Keywords & what should go in ox?
Date: Fri, 27 Mar 2015 13:50:03 +0100	[thread overview]
Message-ID: <87a8yywqo4.fsf@gmx.us> (raw)
In-Reply-To: <87d23vlclb.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Thu, 26 Mar 2015 21:37:20 +0100")

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

>> I have now reviewed this section twice, and I have no clue what you want
>> me to change there. There's no :with-keywords or :with-description.
>
> I don't know either. I was sure that :keywords and :description were
> here, but, oddly, it isn't the case. That's a documentation bug as long
> as these keywords are in "ox.el".

By this logic we'd have to add *every* "global" keyword, no?  Does it make
sense?

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

So should I go ahead a kill KEYWORD and DESCRIPTION in ox?

—Rasmus

-- 
Lasciate ogni speranza o voi che entrate: siete nella mani di'machellaio

  reply	other threads:[~2015-03-27 12:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-14 13:55 [ox, patch] Keywords & what should go in ox? 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 [this message]
2015-03-28 15:21         ` Nicolas Goaziou
2015-03-28 15:50           ` Rasmus
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:
  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=87a8yywqo4.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \
    /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).