* Suggestion: Replace #+SETUP_FILE with #+INCLUDE
@ 2012-10-10 12:08 Nicolas Goaziou
2012-10-10 18:04 ` François Pinard
2012-10-27 7:58 ` Bastien
0 siblings, 2 replies; 4+ messages in thread
From: Nicolas Goaziou @ 2012-10-10 12:08 UTC (permalink / raw)
To: Org Mode List
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.org"
The only difference is that contents of #+SETUP_FILE are not included in
the final document; they are just read. The only use case I can think of
is when one's want to share the same keywords as a file but without its
contents. But then, it's possible to strip keywords from both files and
store them in a third one, that will be included everywhere.
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?
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Suggestion: Replace #+SETUP_FILE with #+INCLUDE
2012-10-10 12:08 Suggestion: Replace #+SETUP_FILE with #+INCLUDE Nicolas Goaziou
@ 2012-10-10 18:04 ` François Pinard
2012-10-11 7:51 ` Sebastien Vauban
2012-10-27 7:58 ` Bastien
1 sibling, 1 reply; 4+ messages in thread
From: François Pinard @ 2012-10-10 18:04 UTC (permalink / raw)
To: emacs-orgmode
Nicolas Goaziou <n.goaziou@gmail.com> 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 easily adapt! :-)
François
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Suggestion: Replace #+SETUP_FILE with #+INCLUDE
2012-10-10 18:04 ` François Pinard
@ 2012-10-11 7:51 ` Sebastien Vauban
0 siblings, 0 replies; 4+ messages in thread
From: Sebastien Vauban @ 2012-10-11 7:51 UTC (permalink / raw)
To: emacs-orgmode-mXXj517/zsQ
Hello Nicolas,
François Pinard wrote:
> Nicolas Goaziou <n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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 easily adapt! :-)
Fine with me. This makes a lot of sense, when they don't differ that much, and
when we don't know exactly which one to use in which context (= my view).
Best regards,
Seb
--
Sebastien Vauban
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Suggestion: Replace #+SETUP_FILE with #+INCLUDE
2012-10-10 12:08 Suggestion: Replace #+SETUP_FILE with #+INCLUDE Nicolas Goaziou
2012-10-10 18:04 ` François Pinard
@ 2012-10-27 7:58 ` Bastien
1 sibling, 0 replies; 4+ messages in thread
From: Bastien @ 2012-10-27 7:58 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: Org Mode List
Hi Nicolas,
Nicolas Goaziou <n.goaziou@gmail.com> 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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-10-27 7:58 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-10-10 12:08 Suggestion: Replace #+SETUP_FILE with #+INCLUDE Nicolas Goaziou
2012-10-10 18:04 ` François Pinard
2012-10-11 7:51 ` Sebastien Vauban
2012-10-27 7:58 ` Bastien
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).