From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Config best practices?
Date: Fri, 20 Mar 2015 23:05:23 -0400 [thread overview]
Message-ID: <87h9tfyrrg.fsf@pierrot.dokosmarshall.org> (raw)
In-Reply-To: 87oannntpg.fsf@wmi.amu.edu.pl
Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
> On 2015-03-20, at 10:07, Sebastien Vauban <sva-news@mygooglest.com> wrote:
>
>> Hello Marcin,
>>
>> Marcin Borkowski wrote:
>>> I'm wondering what people do to keep the configuration of their Org
>>> files in order.
>>
>> I'm not sure to correctly grasp your objective. Could you restate it?
>
> Sure.
>
> Where do you put things like
>
> #+OPTIONS: toc:nil
>
> or
>
> #+SEQ_TODO: TODO | DONE
>
> or
>
> #+LATEX_HEADER: \newcommand{\eps}{\varepsilon}
>
> ?
>
>>> I use a dedicated top-level headline, with a COMMENT keyword, but
>>> I started to think that a :noexport: tag might be a better idea.
>>>
>>> Are there any advantages of one over the other, or other approaches
>>> altogether?
>>
>> I can tell you they aren't isomorphic... The noexport tag simply says
>> "don't export this subtree". The COMMENT keyword adds "don't run any
>> Babel code block in there".
>
COMMENT also says that the whole subtree is not to be exported according
to the doc:
(info "(org) Comment lines")
Has that changed?
> So I guess that – since the lines with options etc. are not exported
> anyway – that using a :noexport: tag might be a better idea. Am I right?
>
>>> The reason I'm asking is that I'm tweaking my org-one-to-many utility
>>> so that it propagates the config to all the generated files.
>>
>> Still not that clear to me. Maybe an ECM would clarify your request?
>
> As you wish. This is what I usually do.
>
> * Headline
> * Another one
> ** Subheadline
> * COMMENT Config
> #+LATEX_HEADER: \newcommand{\eps}{\varepsilon}
> #+SEQ_TODO: TODO | DONE CANCEL
> #+OPTIONS: toc:nil
>
Yes, but why do you do that? What are you trying to accomplish? What
does "keeping the configuration in order" mean?
I sometimes use a Setup heading marked with COMMENT, so it does not get
exported. I never put babel stuff in there so I haven't worried about
that, but if Seb is correct that it prevents babel from evaluating
things in the subtree, that's a bonus. If you are just trying to
(mostly) hide it from view, add an :ARCHIVE: tag to the heading.
But most of the time I have them at the top of the file in plain view.
--
Nick
next prev parent reply other threads:[~2015-03-21 3:05 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 [this message]
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
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=87h9tfyrrg.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 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).