After marc weber's [thread about improving
vim](https://groups.google.com/forum/#!topic/vim_use/IKha1xx6V8Y) I decided to
download the source code and try to fix what I believe to be a great deficiency
of vim: Impossibility to run vim commands from another thread.
Why is this feature so
On Tuesday, December 3, 2013 10:52:47 AM UTC-6, Thiago Arruda wrote:
After marc weber's [thread about improving
vim](https://groups.google.com/forum/#!topic/vim_use/IKha1xx6V8Y) I decided to
download the source code and try to fix what I believe to be a great
deficiency
of vim: Impossibility
On 12/3/2013 9:19 AM, Ben Fritz wrote:
On Tuesday, December 3, 2013 10:52:47 AM UTC-6, Thiago Arruda wrote:
[snip]
This use case--periodically polling an external process and then taking action on results--is a
perfect use case for the timed events patch a while back which was initially
On Tue, Dec 3, 2013 at 2:19 PM, Ben Fritz fritzophre...@gmail.com wrote:
This use case--periodically polling an external process and then taking
action on results--is a perfect use case for the timed events patch a while
back which was initially given the misnomer async:
Please join http://vim-wiki.mawercer.de/wiki/index.html !
Things get burried on the ml over time. Its fine to also post all info
here, but we also need a summary.
Its not only about threads, its also about ctlr-c on python/ruby
threads.
Its also about deciding on when a background thread is
