2017-09-18 5:52 GMT+03:00 Prabir Shrestha <[email protected]>: > I'm currently working on some plugins that requires heavy processing and > would like if I could process this in a different process instead of main ui > thread in vimscript using just vim without any extra dependencies for the > users. > > For example in asyncomplete.vim I would like to implement fuzzy search that > doesn't block the ui thread. > In vim-lsp language servers are started in different process but it needs to > interact with vimscript using stdio and jsonrpc which means there are lot of > json_encode and json_decode happening in vimscript that would slow down vim. > > While I could use jobs to offload the heavy task to different process it > isn't portable as vimscript where it just works out of the box for the user. > For example: If I write the external job in python or other scripting > languages I need to make sure vim users have python or that scripting > language installed. If I distribute it as binaries I need to make sure I > distribute the compiled binary or instructions on how to compile which is an > extra step for the user. > > The next version of Neovim will have remote plugin that can be coded in lua > and they can guarantee that remote lua plugin will always work. Is it > possible to have something like this in vim8? I would like to be able to > write a plugin in lua that starts as a process and can communicate back to > vim and can assume that it always work for anyone who has vim installed.
I do not remember anything about exactly out-of-process lua plugins, though we should have guaranteed support for +lua in the future and already have support for built-in lua plugins, but without Vim compatibility layer yet. What you are asking is actually a fork() support, which with linked in liblua[jit] will yield the desired result; anything else requires setting up $PATH and/or some option like g:nvim_lua_executable_path. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > > -- > -- > 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 > > --- > You received this message because you are subscribed to the Google Groups > "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
