On 2016-02-16 18:34, "Charles C. Berry" writes:
>> I've found a workaround, as it is only for a few blocks I manually
>> change their headers, so it is fine at the moment.
>
> Another workaround would be to add after advice to
> `org-babel-get-src-block-info' to map your faux languages to a comm
On Tue, 16 Feb 2016, Alan Schmitt wrote:
On 2016-02-16 12:42, John Kitchin writes:
I think you are seeing that the blocks are tangled in reverse. If I add a third
arbitrary lang it comes in reverse.
Interesting! Thanks a lot for trying it.
I see that I made the typical scientific method mi
On 2016-02-16 12:42, John Kitchin writes:
> I think you are seeing that the blocks are tangled in reverse. If I add a
> third
> arbitrary lang it comes in reverse.
Interesting! Thanks a lot for trying it.
I see that I made the typical scientific method mistake of testing for
my hypothesis, ins
I think you are seeing that the blocks are tangled in reverse. If I add a
third arbitrary lang it comes in reverse.
If they are all the same language, they are in the right order. It looks
like org collects by language, so your strategy won't work with org-babel
tangle I guess.
On Tue, Feb 16, 20
Hello,
I thought the order source blocks were tangled was the order of the
file. I just discovered this is not necessarily the case. This file:
--8<---cut here---start->8---
#+BEGIN_SRC foob :tangle foo.ml
let x = 1
#+END_SRC
#+BEGIN_SRC fooa :tangle foo.ml
le
