Steven Allen <ste...@stebalien.com> writes: > The concern is that, e.g., there may b a function _marked_ as pure > that's not actually pure, leaks some information, and/or has a > security vulnerability (e.g., a C function exposed to lisp that's > marked as pure but internally has, e.g., a buffer overflow).
Are there any functions marked as pure, by default? > 1. Allow them in both #+LINK: lines and the global > org-link-abbrev-alist. > > 2. Allow them in org-link-abbrev-alist only. > > 3. Remove them entirely. If no functions are marked as pure by default, 1 seems reasonable to me. If some functions are marked as pure by default (by Emacs / Org mode), then 2 seems reasonable. I believe 3 is excessive. -- Suhail
