Re: [O] how to use :options-alist in org-export-define-derived-backend ?

2014-08-02 Thread Nicolas Goaziou
Hello, Bastien b...@gnu.org writes: Yes. But I know see your point about the default title being useless most of the times. So I'm fine with the proposed change in master. Applied. Regards, -- Nicolas Goaziou

Re: [O] how to use :options-alist in org-export-define-derived-backend ?

2014-07-29 Thread Bastien
Hi Nicolas, Nicolas Goaziou m...@nicolasgoaziou.fr writes: The benefit is that it becomes less clumsy to get rid of the title, when you don't want any. You often want a title, you more rarely want no title. AFAIU, using an empty #+TITLE: is the way to go right now, which seems good enough to

Re: [O] how to use :options-alist in org-export-define-derived-backend ?

2014-07-29 Thread Rasmus
Bastien b...@gnu.org writes: Hi Nicolas, Nicolas Goaziou m...@nicolasgoaziou.fr writes: The benefit is that it becomes less clumsy to get rid of the title, when you don't want any. You often want a title, you more rarely want no title. I disagree. If I want a title I'll be sure to type

Re: [O] how to use :options-alist in org-export-define-derived-backend ?

2014-07-29 Thread Nicolas Goaziou
Hello, Bastien b...@gnu.org writes: Nicolas Goaziou m...@nicolasgoaziou.fr writes: The benefit is that it becomes less clumsy to get rid of the title, when you don't want any. You often want a title, you more rarely want no title. That's true in my case. However, the title I want is never

Re: [O] how to use :options-alist in org-export-define-derived-backend ?

2014-07-29 Thread Bastien
Hi Nicolas, Nicolas Goaziou m...@nicolasgoaziou.fr writes: It is good enough, but the default value (without TITLE) is still dubious. Anyway, this is a minor issue, if at all. Yes. But I know see your point about the default title being useless most of the times. So I'm fine with the

Re: [O] how to use :options-alist in org-export-define-derived-backend ?

2014-07-28 Thread Bastien
Hi Nicolas, Nicolas Goaziou m...@nicolasgoaziou.fr writes: Automatically set document's title to file name or buffer name when no TITLE keyword is provided. I think that's the right thing to do and I don't see the benefits of doing otherwise. In some cases, it even forced me to use better

Re: [O] how to use :options-alist in org-export-define-derived-backend ?

2014-07-28 Thread Nicolas Goaziou
Hello, Bastien b...@gnu.org writes: Nicolas Goaziou m...@nicolasgoaziou.fr writes: Automatically set document's title to file name or buffer name when no TITLE keyword is provided. I think that's the right thing to do and I don't see the benefits of doing otherwise. In some cases, it

Re: [O] how to use :options-alist in org-export-define-derived-backend ?

2014-06-16 Thread Nicolas Goaziou
Bastien b...@gnu.org writes: Okay, but what is the benefit of not using a default title? It removes a hack. But there are other reasons at http://permalink.gmane.org/gmane.emacs.orgmode/86442 (e.g., a default title hardly makes sense anyway). Regards, -- Nicolas Goaziou

Re: [O] how to use :options-alist in org-export-define-derived-backend ?

2014-06-15 Thread Nicolas Goaziou
Completing myself, Nicolas Goaziou m...@nicolasgoaziou.fr writes: Automatically set document's title to file name or buffer name when no TITLE keyword is provided. Implemented in the following patch. WDYT? -- Nicolas Goaziou From 7e917e97f99bf9e9266b64f5066bfaa5f8ca98ee Mon Sep 17 00:00:00

Re: [O] how to use :options-alist in org-export-define-derived-backend ?

2014-06-15 Thread Bastien
Hi Nicolas, Nicolas Goaziou m...@nicolasgoaziou.fr writes: Implemented in the following patch. WDYT? Okay, but what is the benefit of not using a default title? -- Bastien

Re: [O] how to use :options-alist in org-export-define-derived-backend ?

2014-06-14 Thread Nicolas Goaziou
Hello, Bastien b...@gnu.org writes: Nicolas Goaziou n.goaz...@gmail.com writes: Anyway, this bug is due to a cheesy workaround in order to get original file name or buffer name if no title is provided. It should work in maint now, but I suggest to get rid of that behaviour in master, as

Re: [O] how to use :options-alist in org-export-define-derived-backend ?

2014-06-13 Thread Bastien
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: Anyway, this bug is due to a cheesy workaround in order to get original file name or buffer name if no title is provided. It should work in maint now, but I suggest to get rid of that behaviour in master, as suggested in a recent

Re: [O] how to use :options-alist in org-export-define-derived-backend ?

2014-06-03 Thread Bastien
Hi Nicolas, Nicolas Richard theonewiththeevill...@yahoo.fr writes: I'm trying to play with the exporter but I'd like my back-end to have no toc by default. I tried (org-export-define-derived-backend 'mytest 'html :translate-alist ;; don't use the template, concentrate on the toc.

Re: [O] how to use :options-alist in org-export-define-derived-backend ?

2014-06-03 Thread Nicolas Goaziou
Hello, Nicolas Richard theonewiththeevill...@yahoo.fr writes: I'm trying to play with the exporter but I'd like my back-end to have no toc by default. I tried (org-export-define-derived-backend 'mytest 'html :translate-alist ;; don't use the template, concentrate on the toc. (list

[O] how to use :options-alist in org-export-define-derived-backend ?

2014-06-02 Thread Nicolas Richard
Hello, I'm trying to play with the exporter but I'd like my back-end to have no toc by default. I tried (org-export-define-derived-backend 'mytest 'html :translate-alist ;; don't use the template, concentrate on the toc. (list (cons 'template (lambda (a _) a))) :options-alist