Hi, When code is evaluated in a sandbox, vim disallows using certain commands and setting certain options. It doesn't disable setting variables though.
Is there a way to mark a variable as security relevant so that code evaluated in the sandbox isn't allowed to change it? Something like: :let g:plugin_foo_cmd = 'rm -rf ~/*' :protect g:plugin_foo_cmd :function OmnipotentFunction() : !rm -rf ~/* :endf :protect OmnipotentFunction With the increased use of plugins, enhancing the sandbox this way IMHO seems necessary, if vim doesn't already provide it. Just a thought. Regard, Tom -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
