From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Barton Subject: Re: What Happened to org-export-html-extension? Date: Fri, 05 Apr 2013 16:25:49 +0100 Message-ID: <515EECFD.9090806@wilkesley.net> References: <51580539.3080106@wilkesley.net> <20130331100123.GA8564@kuru.dyndns-at-home.com> <51584E39.4010004@wilkesley.net> <51588F02.3030203@wilkesley.net> <8738v7j1n6.fsf@bzg.ath.cx> Reply-To: ian@manor-farm.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:57006) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UO8Wc-0004PZ-6C for emacs-orgmode@gnu.org; Fri, 05 Apr 2013 11:26:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UO8WX-0006ih-6h for emacs-orgmode@gnu.org; Fri, 05 Apr 2013 11:25:57 -0400 Received: from mail2.wilkesley.net ([109.74.196.44]:55946 helo=li40-130.members.linode.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UO8WW-0006iS-HA for emacs-orgmode@gnu.org; Fri, 05 Apr 2013 11:25:53 -0400 Received: from [192.168.0.236] (unknown [46.33.134.31]) (Authenticated sender: lists@wilkesley.net) by li40-130.members.linode.com (Postfix) with ESMTPSA id 14E8E33360E for ; Fri, 5 Apr 2013 16:25:49 +0100 (BST) In-Reply-To: <8738v7j1n6.fsf@bzg.ath.cx> 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: emacs-orgmode@gnu.org On 03/04/13 12:26, Bastien wrote: > Hi Ian, > > Ian Barton writes: > >> Thanks for the clear explanation. Using my own function works, but this >> does seem to be a regression. Defining your own extension is useful e.g. if >> you want to emit .php files. > > Indeed. I fixed this regression, and using either :html-extension in > publication projects or (setq org-html-extension "php") globally will > work now. > > Thanks for reporting this, > And thanks for fixing it! Ian.