From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: SETUPFILE and variants Date: Wed, 13 Feb 2013 20:54:20 +0100 Message-ID: <878v6s9ehf.fsf@gmail.com> References: <86pq051qpw.fsf@somewhere.org> <87d2w4cnfr.fsf@gmail.com> <8638x0dmjm.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:44429) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5iQ7-0004uH-4a for emacs-orgmode@gnu.org; Wed, 13 Feb 2013 14:55:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U5iPk-00006x-D9 for emacs-orgmode@gnu.org; Wed, 13 Feb 2013 14:54:46 -0500 Received: from plane.gmane.org ([80.91.229.3]:33709) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U5iPk-00006H-4h for emacs-orgmode@gnu.org; Wed, 13 Feb 2013 14:54:44 -0500 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1U5iQ0-0001QC-7e for emacs-orgmode@gnu.org; Wed, 13 Feb 2013 20:55:00 +0100 In-Reply-To: <8638x0dmjm.fsf@somewhere.org> (Sebastien Vauban's message of "Wed, 13 Feb 2013 20:46:37 +0100") 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: Sebastien Vauban Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org "Sebastien Vauban" writes: > I could advocate that you could define an :EXPORT_INCLUDE: as well, that is > file to be included for the subtree export. It wouldn't make much sense. The location of INCLUDE keyword is meaningful, and so is its indentation. You miss both of them with your suggestion. > Do you prone the utilization of one over the other? No. > #+STYLE: [...] > I really don't understand what's going on. I see that the checks are made > whether the file exist or not. I did press C-c C-c each time before > exporting -- to be sure (because it seems anyway to work without doing that). > > But nothing... I'll to find out another way to understand what's going > on... Try #+HTML_STYLE: instead of #+STYLE: Regards, -- Nicolas Goaziou