From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Re: Suggestion: Replace #+SETUP_FILE with #+INCLUDE
Date: Wed, 10 Oct 2012 14:04:51 -0400 [thread overview]
Message-ID: <86sj9m19vg.fsf@mercure.progiciels-bpi.ca> (raw)
In-Reply-To: <87a9vu5y2e.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 10 Oct 2012 14:08:41 +0200")
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
next prev parent reply other threads:[~2012-10-10 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 12:08 Suggestion: Replace #+SETUP_FILE with #+INCLUDE Nicolas Goaziou
2012-10-10 18:04 ` François Pinard [this message]
2012-10-11 7:51 ` Sebastien Vauban
2012-10-27 7:58 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86sj9m19vg.fsf@mercure.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).