Tom Gillespie <tgb...@gmail.com> writes: > Here is a fix for bad init values for org-babel-tangle-lang-exts. > Details in the patch commit message. > ... > Subject: [PATCH] initialize org-babel-tangle-lang-exts to nil > ... > org-bable-tangle-lang-exts should be initialized to nil and not as a > void variable, if it is not already initialized then this will cause a > void-variable error immediately when it is used in add-to-list > > this corrects the original addition in > 4a0e5cf88f684db775ccf43dc5edc2e8754a2d92 as well as other files that > followed the pattern
Thanks for the patch, but it is not a correct way to fix the problem. `org-babel-tangle-lang-exts' is a custom option defined in ob-tangle.el. If you define it as a global variable separately, there will be subtle bugs depending on the order of loading of ob-tangle and the other files defining the same variable. Currently, it is expected that babel backends *must* be loaded after ob-tangle. More accurate approach would be using (eval-after-load 'ob-tangle ...). This is what is being done in WIP branch that addresses many similar problems across Org mode: https://git.sr.ht/~yantar92/org-mode/log/feature/refactor-deps-v2 https://git.sr.ht/~yantar92/org-mode/commit/6bcb99413e18324367fa27f8572955d5a92092ce Canceled. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
