Generally I would like to second that having async processing would be very useful.
> Vim does have kind of main loop waiting for arriving bytes on files or > sockets. That's what is used by the netbeans.txt API, correct? Current implementation of Netbeans API requires GUI: it uses callbacks under Motif and Gtk (see references to messageFromNetbeans in netbeans.c) and WM_NETBEANS message under Win32 gui. For console you can insert your processing into the main loop (I already did that once for MzScheme threads, see calls to mzvim_check_threads). Also I know that Xavier de Gaye implemented Netbeans for console Vim (http://pyclewn.sourceforge.net/vim-patches.html http://pyclewn.hg.sourceforge.net/hgweb/pyclewn/vim-patches/file/8eb5bd81ffaa/console-netbeans). -- Sergey Khorev http://sites.google.com/site/khorser Can anybody think of a good tagline I can steal?
-- You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php
