From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Config best practices?
Date: Sat, 21 Mar 2015 09:01:46 -0400 [thread overview]
Message-ID: <874mpezepx.fsf@pierrot.dokosmarshall.org> (raw)
In-Reply-To: 86a8z6y9ec.fsf@example.com
Sebastien Vauban <sva-news@mygooglest.com>
writes:
> Marcin Borkowski wrote:
>> On 2015-03-21, at 04:05, Nick Dokos <ndokos@gmail.com> wrote:
>>
>>> Yes, but why do you do that? What are you trying to accomplish? What
>>> does "keeping the configuration in order" mean?
>>
>> I have that org-one-to-many utility, which splits the Org file at
>> (selected) headings, effectively making them separate Org files. If
>> I e.g. use LaTeX macro definitions, or custom (per-file) TODO keywords
>> in that file, it makes sense to put the same configs in the files split
>> from the main one. Putting them into their own headline may be the
>> simplest way to tell org-one-to-many what to copy to each generated
>> file.
>>
>> I don't like putting them at the top; while #+TITLE or #+AUTHOR do make
>> sense there (and don't in the split files!), cluttering the first few
>> screens with e.g. LaTeX definitions is not my favorite way of using
>> Org-mode.
>
> As I wrote, you could choose for an ARCHIVE'd heading (one that's
> always collapsed) or for a SETUPFILE?
>
The SETUPFILE sounds to me like the best solution, assuming that the
different files are sharing configuration.
--
Nick
prev parent reply other threads:[~2015-03-21 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 0:14 Config best practices? Marcin Borkowski
2015-03-20 9:07 ` Sebastien Vauban
2015-03-20 23:18 ` Marcin Borkowski
2015-03-20 23:27 ` Rasmus
2015-03-21 3:05 ` Nick Dokos
2015-03-21 8:09 ` Sebastien Vauban
2015-03-21 12:56 ` Nick Dokos
2015-03-21 9:15 ` Marcin Borkowski
2015-03-21 9:42 ` Sebastien Vauban
2015-03-21 13:01 ` Nick Dokos [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mpezepx.fsf@pierrot.dokosmarshall.org \
--to=ndokos@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.