From: Rainer M Krug <r.m.krug@gmail.com>
To: ian@manor-farm.org
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Babel Tangling Only Blocks Under One Heading in a File with Multiple Blocks.
Date: Tue, 22 Nov 2011 14:46:06 +0100 [thread overview]
Message-ID: <CAGhLh6H1MvKde_d7AUQbEHNBcr5JZkJ+v+UyUKEbNP=NUtT5=g@mail.gmail.com> (raw)
In-Reply-To: <4ECBA544.5010006@wilkesley.net>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
On Tue, Nov 22, 2011 at 2:36 PM, Ian Barton <lists@wilkesley.net> wrote:
> I am using org to keep configuration files for my various servers. A
> typical file might look like:
>
> * Postfix
> ** main.cf
> #+BEGIN_SRC sh :tangle ~/dropbox/configuration_files/**
> wilkesley.org/postfix/main.cf <http://wilkesley.org/postfix/main.cf>:exports none :noweb yes
>
> #+END_SRC
> ** master.cf
>
> * Dovecot
> ** dovecot.conf
>
> Mostly I only change one configuration file and don't need to tangle every
> block in my org file. Is there any method to only tangle files under a
> particular heading? Thus I could regenerate just my Postfix config files
> and not my Dovecot ones.
>
Check org-narrow-to-subtree - you can narrow to subtree and then tangle.
Cheers,
Rainer
>
> Ian.
>
>
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax (F): +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: Rainer@krugs.de
Skype: RMkrug
[-- Attachment #2: Type: text/html, Size: 1990 bytes --]
next prev parent reply other threads:[~2011-11-22 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 13:36 Babel Tangling Only Blocks Under One Heading in a File with Multiple Blocks Ian Barton
2011-11-22 13:46 ` Rainer M Krug [this message]
2011-11-22 14:02 ` Ian Barton
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='CAGhLh6H1MvKde_d7AUQbEHNBcr5JZkJ+v+UyUKEbNP=NUtT5=g@mail.gmail.com' \
--to=r.m.krug@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ian@manor-farm.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).