Re: [O] Suggestion: Replace #+SETUP_FILE with #+INCLUDE

2012-10-27 Thread Bastien
Hi Nicolas, Nicolas Goaziou writes: > Therefore, I don't see any reason to keep maintaining the #+SETUP_FILE > keyword. I'd rather remove it and suggest to use #+INCLUDE: keyword > instead. > > Any objection? FWIW, none on my side. Thanks, -- Bastien

Re: [O] Suggestion: Replace #+SETUP_FILE with #+INCLUDE

2012-10-11 Thread Sebastien Vauban
Hello Nicolas, François Pinard wrote: > Nicolas Goaziou writes: > >> Therefore, I don't see any reason to keep maintaining the #+SETUP_FILE >> keyword. I'd rather remove it and suggest to use #+INCLUDE: keyword >> instead. Any objection? > > None really. I use both and distinguish them in some

Re: [O] Suggestion: Replace #+SETUP_FILE with #+INCLUDE

2012-10-10 Thread François Pinard
Nicolas Goaziou writes: > Therefore, I don't see any reason to keep maintaining the #+SETUP_FILE > keyword. I'd rather remove it and suggest to use #+INCLUDE: keyword > instead. Any objection? None really. I use both and distinguish them in some validation tool, which I would happily and easil

[O] Suggestion: Replace #+SETUP_FILE with #+INCLUDE

2012-10-10 Thread Nicolas Goaziou
Hello, I'd like to remove #+SETUP_FILE (that is #+SETUPFILE in the old exporter) from the new exporter. The reasoning behind this is that #+INCLUDE already provides a similar feature (and some others). I.e. you can almost always do: #+INCLUDE: "my-setup.org" instead of #+SETUP_FILE: "my-setup.