emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Daly <nick.m.daly@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature Request: Allow Tangling Named INCLUDEs
Date: Sun, 26 Jan 2014 18:44:43 -0600	[thread overview]
Message-ID: <87ob2y5k3o.fsf@gmail.com> (raw)
In-Reply-To: <877g9w9d10.fsf@bzg.ath.cx>

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

Hi Bastien,

> Nick Daly wrote:
>
>> Hi folks, I have a situation where I have many named code snippets
>> currently available in external files, and would like to tangle them
>> into an Org mode file.

Bastien writes:
> I'm not the one who would undertake this, so my opinion on this should
> not matter much... but I think #+INCLUDE is well suited for exporting,
> not for tangling.  I'm not able to say why, this is just an intuition.

It seems to me like it's trying to unify exporting and tangling: this
emphasizes that tangling is just another (very specific plain-text) form
of exporting.  Using Eric's function for exporting allows me to remove
lots of boilerplate code from the source org file and keep the org
source better focused on the code's function and structure.

Sure it's weird, but it sure is handy.

Nick

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2014-01-27  0:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11 21:04 Feature Request: Allow Tangling Named INCLUDEs Nick Daly
2014-01-19 16:01 ` Bastien
2014-01-27  0:44   ` Nick Daly [this message]
2014-01-27  9:26     ` Rainer M Krug
2014-01-27 14:37       ` Eric Schulte
2014-01-28  8:12         ` Rainer M Krug
2014-01-27 14:40     ` Eric Schulte
2014-01-20 16:19 ` Eric Schulte
2014-01-27  0:36   ` Nick Daly
2014-01-20 16:20 ` Eric Schulte

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=87ob2y5k3o.fsf@gmail.com \
    --to=nick.m.daly@gmail.com \
    --cc=bzg@gnu.org \
    --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).