Hi Tom,
Sorry that it's taken so long for someone to get to this. I've just
applied your patch to my local Org instance, and then tested the
described behaviour before and afterwards. I can confirm that the issue
reported exists, and that your patch fixes this.
In light of this and the two othe
Tom Gillespie writes:
> Pinging on this to see if anyone can test it so that it can be merged.
> Tom
I agree with this patch.
Just to make clear the default behavior and the behavior that would
exist with this patch.
The current behavior
1. You have a code block C1 in a buffer B1.
2. You exec
Tom Gillespie writes:
> Pinging on this to see if anyone can test it so that it can be merged.
> Tom
>
> On Wed, Jun 16, 2021 at 4:29 PM Tom Gillespie wrote:
>>
>> Hi,
>>This is a patch that fixes tangling behavior when a block has been
>> ingested into the library of babel and then modified
Pinging on this to see if anyone can test it so that it can be merged.
Tom
On Wed, Jun 16, 2021 at 4:29 PM Tom Gillespie wrote:
>
> Hi,
>This is a patch that fixes tangling behavior when a block has been
> ingested into the library of babel and then modified. Best!
> Tom
: tangle check library of babel after current buffer
* lisp/ob-core.el (org-babel-expand-noweb-references): Fix order when
searching for named babel blocks so that blocks in the current buffer
are always found first. This fixes a bug where stale versions of
blocks that have been ingested into the library
