On Sun, Jan 16, 2011 at 9:31 AM, Eric Schulte wrote:
>
> #+source: wrappable
> #+begin_src emacs-lisp
> (setq x (+ 4 x))
> #+end_src
>
> #+begin_src emacs-lisp :comments noweb :noweb yes :tangle yes
> (let ((x 1))
>(message "x=%s" x)
><>
>(message "x=%s" x))
> #+end_src
>
> which tan
Seth Burleigh writes:
>>As for how to trace back through noweb links, the best option seem to be
>>using the existing jump function to navigate from raw source to the
>>embedded block, keeping track of the point's offset form the beginning
>>of the block, then using `org-babel-expand-src-block' t
>As for how to trace back through noweb links, the best option seem to be
>using the existing jump function to navigate from raw source to the
>embedded block, keeping track of the point's offset form the beginning
>of the block, then using `org-babel-expand-src-block' to expand the body
>of the em
I briefly mentioned the approach you describe below earlier in this
thread [1], and while I see the appeal of this approach, I think that
the second approach I described in that same message (using offsets
instead of comments) is preferable -- although I am of course open to
being persuaded otherwi
I would just like to throw in a quick idea.
The easiest way to support noweb tangling is to get org-babel-tangle to
create nested tags and change detangle to take these into account.
for example, i have the forex_user source block that is tangled.
;; [[file:~/Dropbox/.rep/clj-forex/clj-forex.org:
"Eric Schulte" writes:
> Eric S Fraga writes:
[...]
>> management issue: I find it difficult (a) to remember what all my source
>> code snippets are called and (b) to navigate to any given snippet. I
>> would love to see a babel table of contents popup (a la the table of
>> contents popup wit
woops, what i actually meant is that noweb doesnt work. I was thinking about
it, and it might be possible to
(a) automatically create overlays around begin_src blocks using
auto-overlays
(b) have a custom syntax parser that parses noweb syntax in those blocks.
Sort of like what is done for syntax
Eric S Fraga writes:
> "Eric Schulte" writes:
>
> [...]
>
>> A crude version of the above is already possible using the
>> `org-babel-detangle' function. For example, follow the instructions in
>> the attached org-mode file (which uses elisp rather than clojure code
>> blocks simply for wider p
"Eric Schulte" writes:
[...]
> A crude version of the above is already possible using the
> `org-babel-detangle' function. For example, follow the instructions in
> the attached org-mode file (which uses elisp rather than clojure code
> blocks simply for wider portability to non-clojure users).
Hi Seth,
Thanks for the thoughtful comments. I especially like the method of
literate programming described in your second proposal. Over the last
months I have switched from working mainly in code blocks to working
mainly in pure source files due to issues along the lines of those
mentioned in
Preface: I hope attachments show up, i dont know if they are allowed
Im currently interested in using babel for a medium size clojure project. I
think the below propositions would greatly benefit babel in accomplishing
literate programming.
First part of the proposal to make this painless:
11 matches
Mail list logo
