Hi Eric, Eric Schulte <schulte.e...@gmail.com> writes:
> This is refactoring not bug fixing. The most important impact is that > this will provide for simpler requires by the files implementing support > for particular languages. Rather than having to do piecemeal requires > of those portions of the Babel infrastructure which may be needed > locally they can simple (require 'ob) and bring in all of the Babel > support as a single unit. I agree with the simplification if it does not involved creating ob-core.el and ob-customs.el. Merging ob.el and ob-tangle.el (and perhaps ob-eval.el and ob-comint.el) is a good simplification option IMHO. > Prior to this change there are language specific files which are using > tangle defcustoms which have not been required and thus are not in > scope. Got it. > Finally this consolidates Babel defcustoms into ob.el where they will be > more immediately brought into scope, and are more easily maintained. Yes, if you merge the files; otherwise, I'd stick to the namespace rule: defcustoms belong where their namespace indicate they belong. Thanks, -- Bastien
