emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
	<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: SETUPFILE and variants
Date: Wed, 13 Feb 2013 15:12:40 +0100	[thread overview]
Message-ID: <87d2w4cnfr.fsf@gmail.com> (raw)
In-Reply-To: <86pq051qpw.fsf@somewhere.org> (Sebastien Vauban's message of "Tue, 12 Feb 2013 16:44:59 +0100")



Hello,

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:

> With the new exporter, I still couldn't find how to use a setup file.
>
> Neither with:
>
> - the old `#+SETUPFILE:' directive

Still working here.

> - the new one (?): `#+SETUP_FILE:'

It has been dropped. You can safely forget it.

> - the soon to be unique one (?): `#+INCLUDE:'

It should work too.

I had indeed considered dropping #+SETUPFILE. but if we keep it, we
might be able to define an :EXPORT_SETUPFILE: for subtree export (not
implemented). So, after all, I

Anyway, for the time being, I prefer to focus on real bugs.

> ECM file:
>
> #+TITLE:     Example of Tasks
> #+AUTHOR:    Sebastien Vauban
> #+DESCRIPTION:
> #+KEYWORDS:
> #+LANGUAGE:  en
>
> #+INCLUDE: "~/src/org-style/bigblow.setup"
>
> * Marketing
>
> ** STRT Hire PR firm

What does "bigblow.setup" contain? I have no problem with this ECM.

Also what did you expect?


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-02-13 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 15:44 SETUPFILE and variants Sebastien Vauban
2013-02-13 14:12 ` Nicolas Goaziou [this message]
2013-02-13 19:46   ` Sebastien Vauban
2013-02-13 19:54     ` Nicolas Goaziou
2013-02-14  8:55       ` Sebastien Vauban
2013-02-13 20:42     ` Sebastien Vauban

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=87d2w4cnfr.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.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).