Define the library-of-babel files and the source files at run-time

[aldrichtr]

Overview

Since named code blocks are only available to be called if they are in the same file, or in the library-of-babel, it would be convenient to be able to configure which files are in the lib and which ones are source at run-time. I can think of two use cases:

1. std-lib type functions and data
2. a collection of files to be "compiled" into one file

std-lib type

Most programming languages have a standard library of functions and data that developers can use in their programs. As a =tangld= project grows, functions that the user wants to reuse in several places would naturally migrate to the library.

many-to-one

For large configuration files (like, uhm... init.el) it can be useful to divide the components up into "chunks" that are saved in separate files. The blocks in the separate files would be "called" by the main file, for example, divide the init.el up into packages:

- helm.org
- magit.org
- ...
- init.org

and then in init.org

#+BEGIN_SRC emacs-lisp
<<helm_package>>
<<magit_package>>
#+END_SRC