aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* | | | | Merge pull request #4880 from bfredl/zerotimerBjörn Linse2016-07-01
|\ \ \ \ \ | | | | | | | | | | | | make timers work correctly when timeout or repeat is zero
| * | | | | timers: make repeat=0 work one-shot (consistent with vim)Björn Linse2016-06-29
| | | | | |
| * | | | | timers: make timers work with zero timeoutBjörn Linse2016-06-29
| | | | | |
* | | | | | Add test for :dropKillTheMule2016-07-01
| | | | | | | | | | | | | | | | | | | | | | | | Cf. https://github.com/neovim/neovim/pull/4995
* | | | | | Fix regression of :drop introduced in 1a91000Michael Budde2016-07-01
| |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A single line was deleted from `ex_drop()` in 1a91000 when fixing clint warnings causing the `:drop` command to not work correctly if the buffer is not already open in a window. Fixes #4981
* | | | | rplugin: Manifest file name fallback (#4935)Shougo2016-06-30
| | | | |
* | | | | vim-patch:7.4.1136Patrick2016-06-30
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Wrong argument to assert_exception() causes a crash. (reported by Coverity) Solution: Check for NULL pointer. Add a test. https://github.com/vim/vim/commit/da5dcd936656f524dd0ae7cb2685245f07f5720f
* | | | Merge #4984 'Trigger TabNewEntered with <CTRL-W>T'Justin M. Keyes2016-06-28
|\ \ \ \ | | | | | | | | | | | | | | | Closes #4979
| * | | | [RFC] Fix #4979: Trigger TabNewEntered also with <CTRL-W>TDimitri Merejkowsky2016-06-28
| | | | | | | | | | | | | | | | | | | | Original patch by @fmoralesc
* | | | | doc: remove obsolete reference (#4978)KillTheMule2016-06-27
|/ / / /
* | | | Update version.c (#4974)KillTheMule2016-06-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Only update some entries that are already in `version.c`. Mercilessly stolen from https://github.com/neovim/neovim/pull/4634. At least one possible contributor got confused by it not being as-up-do-date-as-it-coul-be(tm). We shouldn't have that. 1005, 1010: :smile 1039: small Build 1058, 1073, 1079, 1097: alloc 1555, 1556, 1573: Makefile 1560, 1579: channel
* | | | Merge #4646 from oni-link/fix.issue.4569.3Justin M. Keyes2016-06-26
|\ \ \ \ | |/ / / |/| | | Fix for missing output (#4569, ...)
| * | | fixup2: process.c: Prevent data loss for process output streamsoni-link2016-05-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The only data loss should be, if a process forked a child that keeps sending data after the parent terminated. While not in teardown mode we could keep reading child data, but then `:!cmd` would block after `cmd` exited. In teardown mode we want to exit nvim so we cannot keep reading child data.
| * | | fixup: process.c: Prevent data loss for process output streamsoni-link2016-05-15
| | | | | | | | | | | | | | | | | | | | | | | | * Get system buffer size for upper data limit. Otherwise data loss if this buffer is too big. * Test whether teardown needs special handling.
| * | | shell.c: Fix missing outputoni-link2016-05-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The whole stream buffer is now put on screen at once instead of only data up to the last newline. This has some advantages: * RBuffer cannot wrap around, so we never forget to output second half of the buffer. * Stream data is not delayed anymore, because we don't have to wait for a newline. This works by remembering the last used screen column.
| * | | process.c: Prevent data loss for process output streamsoni-link2016-05-15
| | | | | | | | | | | | | | | | | | | | For a terminating process, it's output streams could be closed, before all data is read.
* | | | Merge #4969 from ZyX-I/update-unicodeJustin M. Keyes2016-06-26
|\ \ \ \ | | | | | | | | | | Update unicode files
| * | | | version: State that 1960 was includedZyX2016-06-26
| | | | |
| * | | | Update unicode filesZyX2016-06-26
|/ / / /
* | | | ci: Remove MSAN build until it is fixed. (#4966)Justin M. Keyes2016-06-25
| | | | | | | | | | | | Closes #4956
* | | | Merge #4965 from justinmk/fixup4453Justin M. Keyes2016-06-25
|\ \ \ \ | | | | | | | | | | ex_cmds2.c: lint
| * | | | ex_cmds2.c: cleanupJustin M. Keyes2016-06-25
| | | | |
| * | | | ex_cmds2.c:style: Silence all clint warningsJ Phani Mahesh2016-06-24
| | | | |
* | | | | Merge #4607 from ZyX-I/luaviml'/lua'/encode_vim_to_objectJustin M. Keyes2016-06-25
|\ \ \ \ \ | | | | | | | | | | | | Remove recursion from various serializers/converters
| * | | | | unittests/*/helpers: Fix testlint errorsZyX2016-06-24
| | | | | |
| * | | | | option: Make all pointers in set_string_option constantZyX2016-06-24
| | | | | |
| * | | | | *: Fix linter errorsZyX2016-06-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Also adds one exception to linter rules: typedef struct { kvec_t(Object) stack; } EncodedData; is completely valid (from the style guide point of view) code.
| * | | | | kvec: Do not bother with making capacity a power of 2ZyX2016-06-24
| | | | | | | | | | | | | | | | | | This avoids gcc warnings about undefined behaviour.
| * | | | | msgpack_rpc: Fix crash in log_server_msgZyX2016-06-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It appears that used msgpack library is not able to parse back message created by msgpack_rpc_from_object() if nesting level is too high, so log_server_msg now cares about msgpack_unpack_next() return value. Also error message from server_notifications_spec.lua is not readable if something is wrong (though at least now it does not crash when parsing deeply nested structures). log_server_msg() in the test reports [msgpack-rpc] nvim -> client(1) [error] "parse error"
| * | | | | fixup! unittests: Add tests for vim_to_object functionZyX2016-06-24
| | | | | |
| * | | | | option: Handle NULL string in set_option_valueZyX2016-06-24
| | | | | |
| * | | | | eval: Also make clear_tv non-recursiveZyX2016-06-24
| | | | | |
| * | | | | kvec,typval_encode: Add new vector: the one with preallocated arrayZyX2016-06-24
| | | | | |
| * | | | | msgpack_rpc: Also make msgpack_from_*/msgpack_to_* functions not recurZyX2016-06-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This removes some stack overflows in new test regarding deeply nested variables. Now in place of crashing vim_to_object/msgpack_rpc_from_object/etc it crashes clear_tv with stack overflow.
| * | | | | unittests: Add tests for vim_to_object functionZyX2016-06-24
| | | | | |
| * | | | | api/helpers: Use typval_encode.h for vim_to_objectZyX2016-06-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This ought to prevent stack overflow, but I do not see this actually working: *lua* code crashes with stack overflow when trying to deserialize msgpack from Neovim, Neovim is fine even if nesting level is increased 100x (though test becomes very slow); not sure how recursive function may survive this. So it looks like there are currently only two positive effects: 1. NULL lists are returned as empty (#4596). 2. Functional tests are slightly more fast. Very slightly. Checked for Release build for test/functional/eval tests because benchmarking of debug mode is not very useful.
* | | | | | Merge pull request #4962 from neovim/ZyX-I-patch-1Nikolai Aleksandrovich Pavlov2016-06-25
|\ \ \ \ \ \ | |/ / / / / |/| | | | | | | | | | | | | | | | | doc: Add missing /site/ path component to &runtimepath description Fixes #4957
| * | | | | doc: Add missing /site/ path component to &runtimepath descriptionNikolai Aleksandrovich Pavlov2016-06-25
|/ / / / /
* | | | | Merge #4865 from ZyX-I/file-buffered-readJustin M. Keyes2016-06-24
|\ \ \ \ \ | |/ / / / |/| | | | Use buffered reading/writing for ShaDa files
| * | | | unittests: Fix testlint errorsZyX2016-06-24
| | | | |
| * | | | os/fileio: Use readv oftenZyX2016-06-24
| | | | |
| * | | | unittests: Fix kFileNoSymlink test on FreeBSDZyX2016-06-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Actual value on FreeBSD is -31, UV_EMLINK was obtained from /usr/include/asm-generic/errno-base.h (there EMLINK is defined as 31 there). This may actually be something else, but I do not think so as “Too many links” description also fits in. [Man page][1] agrees with me, search for `[EMLINK]` ([linux man page][2] also specifies ELOOP explicitly in a similar section). [1]: https://www.freebsd.org/cgi/man.cgi?query=open&sektion=2 [2]: http://man7.org/linux/man-pages/man3/open.3p.html
| * | | | *: Satisfy linter (newest type casts rule)ZyX2016-06-24
| | | | |
| * | | | unittests: Fix bug somewhere that makes file_read tests SEGVZyX2016-06-24
| | | | |
| * | | | file: Move src/nvim/file.* to src/nvim/os/fileio.*ZyX2016-06-24
| | | | |
| * | | | unittests: Add tests for file.cZyX2016-06-24
| | | | | | | | | | | | | | | | | | | | Also fixes some errors found.
| * | | | unittests: Add os_write testZyX2016-06-23
| | | | | | | | | | | | | | | New os/fs.c functions are now all tested.
| * | | | shada: Do not forget to close ShaDa readerZyX2016-06-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously there was file descriptor leak, not detected by sanitizers. Now it is file descriptor leak with a small memory leak which is detected by ASAN what fails one of the tests (actually, “ShaDa support code leaves .tmp.z in-place when there is error in original ShaDa and it has .tmp.a … .tmp.x”, but error is reported at the next test because leaks are not detected until Neovim exit and Neovim exit happens when clear()/reset() is called which happens in before_each only).
| * | | | file: Use own constants, do not rely on fcntl.hZyX2016-06-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | One of the reasons is that O_RDONLY is zero, which makes checking whether file is opened read- or write-only harder. It is not guaranteed that on other system O_WRONLY will not be zero (e.g. because file can only be opened in read-write mode).
| * | | | unittests: Add os_close, os_read and os_readv testsZyX2016-06-23
| | | | |
generated by cgit (git 2.34.1) at 2025-05-21 01:07:33 +0000