emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Config best practices?
Date: Sat, 21 Mar 2015 00:27:41 +0100	[thread overview]
Message-ID: <87619vz1ua.fsf@gmx.us> (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 usually have something like

* export options :noexport:
# whatever.

But in e.g. ox-koma-letter I'd just have

* attachments and export options :after-letter:
% Enclosure commands
# whatever

Generally, I try to minimize the number of (i) hacks outside of org-core
(e.g. :ignoreheading:); (ii) number of headings without exported content.


And I faced endless streams of vendor-approved Ikea furniture. . .

  reply	other threads:[~2015-03-20 23:30 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 [this message]
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

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:

  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=87619vz1ua.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \


* 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


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).