From: Nick Dokos <email@example.com>
Subject: Re: [PATCH] ob-core: tangle check library of babel after current buffer
Date: Sat, 17 Jul 2021 16:33:04 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Tom Gillespie <email@example.com> writes:
> Pinging on this to see if anyone can test it so that it can be merged.
> On Wed, Jun 16, 2021 at 4:29 PM Tom Gillespie <firstname.lastname@example.org> wrote:
>> This is a patch that fixes tangling behavior when a block has been
>> ingested into the library of babel and then modified. Best!
I have not tested it but I reviewed the code and it looks good to me.
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
next prev parent reply other threads:[~2021-07-17 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 23:29 [PATCH] ob-core: tangle check library of babel after current buffer Tom Gillespie
2021-07-17 17:42 ` Tom Gillespie
2021-07-17 20:33 ` Nick Dokos [this message]
2021-07-17 21:40 ` Rodrigo Morales
2021-07-24 19:41 ` Timothy
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).