Ihor Radchenko writes: > This would not solve the problem of shadowing. > It may be better idea to provide a custom variable controlling > org-babel-speed-command-activate: do nothing or throw an error. > This custom variable should also be described in the docstring of > org-speed-command-hook to warn about potential shadowing. > > To summarise, your idea will be reasonable if: > 1. The new behaviour can be customized > 2. The new behaviour is documented in org-speed-command-hook
Ok, I agree that this is the most reasonable direction. What do you think about the idea that I outlined in the last post of this thread (https://list.orgmode.org/87v8uqmkc0....@posteo.net/)?: it consists in defining a new hook (by default with value nil) where the user can store those functions that he wants to have a 'strict' behavior: some functions or all. And then the user should add the org-speed-command-strict-function to org-speed-command-hook. If this idea sounds too hacky, I think a defcustom for org-babel-speed-command-activate, as you suggest, might suffice. Best regards, Juan Manuel
