Re: Pluggable eventloop, was Re: Plans for Vim 7.4

2013-05-15 Fir de Conversatie Charles Campbell
Jan Pobrislo wrote: Glib inside gvim, since gtk+ uses glib internally. More precisely glib is that part of gtk+ that does not deal with gui, so there's no gvim without glib. (Unless there's implementation of gvim not based on gtk which I'm unaware of). A gvim can be compiled using motif under L

Re: Pluggable eventloop, was Re: Plans for Vim 7.4

2013-05-12 Fir de Conversatie James McCoy
On Mon, May 13, 2013 at 02:40:20AM +0200, Tony Mechelynck wrote: > On 12/05/13 21:28, Jan Pobrislo wrote: > >Glib inside gvim, since gtk+ uses glib internally. More precisely glib is > >that part of gtk+ that does not deal with gui, so there's no gvim without > >glib. (Unless there's implementation

Re: Pluggable eventloop, was Re: Plans for Vim 7.4

2013-05-12 Fir de Conversatie Tony Mechelynck
On 12/05/13 21:28, Jan Pobrislo wrote: On Sat, 11 May 2013 04:45:50 +0200, Tony Mechelynck wrote: 1) Add VimL api to hook into the eventloops. The unix poll() eventloop seems simple enough to start with. Is it guaranteed to be available? Think MS-Windows or IBM-mainframe. Nope, neith

Re: Pluggable eventloop, was Re: Plans for Vim 7.4

2013-05-12 Fir de Conversatie Jan Pobrislo
On Sat, 11 May 2013 15:44:10 +0200, Xavier de Gaye wrote: > An alternative would be to allow any python thread to call the vim-python > interface through message passing. That indeed is also possible, but for it to work properly you need to create interface for waking the main thread from iowait,

Re: Pluggable eventloop, was Re: Plans for Vim 7.4

2013-05-12 Fir de Conversatie Jan Pobrislo
On Sat, 11 May 2013 04:45:50 +0200, Tony Mechelynck wrote: > > 1) Add VimL api to hook into the eventloops. The unix poll() eventloop seems > > simple enough to start with. > > Is it guaranteed to be available? Think MS-Windows or IBM-mainframe. > Nope, neither are some other optional feat

Re: Pluggable eventloop, was Re: Plans for Vim 7.4

2013-05-11 Fir de Conversatie tyru
Hi vimmers! On Sat, May 11, 2013 at 11:45 AM, Tony Mechelynck wrote: > On 10/05/13 10:54, Jan Pobrislo wrote: >> >> On Thu, 09 May 2013 05:51:48 +0200, Bram Moolenaar >> wrote: >>> >>> The top five of the voting list: >>> http://www.vim.org/sponsor/vote_results.php >>> >>> 1. add IDE features >>

Re: Pluggable eventloop, was Re: Plans for Vim 7.4

2013-05-11 Fir de Conversatie Xavier de Gaye
On Fri, May 10, 2013 at 10:54 AM, Jan Pobrislo wrote: > > I'm quite curious what is meant by IDE-like features. From my experience > most of that is covered by plugins already, except for one significant > roadblock: inability to communicate with external processes without blocking > whole UI. Ther

Re: Pluggable eventloop, was Re: Plans for Vim 7.4

2013-05-10 Fir de Conversatie Tony Mechelynck
On 10/05/13 10:54, Jan Pobrislo wrote: On Thu, 09 May 2013 05:51:48 +0200, Bram Moolenaar wrote: The top five of the voting list: http://www.vim.org/sponsor/vote_results.php 1. add IDE features 2. add integration with Python instead of inventing more Vim script 3. fix all problems, big and sma

Pluggable eventloop, was Re: Plans for Vim 7.4

2013-05-10 Fir de Conversatie Jan Pobrislo
On Thu, 09 May 2013 05:51:48 +0200, Bram Moolenaar wrote: > The top five of the voting list: > http://www.vim.org/sponsor/vote_results.php > > 1. add IDE features > 2. add integration with Python instead of inventing more Vim script > 3. fix all problems, big and small; make Vim more robust > 4.