rneovim.git/src/nvim/event, branch v0.3.0

Merge #7679 'startup: treat stdin as text instead of commands'

2018-06-10T13:10:59+00:00

lint

2018-06-04T00:09:24+00:00

Bump up buffer capacity to 2GB

2018-05-23T20:07:27+00:00

socket.c: Ignore PVS/V547: False positive

2018-05-20T06:46:26+00:00

https://github.com/neovim/neovim/pull/8218#issuecomment-383412049

timer: make sure to free callback after the last timer due callback

2018-05-13T17:59:28+00:00

fixes #6974

Before this change, the partial could be freed before the last due
callback got invoked, which caused a use-after-free when the due
callback called the partial.

Merge #8218 'Fix errors reported by PVS'

2018-04-27T07:25:02+00:00

closes #4983

win: open child stdio handles in overlapped-mode (#8113)

2018-04-25T08:11:08+00:00

This will be used e.g. by the python client for native asyncio support

IO: shada should respect 'fsync' option

2018-04-21T10:50:28+00:00

shada_write_file() is called on exit (:quit and friends), this can be
very slow.

Note: AFAICT Vim (do_viminfo()) does not appear to fsync() viminfo.

event/process: Silence PVS/V547: assuming stream->num_bytes changes

2018-04-16T22:49:46+00:00

Not familiar with the code, but I assume that loop_poll_events can actually 
change stream->num_bytes, so condition is not always false.

job-control: children_kill_cb(): do not check elapsed time

2018-04-15T16:23:11+00:00

1. Don't check elapsed time in children_kill_cb(), it's already implied
   by the start-time of the timer itself.
2. Restart timer from children_kill_cb() for PTY jobs, to send SIGKILL
   after SIGTERM. There is an edge case where SIGKILL might follow
   SIGTERM too quickly, if jobstop() is called near the 2-second timer
   window.  But this edge case is not worth code complication.