On Thu, 02 Sep 2010 14:43:07 +0200, Sébastien Vauban wrote: > > Hi Eric(s) and Dan, > > Eric S Fraga wrote: > > On Wed, 01 Sep 2010 13:25:35 +0200, Sébastien Vauban wrote: > >>>>> I have just placed on Worg [1] a short tutorial/example for using > >>>>> ledger with babel. Please have a look and comment etc! > >>> > >>> [1] http://orgmode.org/worg/org-contrib/babel/languages.php#langs > >> > >> Being interested a lot in Ledger integration with Org-Babel as well, I have a > >> quick remark: instead of including (with explicit full path) the journal > >> entries in every code block, can't we use the more natural (at least, to me) > >> tangling provided by the Noweb syntax? > > Yes, I would have thought that this would work. It doesn't fit in naturally > > with how I would like to do things as I have many different blocks of ledger > > entries spread around the file... > > I don't understand your argument: why wouldn't you use <> blocks > and <> blocks for example, or even much more? What am I missing? You are not missing anything at all! I didn't say it couldn't be done; I just said that it didn't fit in with *my* workflow. I have many (tens) of little to medium sized ledger snippets throughout my personal finances org file. As well as collections of entries (for regular payments, say), the set of snippets includes one-off expenses (e.g. bought a specific piece of furniture for the house) that I want to record and annotate. Labelling all of these snippets and then putting in the <<...>> entry in the full list gives two extra steps. Instead, I create as many snippets as I want without worrying about it and I simply have to /tangle/ before evaluating any of the financial summary ledger snippets. This minimises, for me, the number of things I need to remember to keep track of my finances. The other extreme is to simply put *all* ledger entries in one source block but then you might as well use a ledger file directly... Your suggestion fits bang in the middle and: > What cannot be done with the noweb syntax in your Org file? I find it much > better if we can avoid specifying explicit paths, in order to guarantee use > and execution of our Org files by other users, on other (even Windows) > machines, among others. I agree completely with this. The tutorial probably did not reflect what is likely to be the most common and more robust usage. Sorry!