SETUPFILE and variants

SETUPFILE and variants

[Sebastien Vauban]

Hello,

With the new exporter, I still couldn't find how to use a setup file.

Neither with:

- the old `#+SETUPFILE:' directive
- the new one (?): `#+SETUP_FILE:'
- the soon to be unique one (?): `#+INCLUDE:'

Am I missing something?

Best regards,
  Seb

ECM file:

--8<---------------cut here---------------start------------->8---
#+TITLE:     Example of Tasks
#+AUTHOR:    Sebastien Vauban
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE:  en

#+INCLUDE: "~/src/org-style/bigblow.setup"

* Marketing

** STRT Hire PR firm
--8<---------------cut here---------------end--------------->8---

-- 
Sebastien Vauban

Re: SETUPFILE and variants

[Nicolas Goaziou]

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

Re: SETUPFILE and variants

[Sebastien Vauban]

Hi Nicolas,

Nicolas Goaziou wrote:
> Sebastien Vauban 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

I could advocate that you could define an :EXPORT_INCLUDE: as well, that is
file to be included for the subtree export.

Do you prone the utilization of one over the other?

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

I fully agree.

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

In essence: links to CSS and JavaScript "libraries":

--8<---------------cut here---------------start------------->8---
# -*- mode: org; -*-

#+STYLE: <script src="http://code.jquery.com/jquery-1.9.0.js"></script>
#+STYLE: <script src="http://code.jquery.com/ui/1.10.0/jquery-ui.js"></script>

#+STYLE: <link rel="stylesheet" type="text/css" href="http://svn-server/org-style/trunk/bigblow/css/bigblow.css"/>
#+STYLE: <link rel="stylesheet" type="text/css" href="http://svn-server/org-style/trunk/bigblow/css/htmlize.css"/>
#+STYLE: <script type="text/javascript" src="http://svn-server/org-style/trunk/bigblow/js/bigblow.js"></script>
#+STYLE: <script type="text/javascript" charset="utf-8" src="http://svn-server/org-style/trunk/bigblow/js/jquery.scrollTo-1.4.3.1-min.js"></script>
#+STYLE: <script type="text/javascript" charset="utf-8" src="http://svn-server/org-style/trunk/bigblow/js/jquery.localscroll-min.js"></script>

#+STYLE: <link rel="stylesheet" type="text/css" href="css/bigblow.css"/>
#+STYLE: <link rel="stylesheet" type="text/css" href="css/htmlize.css"/>
#+STYLE: <script type="text/javascript" src="js/bigblow.js"></script>
#+STYLE: <script type="text/javascript" src="js/jquery.scrollTo-1.4.3.1-min.js"></script>
#+STYLE: <script type="text/javascript" src="js/jequery.localscroll-min.js"></script>
--8<---------------cut here---------------end--------------->8---

> I have no problem with this ECM.

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

> Also what did you expect?

My CSS style to be applied! ;-)

Best regards,
  Seb

-- 
Sebastien Vauban

Re: SETUPFILE and variants

[Nicolas Goaziou]

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> 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: <script src="http://code.jquery.com/jquery-1.9.0.js"></script>

[...]

> 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

Re: SETUPFILE and variants

[Sebastien Vauban]

Hi Nicolas,

Nicolas Goaziou wrote:
> "Sebastien Vauban" writes:
>
>> #+STYLE: <script src="http://code.jquery.com/jquery-1.9.0.js"></script>
>
> [...]
>
>> 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:

That was it. Thanks a lot!

Best regards,
  Seb

-- 
Sebastien Vauban

Re: SETUPFILE and variants

[Sebastien Vauban]

Nicolas, Bastien,

"Sebastien Vauban" wrote:
>>> 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?
>
> In essence: links to CSS and JavaScript "libraries"

By the way, it'd be wonderful if we could put an URL to the setup file: that
way, for documents we edit together, I don't have either:

- to impose an absolute location for the setup file, nor
- to copy the setup file locally in every project we collaborate on.

Is that somehow doable?

Best regards,
  Seb

-- 
Sebastien Vauban