tarruda

56 ms·

1. 691.▲
   by tarruda 13y ago

   I am enthusiastic about it, thats why I started the fundraiser. To finish the first iteration fast I need to put my freelance work to a halt.
2. 692.▲
   by tarruda 13y ago

   I greatly appreciate it, thanks :)
3. 693.▲
   by tarruda 13y ago

   As the author I would like to contribute changes back, search vim_dev mailing list for 'message loop' and 'job control' and you will find two patches I've sent that werent even commented by Bram. This fork changes s
4. 694.▲
   Neovim(github.com)

   879 points by tarruda 13y ago|362 comments
5. 695.▲
   by tarruda 13y ago

   All that does is display a popup on the desktop, it does nothing to notify/callback to the vimscript code that started the process
6. 696.▲
   by tarruda 13y ago

   Actually, python interop was only a for quickly testing multi-threaded plugins. See the issue tracker for examples of vimscript functions that can be added on top of the message queue: https://github.com/tarruda/vim&#x2
7. 697.▲
   by tarruda 13y ago

   The redraw issue is also related to vim not being thread-safe. With this fork youcompleteme can probably do something like 'vim.defer("YcmTriggerSyntastic")' from a background thread to invoke syntastic and redraw the sc
8. 698.▲
   by tarruda 13y ago

   Perhaps with enough pressure from the community there's a chance this will happen? Meanwhile I will keep maintaining the fork up-to-date with upstream, so plugins can make use of the patch through a simple 'if has("messageque
9. 699.▲
   by tarruda 13y ago

   I agree, but how do you get notified that 'long-process' finished running? Even if you poll using CursorHold-like hacks the user still needs to type something.
10. 700.▲
    An experimental Vim fork with multi-threading capabilities(github.com)

    75 points by tarruda 13y ago|33 comments
11. 701.▲
    Run virtualbox headless as windows tray icon (github.com)

    1 points by tarruda 14y ago|0 comments