Re: transclusion, tangling, flycheck/flymake, etc.

[Ihor Radchenko <yantar92@gmail.com>]

Greg Minshall <minshall@umich.edu> writes:

> my thought about flycheck, flymake, whatever, is that (optionally) a
> silent, background, =tangle= and/or =<<noweb>> expansion= would take
> place to produce a "full source file buffer"[*], then the narrowed
> version of that (corresponding to the part where =C-c '= was issued)
> buffer is presented for the user's editing convenience.

You are right. That's what I had in mind. Though noweb <<name()>>-style
references may need to be transcluded without expanding - they may be
computationally expensive.

> your thought here, iiuc, is that source files would live in the file
> system, and be transcluded into the .org file.  i can see the utility of
> that.  but, i would miss =<<noweb>>= and also the ability to break the
> source code into small chunks for purposes of documentation.

No. I did not imply that source files will be transcluded into the .org
file. Currently, .org file is the source of the code (unless you use
org-babel-detangle). I was thinking that C-c ' will trigger generating a
temporary prog-mode buffer (according to .org file!). It is not a good
idea to associate the temporary buffer with actual file because tangling
may involve expanding noweb references. Noweb sometimes require long
computations or even access to remote servers. I think that it's better
to trigger tangle process manually by default.

Best,
Ihor