On Tuesday, January 14, 2014 4:03:21 PM UTC-8, Thiago Arruda wrote: > On Tue, Jan 14, 2014 at 7:10 PM, kans <[email protected]> wrote: > > > Thiago, > > > > > > I am not hopeful for this patch, but I would love to see you succeed. We > > spent around two months working on adding async support to Vim without > > threads, https://groups.google.com/d/msg/vim_dev/-4pqDJfHCsM/LkYNCpZjQ70J . > > We added a timer function and called the callbacks in the main loop when > > appropriate. Ultimately, we gave up for a few reasons: > > > > > > 1. A large percent of the Vim community was outright hostile to the idea. > > > 2. Bram was disinterested > > > 3. Vim was unstable with the patch (segfaults outside of the patched code) > > AND > > > 4. The Vim code base is abysmal. > > > > > > How stable is this patch and what do you think about cross platform support? > > > > > > -Matt > > > > Thanks Matt > > > > Its very stable for me, the only problem I could detect was test94 > > failure. I dont think cross-platform is an issue as the only > > dependency this patch introduces is pthreads, which is available in > > windows through the pthreads-win32 library. > > > > I'm not raising my hopes too high, but in any case I think this patch > > can be used as a base for a modern vim fork so I will keep maintaining > > it. > > > > About your patch, I was sorry it didnt get accepted. Even so I > > encourage you to join me as the timer functions proposed in your patch > > can easily be implemented on top of a message queue. I have enabled > > the issue tracker at https://github.com/tarruda/vim to document > > pending issues and extend discussions.
Thiago, It would be rather trivial for us to push timeout events into the queue as you suggested- our code already does this, but from a slightly different place than you hooked. I believe the last bug that stopped us was in memfile.c (which hasn't been touched in a decade) with a memory corruption error. In our experience, Vim is only robust in so much as you don't step outside of the normal flow which makes me suspicious you will run into the same problems. I'm guessing that CursorHold and friends may also need work. At any rate, I'll have a look at your patch and try to get the Floobits python plugin to work on top of it. -Matt -- -- 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/groups/opt_out.
