From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [RFC] Replace some HTML related keywords with OPTIONS items Date: Thu, 27 Jun 2013 21:18:11 +0200 Message-ID: <87y59vqs5o.fsf@gmail.com> References: <87vc58fv2x.fsf@gmail.com> <87wqpfoarm.fsf@bzg.ath.cx> <87ehbnsfuy.fsf@gmail.com> <874ncjil07.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49886) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UsHhn-0006j1-Fd for emacs-orgmode@gnu.org; Thu, 27 Jun 2013 15:18:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UsHhh-0007lo-UE for emacs-orgmode@gnu.org; Thu, 27 Jun 2013 15:18:07 -0400 In-Reply-To: <874ncjil07.fsf@bzg.ath.cx> (Bastien's message of "Thu, 27 Jun 2013 18:19:52 +0200") 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: Bastien Cc: Org Mode List Bastien writes: > Nicolas Goaziou writes: > >> Basically, #+keyword: is for strings, #+OPTIONS: use `read' on the >> values, so it should be used for every other type. > > Thanks for the explanation, it makes sense. > > Let's make it explicit somewhere in the manual, so that users > have a clear rule in mind when wondering what syntax they need > to look for. I tend to think it's more a developer information. By looking at the manual, there's no confusion possible for a user. Maybe it should go in `org-export-options-alist' docstring instead. Regards, -- Nicolas Goaziou