all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Robert Klein <roklein@roklein.de>
Cc: Marco Wahl <marcowahlsoft@gmail.com>,
	emacs-orgmode@gnu.org, Harry Butterworth <heb1001@gmail.com>
Subject: Re: Tangling include files
Date: Thu, 24 Nov 2016 09:56:32 -0800	[thread overview]
Message-ID: <alpine.OSX.2.20.1611240933060.703@charles-berrys-macbook.local> (raw)
In-Reply-To: <20161124100004.40b85423@pckr186.mpip-mainz.mpg.de>

On Thu, 24 Nov 2016, Robert Klein wrote:

> On Wed, 23 Nov 2016 21:22:08 -0800
> "Charles C. Berry" <ccberry@ucsd.edu> wrote:
>
>> On Thu, 24 Nov 2016, Harry Butterworth wrote:
>>
>>> I tried org-org-export-to-org which puts everything into a single
>>> document but it strips the :tangle parameters out so a subsequent
>>> tangle doesn't generate any source code.
>>>
>>
>> You might try this. Put this at the *top* of your file:
>>
>> --8<---------------cut here---------------start------------->8---
>>
>> #+PROPERTY: header-args :eval never-export
>>

[deleted]

>
> A line
>
> #+Property: tangle yes

That idiom is *obsolete* and *deprecated* for a long time and 
*incompatible* as of org 9.0.

>
> in your org document is sufficient to get it tangled (in org 8.3.6).
>

The point of that line was to prevent unwanted evaluation. Presumably, OP 
had :tangle headers in the desired locations in the original org file.

Chuck

      reply	other threads:[~2016-11-24 17:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23  8:24 Tangling include files Harry Butterworth
2016-11-23  9:47 ` Marco Wahl
2016-11-24  4:00   ` Harry Butterworth
2016-11-24  5:22     ` Charles C. Berry
2016-11-24  9:00       ` Robert Klein
2016-11-24 17:56         ` Charles C. Berry [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.OSX.2.20.1611240933060.703@charles-berrys-macbook.local \
    --to=ccberry@ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=heb1001@gmail.com \
    --cc=marcowahlsoft@gmail.com \
    --cc=roklein@roklein.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.