search

preservim / vim-textobj-quote

Use ‘curly’ quote characters in Vim
Other
123 stars 6 forks source link

scriptencoding utf-8 not allowed in sandbox #17

Closed mcepl closed 4 years ago

mcepl commented 6 years ago

When starting vim with the file which activates call textobj#quote#init (actually, neovim from git (commit neovim/neovim@e46534b42 ) I get this error:

Error detected while processing \
    /home/matej/.vim/pack/minpac/start/vim-textobj-quote/autoload/textobj/quote.vim:                                                                      
line    9:                                                                                 
E48: Not allowed in sandbox: scriptencoding utf-8

I don't know if it matters, we could use "\u02a4" instead of switching scriptencoding.

After that something is wrong, e.g., :w says E13: File exists (add ! to override), I have to run :w! to save the file.

mcepl commented 6 years ago

See my rumination on the pull request #18.

mcepl commented 6 years ago

This one happened when I run :e filename.rst:

Error detected while processing function TextObjSettings[3]..textobj#quote#init[21]..textob
j#user#plugin:                                                                             
line    9:                                                                                 
E48: Not allowed in sandbox: command! -bang -bar -nargs=0 TextobjQuoteDefaultKeyMappings ca
ll g:__textobj_quote.define_default_key_mappings("<bang>" == "!")

Why are all these commands running in the sandbox?

mcepl commented 6 years ago

I can reproduce with vim8 as well (VIM - Vi IMproved 8.0 (2016 Sep 12, compiled May 11 2018 15:16:16) Included patches: 1-1813).

bergercookie commented 5 years ago

Hi there,

I'm facing a similar issue with this plugin. I'm apparently running in a sandbox when I open any ruby script from neovim. In your case why were you running in a sandbox in the first place?

Thanks, Nikos

mcepl commented 4 years ago

Hmm, I am not sure, what happened, but I haven’t seen this issue some time already. Let’s not bother upstream with it.