emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Julian Burgos <julian@hafro.is>
Cc: emacs-orgmode@gnu.org
Subject: Re: buffer-wide tangle filename
Date: Thu, 29 Mar 2012 09:47:28 +0200	[thread overview]
Message-ID: <4F741390.9020209@christianmoe.com> (raw)
In-Reply-To: <10986.>

Hi, Julian,

See if it helps to fix a small syntax error: drop the colon before 
"tangle", and place it after #+PROPERTY instead.

#+PROPERTY: tangle output.el

The colon in ":tangle" is needed when you're providing a header 
argument to a src block, but not when you're setting buffer-wide 


On 3/29/12 3:25 AM, Julian Burgos wrote:
> Hello everyone,
> This may be a very simple question.  I want to tangle multiple source code
> blocks into a single file.  Instead of using the same output filename as a
> block header (e.g. :tangle output.el) in each code block, can I I define a
> buffer-wide tangle filename?  Something like this (which does not work)?
> #+PROPERTY :tangle output.el
> Any ideas?
> Julian

  reply	other threads:[~2012-03-29  7:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29  1:25 buffer-wide tangle filename Julian Burgos
2012-03-29  7:47 ` Christian Moe [this message]
2012-03-29  7:56   ` Rainer M Krug
2012-03-29  7:57 ` Sebastien Vauban
2012-03-29  8:20   ` Julian Burgos
2012-03-29  8:27 ` Martyn Jago

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=4F741390.9020209@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=julian@hafro.is \


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