{New exporter] What happened to the export template

{New exporter] What happened to the export template

[Rick Frankel]

Hi-

Been using the new exporter for a while, and have not had much problem
w/ the migration, but it seems that org-insert-export-options-template
and the associated keybinding in the dispatch menu are gone. 

Once the old exporter (org-exp.el) is entirely gone, it's going to be
real difficult (at least for me :) not start a new org file.

Am i missing a replacement function in the new exporter, or has this
functionality been removed entirely?

rick

Re: {New exporter] What happened to the export template

[Rasmus]

> Been using the new exporter for a while, and have not had much problem
> w/ the migration, but it seems that org-insert-export-options-template
> and the associated keybinding in the dispatch menu are gone. 
>
> Once the old exporter (org-exp.el) is entirely gone, it's going to be
> real difficult (at least for me :) not start a new org file.
>
> Am i missing a replacement function in the new exporter, or has this
> functionality been removed entirely?

I guess one option might be org-structure-template-alist.  You could
make different templates and could even customize them based on the
particularities needed.  Probably, however, there is a better approach
that I'm unaware of.

–Rasmus

-- 
A clever person solves a problem. A wise person avoids it

Re: {New exporter] What happened to the export template

[Nicolas Goaziou]

Hello,

Rick Frankel <rick@rickster.com> writes:

> Been using the new exporter for a while, and have not had much problem
> w/ the migration, but it seems that org-insert-export-options-template
> and the associated keybinding in the dispatch menu are gone. 
>
> Once the old exporter (org-exp.el) is entirely gone, it's going to be
> real difficult (at least for me :) not start a new org file.
>
> Am i missing a replacement function in the new exporter, or has this
> functionality been removed entirely?

It has been removed. Such a template depends on the back-end used, which
was not the case of the previous implementation.


Regards,

-- 
Nicolas Goaziou

Re: {New exporter] What happened to the export template

[Bastien]

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> It has been removed. Such a template depends on the back-end used, which
> was not the case of the previous implementation.

One idea would be to have an equivalent of the now-defunct
`org-insert-export-options-template' but for each backend.

For example `C-c C-e h t' would insert the default template
for the HTML export.

Is anyone interested in this?

-- 
 Bastien

Re: {New exporter] What happened to the export template

[Dieter Wilhelm]

Bastien <bzg@altern.org> writes:

> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> It has been removed. Such a template depends on the back-end used, which
>> was not the case of the previous implementation.
>
> One idea would be to have an equivalent of the now-defunct
> `org-insert-export-options-template' but for each backend.
>
> For example `C-c C-e h t' would insert the default template
> for the HTML export.
>
> Is anyone interested in this?

Well I found this template very helpful!  I hope there will be an
equivalent to it.  

I think (for the beginning) it could be a compilation of *all* back-end
variations (commented out? I don't yet understand the new exporter
concept).

Thanks
-- 
Best wishes

H. Dieter Wilhelm
Darmstadt
Germany

Re: {New exporter] What happened to the export template

[Rasmus]

Bastien <bzg@altern.org> writes:

>> It has been removed. Such a template depends on the back-end used, which
>> was not the case of the previous implementation.
>
> One idea would be to have an equivalent of the now-defunct
> `org-insert-export-options-template' but for each backend.
>
> For example `C-c C-e h t' would insert the default template
> for the HTML export.
>
> Is anyone interested in this?

Not really.  IMO, the old template added to much noise and didn't have
nice defaults.  That's purely subjective, though!  

IMO, it would be better to have a section on adopting mechanisms such as
org-structure-template-alist for templates.  Personally, I use
org-latex-classes for rudimentary customizations (letter, problemset,
thesis etc.).

–Rasmus


-- 
Send from my Emacs

Re: {New exporter] What happened to the export template

[Bastien]

Rasmus <rasmus@gmx.us> writes:

> Not really.  IMO, the old template added to much noise and didn't have
> nice defaults.  That's purely subjective, though!  

That's what this thread is for -- collect purely subjective
feedback so we can get a rough idea of whether it's useful to
implement this feature or not :)

-- 
 Bastien

Re: {New exporter] What happened to the export template

[Sebastien Vauban]

Hello Bastien,

Bastien wrote:
> Nicolas Goaziou <n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
>> It has been removed. Such a template depends on the back-end used, which
>> was not the case of the previous implementation.
>
> One idea would be to have an equivalent of the now-defunct
> `org-insert-export-options-template' but for each backend.
>
> For example `C-c C-e h t' would insert the default template
> for the HTML export.
>
> Is anyone interested in this?

My personal answer is: yes!

I constantly used it for inserting a title (defaulting to the name of the
file, which is the best default), timestamp, etc.

Regarding Rasmus objections, yes, maybe there are too much defaults inserted,
or not yours. Maybe the template could be customized, but present in the code
base with a common, good default?

If not, anyway, I'll just mimick the old template with a YASnippet.

Best regards,
  Seb

PS- By the way, there is already such a sort of template for Beamer...

-- 
Sebastien Vauban

Re: {New exporter] What happened to the export template

[Nicolas Goaziou]

Hello,

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

> Hello Bastien,
>
> Bastien wrote:
>> Nicolas Goaziou <n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>>> It has been removed. Such a template depends on the back-end used, which
>>> was not the case of the previous implementation.
>>
>> One idea would be to have an equivalent of the now-defunct
>> `org-insert-export-options-template' but for each backend.
>>
>> For example `C-c C-e h t' would insert the default template
>> for the HTML export.
>>
>> Is anyone interested in this?
>
> My personal answer is: yes!
>
> I constantly used it for inserting a title (defaulting to the name of the
> file, which is the best default), timestamp, etc.

You can also type #+ti M-TAB M-TAB to get the same result. It works for
most default keywords.


Regards,

-- 
Nicolas Goaziou

Re: {New exporter] What happened to the export template

[Suvayu Ali]

Hey Seb,

On Mon, Feb 25, 2013 at 02:15:05PM +0100, Sebastien Vauban wrote:
> 
> PS- By the way, there is already such a sort of template for Beamer...

I believe Nicolas' argument was, for the new exporter such a template
depends on the backend hence a default one for beamer makes sense but
not a backend agnostic template.

I'm not completely sure I follow the argument though, since keywords
like TITLE, DATE, AUTHOR, or even an OPTIONS line seem generic enough
for most backends.  But then I have not thought long enough to spot any
inconsistencies.  :-p

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: {New exporter] What happened to the export template

[Robert Goldman]

A very late follow-up:

I note that the Worg instructions for HTML export still cite 
org-insert-export-options-template: 

http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html

Re: {New exporter] What happened to the export template

[Bastien]

Hi Robert,

Robert Goldman <rpgoldman@sift.info> writes:

> A very late follow-up:
>
> I note that the Worg instructions for HTML export still cite 
> org-insert-export-options-template: 
>
> http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html

Can you fix this?

Please send me your public key if you don't have access to Worg
already, I'll give you push access.

Thanks in advance!

-- 
 Bastien