emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Davison <davison@stats.ox.ac.uk>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [OT] Re: Include files to be used in literate programming
Date: Mon, 13 Sep 2010 14:23:55 -0400	[thread overview]
Message-ID: <87mxrlqz7o.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <81pqwhefpp.fsf_-_@gmail.com> (Jambunathan K.'s message of "Mon, 13 Sep 2010 22:35:54 +0530")

Jambunathan K <kjambunathan@gmail.com> writes:

> Dan Davison <davison@stats.ox.ac.uk> writes:
>
> [Warning: OT]
>
>>  tangling is not (technically at least) an Org-mode export method. 
>
> This is an implementation artefact (as you have noted). 
>
>From a user-perspective tangling is a specialized form of export.

I think I agree with that. I wonder if it would be helpful to more
formally recognise tangling as a form of export. For example, in one of
the other threads, you were talking about selective tangling. If
tangling were treated as a form of export, presumably that would mean
that tangling would obey the tag-based selective export mechanisms
(variables org-export-select-tags and org-export-exclude-tags), and also
that #+INCLUDE would have the semantics expected by the OP.

[...]

> May be in coming days I should be able to make concrete, code-level
> suggestions on that would take my prayers further down in your altar
> :-).

I've certainly read your recent series of emails and the resulting
discussion. But of course time is the major limiting factor, and I
haven't yet managed to properly get my head round the various ideas that
have been discussed. Would you be able to provide a brief summary of the
series of emails? If you could identify one or a few core proposal(s)
and be explicit about exactly what changes in behaviour you're
suggesting, and whether they would be backwards compatible, that could
be very helpful.

Dan

>
> Meanwhile I invite you to give my posts some thought ... Dan or Eric
> could churn out babel code faster and more effectively than I could
> possibly could.
>
> Jambunathan K.

  reply	other threads:[~2010-09-13 18:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-12 17:02 Include files to be used in literate programming Giorgio Valoti
2010-09-13 12:47 ` Dan Davison
2010-09-13 15:17   ` Giorgio Valoti
2010-09-13 15:39   ` Rainer M Krug
2010-09-13 17:05   ` [OT] " Jambunathan K
2010-09-13 18:23     ` Dan Davison [this message]
2010-09-13 19:04       ` Jambunathan K
2010-09-17 12:51 ` 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=87mxrlqz7o.fsf@stats.ox.ac.uk \
    --to=davison@stats.ox.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \
    /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).