emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: problems with INCLUDE, noweb and tangle
Date: Tue, 09 Dec 2014 14:10:00 +0100	[thread overview]
Message-ID: <86bnndnf4n.fsf@example.com> (raw)
In-Reply-To: 868uihvy4z.fsf@me.localhost.invalid

Daniele Pizzolli wrote:
> Sebastien Vauban writes:
>
>>> Thanks for the clarification.  I did not noticed that before.  I guess
>>> that there is no plan to get this working for the general case, so the
>>> only viable option is using one big .org file.
>>
>> Or use the Library of Babel, if the code you wanna tangle gets
>> eventually used in many different files?
>
> Thanks, I was not aware of this option.  But it seems that the blocks
> are statically added to the variable org-babel-library-of-babel, so when
> I change the included files the changes does not propagate to the
> library of babel automatically.  I also prefer a file based solution
> rather than a global one.

The idea of the LOB is that it's a place where you put all the code
blocks you use in more than one file; you load the LOB, and the code
blocks are in memory -- known, so that you can reference them.

If you need to update them, the easiest is to directly edit them in (one
of) the (many) LOB file(s).

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2014-12-09 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 20:26 problems with INCLUDE, noweb and tangle Daniele Pizzolli
2014-12-09  9:33 ` Nicolas Goaziou
2014-12-09 10:55   ` Daniele Pizzolli
2014-12-09 11:06     ` Sebastien Vauban
2014-12-09 11:52       ` Daniele Pizzolli
2014-12-09 13:10         ` Sebastien Vauban [this message]
2014-12-09 12:55       ` ablepharus

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=86bnndnf4n.fsf@example.com \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).