Thank you so much @cpitclaudel! What workflow would you recommend for me, who has a literate init file with many source blocks? When I use flycheck on this revision I get errors now, but they're mostly of the form "the function foo is not known to be defined", and I don't want to put a bunch of require statements at the front of every source block. It feels like currently every source block is like its own package.

What workflow would you recommend for me, who has a literate init file with many source blocks? It feels like currently every source block is like its own package.

It's quite tricky. Your description is exactly right.

Ideally, you'd want org to create an indirect buffer that has all your snippets in it, and narrow it to the snippet you're editing. Then Flycheck and Emacs would see the whole context.

Is there a generic way (in org-mode) to extract all snippets that a snippet depends on?

I've updated the PR to make it more robust. Can you give it a new try and tell me if it still gives you errors (the update won't improve things in terms of spurious errors)

Ideally, you'd want org to create an indirect buffer that has all your snippets in it, and narrow it to the snippet you're editing. Then Flycheck and Emacs would see the whole context.

Is there a generic way (in org-mode) to extract all snippets that a snippet depends on?

Well there's tangling. If I jump to definition (xref-find-definition) in main.org, it jumps me to the tangled main.el file, even if the definition being jumped to is in the same snippet. If flycheck used main.el as the backing file for errors, while using the snippet buffer for error location data, then I think that would do it. Keeping them in sync is another issue though. Maybe I should look into Org Tanglesync.

I've updated the PR to make it more robust. Can you give it a new try and tell me if it still gives you errors (the update won't improve things in terms of spurious errors)

Confirmed, still works on 33f2b01.

Well there's tangling

Right. Ideally, that temporary buffer that org gives you should be the full tangled file, narrowed to just the snippet that you're editing. That's a discussion that would be better taken to the org-mode list, though.

Confirmed, still works on 33f2b01.

Thanks!

That's a discussion that would be better taken to the org-mode list.

Quite right. Never did figure out how to use it, to be honest. If only they had a status-based bug tracker…