aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* vim-patch:7.4.2049lonerover2017-01-19
| | | | | | | Problem: There is no way to get a list of the error lists. Solution: Add ":chistory" and ":lhistory". https://github.com/vim/vim/commit/f6acffbe83e622542d9fdf3066f51933e46e4954
* win: Define USE_FNAME_CASE (#5962)Justin M. Keyes2017-01-17
|
* DirChanged: set <amatch> (#5961)Justin M. Keyes2017-01-17
| | | | | Also: - test that DirChanged is not recursive - fix 'not trigger if :cd fails' test on Windows
* vim-patch:7.4.2062 (#5954)Shougo2017-01-16
| | | | | | Problem: Using dummy variable to compute struct member offset. Solution: Use offsetof(). https://github.com/vim/vim/commit/840268400dc8fda62a14f8a084e8b1ea46619454
* Merge #5928 'New event: DirChanged'Marco Hinz2017-01-16
|\
| * Rename yank_do_autocmd() to do_autocmd_textyankpost()Marco Hinz2017-01-13
| |
| * Document DirChangedMarco Hinz2017-01-13
| |
| * Move apply_autocmd_dirchanged() to vim_chdir()Marco Hinz2017-01-13
| |
| * Add autocmd/dirchanged_spec.luaMarco Hinz2017-01-13
| |
| * Trigger DirChanged on 'autochdir'Marco Hinz2017-01-13
| |
| * Don't expand filenames during autocmdMarco Hinz2017-01-13
| |
| * New event: DirChangedMarco Hinz2017-01-13
| |
* | vim-patch:7.4.2031 (#5955)Shougo2017-01-16
| | | | | | | | | | | | | | | | Problem: The list_lbr_utf8 test fails if ~/.vim/syntax/c.vim sets 'textwidth' to a non-zero value. (Oyvind A. Holm) Solution: Add a setup.vim file that sets 'runtimepath' and $HOME to a safe value. (partly by Christian Brabandt, closes vim/vim#912) https://github.com/vim/vim/commit/89b10421ca1aea55acbafac1df93be4e20210ceb
* | readfile(): Avoid file message when reading from stdin. #5956Michael Schupikov2017-01-16
| | | | | | | | Closes #5921
* | Merge #5918 'vim-patch: 7.4.2006, 7.4.2075, 7.4.2077, 7.4.2117, 7.4.2300, ↵Justin M. Keyes2017-01-16
|\ \ | | | | | | | | | 7.4.2313, 7.4.2314'.
| * | fix test failurelonerover2017-01-09
| | |
| * | vim-patch:7.4.2314lonerover2017-01-09
| | | | | | | | | | | | | | | | | | | | | Problem: No error when deleting an augroup while it's the current one. Solution: Disallow deleting an augroup when it's the current one. https://github.com/vim/vim/commit/de653f08805dde14424d417502a0480a6ad292f8
| * | vim-patch:7.4.2313lonerover2017-01-09
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Crash when deleting an augroup and listing an autocommand. (Dominique Pelle) Solution: Make sure deleted_augroup is valid. https://github.com/vim/vim/commit/b62cc36a600e2e1e5a1d1d484fef89898c847c4c
| * | vim-patch:7.4.2300lonerover2017-01-09
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Get warning for deleting autocommand group when the autocommand using the group is scheduled for deletion. (Pavol Juhas) Solution: Check for deleted autocommand. https://github.com/vim/vim/commit/5c80908ced601be6db7554a147cdb0f98ac8daa1
| * | vim-patch:7.4.2117lonerover2017-01-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Deleting an augroup that still has autocmds does not give a warning. The next defined augroup takes its place. Solution: Give a warning and prevent the index being used for another group name. https://github.com/vim/vim/commit/f2c4c391192cab6e923b1a418d4af09106fba25f
| * | vim-patch:7.4.2077rover2017-01-08
| | | | | | | | | | | | | | | | | | | | | Problem: Cannot update 'tabline' when a tab was closed. Solution: Add the TabClosed autocmd event. (partly by Felipe Morales) https://github.com/vim/vim/commit/12c11d553053f5a9eae9eb3c518279b12fa928c2
| * | vim-patch:7.4.2075rover2017-01-08
| | | | | | | | | | | | | | | | | | | | | Problem: No autocommand event to initialize a window or tab page. Solution: Add WinNew and TabNew events. (partly by Felipe Morales) https://github.com/vim/vim/commit/c917da4b3e8801a255dbefea8e4ed19c1c716dd8
| * | vim-patch:7.4.2006rover2017-01-08
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Crash when using tabnext in BufUnload autocmd. (Norio Takagi) Solution: First check that the current buffer is the right one. (Hirohito Higashi) https://github.com/vim/vim/commit/30445cb6e94698d212ba866ef3e4022ac625540a
* | | vim-patch:7.4.2099 (#5951)Shougo2017-01-15
| | | | | | | | | | | | | | | | | | | | | Problem: When a keymap is active only "(lang)" is displayed. (Ilya Dogolazky) Solution: Show the keymap name. (Dmitri Vereshchagin, closes vim/vim#933) https://github.com/vim/vim/commit/73ac0c4281a3606651604a3cbcc334bfb3859a87
* | | setpos(): Set lowercase mark in other buffers (#5753)Matthew Malcomson2017-01-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Also make setpos("'A", [999, 1, 1, 0]) fail, i.e. return -1 (assuming there is no buffer 999). Fixes #5713 Background: `:help setpos()` mentions an argument `"bufnum"` that determines the buffer a mark should be put in. This argument is respected for uppercase marks, but not for lowercase marks. This is reasonable (though I personally would like `setpos()` to be able to set marks in other buffers), but the help doesn't mention this anywhere. It's also strange that attempting to change buffers with `setpos('.', [bufnr('#'), 1, 1, 0])` alerts the user that having a different buffer is an error, while attempting to set a mark with `setpos("'d", [bufnr('#'), 1, 1, 0])` doesn't tell the user that the `"bufnum"` argument is an error.
* | | win: ci/AppVeyor: Rearrange PATH setup for python. (#5946)Justin M. Keyes2017-01-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This was an attempt to enable test/functional/provider/python3_spec.lua It actually *does* appear to work if we do this: mingw32-make functionaltest VERBOSE=1 PATH=C:\Python35;C:\Python27;%PATH% Note that %PATH% *already* has C:\Python35 at its start by then, so PATH=C:\Python35;C:\Python27;%PATH% is _redundant_. python3_spec.lua *does* find python3.exe in that case, and succeeds. But it causes weird failures in unrelated tests: [----------] Running tests from C:/projects/neovim/test/functional\core\job_partial_spec.lua [ RUN ] ...rojects/neovim/test/functional\core\job_partial_spec.lua @ 17: jobs with partials works correctly .\test\functional\helpers.lua:89: Vim(call):E903: Process for command "powershell" could not be spawned stack traceback: .\test\functional\helpers.lua:89: in function 'request' .\test\functional\helpers.lua:147: in function 'nvim_command' .\test\functional\helpers.lua:344: in function 'source' ...rojects/neovim/test/functional\core\job_partial_spec.lua:18: in function <...rojects/neovim/test/functional\core\job_partial_spec.lua:17> [ ERROR ] ...rojects/neovim/test/functional\core\job_partial_spec.lua @ 17: jobs with partials works correctly (0.00 ms) [ RUN ] C:/projects/neovim/test/functional\eval\execute_spec.lua @ 73: execute() does not capture shell-command output C:/projects/neovim/test/functional\eval\execute_spec.lua:74: Expected objects to be the same. Passed in: (string) ' :!echo "foo" Cannot execute cmd.exe shell returned -1 ' Expected: (string) ' :!echo "foo" ' stack traceback: C:/projects/neovim/test/functional\eval\execute_spec.lua:74: in function <C:/projects/neovim/test/functional\eval\execute_spec.lua:73> [ FAILED ] C:/projects/neovim/test/functional\eval\execute_spec.lua @ 73: execute() does not capture shell-command output (15.60 ms) [ RUN ] C:/projects/neovim/test/functional\ex_cmds\arg_spec.lua @ 11: :argument does not restart :terminal buffer C:/projects/neovim/test/functional\ex_cmds\arg_spec.lua:18: Expected objects to be the same. Passed in: (boolean) false Expected: (boolean) true stack traceback: C:/projects/neovim/test/functional\ex_cmds\arg_spec.lua:18: in function <C:/projects/neovim/test/functional\ex_cmds\arg_spec.lua:11> [ FAILED ] C:/projects/neovim/test/functional\ex_cmds\arg_spec.lua @ 11: :argument does not restart :terminal buffer (0.00 ms) [ RUN ] C:/projects/neovim/test/functional\ex_cmds\edit_spec.lua @ 11: :edit without arguments does not restart :terminal buffer C:/projects/neovim/test/functional\ex_cmds\edit_spec.lua:16: Expected objects to be the same. Passed in: (boolean) false Expected: (boolean) true stack traceback: C:/projects/neovim/test/functional\ex_cmds\edit_spec.lua:16: in function <C:/projects/neovim/test/functional\ex_cmds\edit_spec.lua:11> [ FAILED ] C:/projects/neovim/test/functional\ex_cmds\edit_spec.lua @ 11: :edit without arguments does not restart :terminal buffer (15.60 ms) [ RUN ] ...s/neovim/test/functional\eval\msgpack_functions_spec.lua @ 457: msgpackparse() function msgpackparse(systemlist(...)) does not segfault. #3135 .\test\functional\helpers.lua:89: Failed to evaluate expression stack traceback: .\test\functional\helpers.lua:89: in function 'eval' ...s/neovim/test/functional\eval\msgpack_functions_spec.lua:460: in function <...s/neovim/test/functional\eval\msgpack_functions_spec.lua:457> [ ERROR ] ...s/neovim/test/functional\eval\msgpack_functions_spec.lua @ 457: msgpackparse() function msgpackparse(systemlist(...)) does not segfault. #3135 (15.63 ms) [ FAILED ] 3 tests, listed below: [ FAILED ] C:/projects/neovim/test/functional\eval\execute_spec.lua @ 73: execute() does not capture shell-command output [ FAILED ] C:/projects/neovim/test/functional\ex_cmds\arg_spec.lua @ 11: :argument does not restart :terminal buffer [ FAILED ] C:/projects/neovim/test/functional\ex_cmds\edit_spec.lua @ 11: :edit without arguments does not restart :terminal buffer [ ERROR ] 2 errors, listed below: [ ERROR ] ...rojects/neovim/test/functional\core\job_partial_spec.lua @ 17: jobs with partials works correctly [ ERROR ] ...s/neovim/test/functional\eval\msgpack_functions_spec.lua @ 457: msgpackparse() function msgpackparse(systemlist(...)) does not segfault. #3135 64 SKIPPED TESTS 3 FAILED TESTS 2 ERRORS -- Output to stderr: The system cannot find the path specified. CMake Error at C:/projects/neovim/cmake/RunTests.cmake:46 (message): Running functional tests failed with error: 1.
* | | vim-patch:7.4.2065 (#5950)Shougo2017-01-15
| | | | | | | | | | | | | | | | | | Problem: Compiler warns for uninitialzed variable. (John Marriott) Solution: Set lnum to the right value. https://github.com/vim/vim/commit/69aa099641616268bfcde9dc3aa313c677846b12
* | | test: fix syntax errorJustin M. Keyes2017-01-15
| | | | | | | | | | | | Also re-arrange the test to match Vim upstream.
* | | vim-patch:7.4.2160 (#5952)Shougo2017-01-15
| | | | | | | | | | | | | | | | | | Problem: setmatches() mixes up values. (Nikolai Pavlov) Solution: Save the string instead of reusing a shared buffer. https://github.com/vim/vim/commit/7dc5e2e486fe0287601968e535902a41a39f65bb
* | | vim-patch:7.4.1968 (#5949)Shougo2017-01-15
| | | | | | | | | | | | | | | | | | Problem: Invalid memory access with "\<C-">. Solution: Do not recognize this as a special character. (Dominique Pelle) https://github.com/vim/vim/commit/1d90a5a5af84250e226f8a9121e771f7b72aa894
* | | vim-patch:7.4.1910 (#5948)Shougo2017-01-15
| | | | | | | | | | | | | | | | | | Problem: Tests using external command to delete directory. Solution: Use delete(). https://github.com/vim/vim/commit/abc70bbf363dbbe3f2bf714102f55648a512791e
* | | vim-patch:7.4.1851 (#5947)Shougo2017-01-15
| | | | | | | | | | | | | | | | | | Problem: test_syn_attr failes when using the GUI. (Dominique Pelle) Solution: Escape the font name properly. https://github.com/vim/vim/commit/180fc2d41812c49b60224a1ca89945a002a090f5
* | | Merge pull request #5940 from jamessan/masterJames McCoy2017-01-14
|\ \ \ | | | | | | | | job: Consume content from rbuffer before invoking the callback again
| * | | job: Consume content from rbuffer before invoking the callback againJames McCoy2017-01-14
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | While a job callback is active, it may be invoked again. Since the data handled by the first invocation of the callback hasn't been marked as consumed, the subsequent invocation will see the same data. Reported-by: Daniel Hahler Patch-by: oni-link Closes #5889
* | | Merge #5936 from blueyed/vim-8.0.0121Justin M. Keyes2017-01-14
|\ \ \ | | | | | | | | vim-patch:8.0.0121
| * | | LintingDaniel Hahler2017-01-13
| | | |
| * | | vim-patch:8.0.0121Daniel Hahler2017-01-13
| | |/ | |/| | | | | | | | | | | | | | | | Problem: Setting 'cursorline' changes the curswant column. (Daniel Hahler) Solution: Add the P_RWINONLY flag. (closes vim/vim#1297) https://github.com/vim/vim/commit/a2477fd3490c1166522631eee53c57d34321086a
* | | Merge pull request #5941 from blueyed/better-clint-noteJames McCoy2017-01-13
|\ \ \ | |/ / |/| | src/clint.py: improve "Ignoring" message
| * | src/clint.py: improve "Ignoring" messageDaniel Hahler2017-01-13
|/ / | | | | | | | | | | It was a bit confusing for me when seeing it myself the first time. [ci skip]
* | Merge #5933 from justinmk/dir-bufenterJustin M. Keyes2017-01-13
|\ \ | | | | | | open_buffer(): Raise `BufEnter` for directories.
| * | Windows: enable more testsJustin M. Keyes2017-01-13
| | |
| * | test: BufEnterJustin M. Keyes2017-01-13
| | |
| * | lintJustin M. Keyes2017-01-13
| | |
| * | open_buffer(): Do `BufEnter` for directories.Justin M. Keyes2017-01-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Abuse NOTDONE to give some nuance to the return value of readfile(), so that open_buffer() can distinguish between "failed, lol" and "failed because the path is a directory". Before this change, Vim *already* creates a new buffer when a directory is edited. So there is no reason it should not raise BufEnter, that was an implementation detail of ye olde readfile(). Most of the changes in this commit merely preserve the old semantics. The "implicit" change that we actually are interested in, is this line in `open_buffer()`, where `retval` being non-FAIL allows EVENT_BUFENTER to be applied: apply_autocmds_retval(EVENT_BUFENTER, NULL, NULL, FALSE, curbuf, &retval); References https://github.com/vim/vim/issues/1353
* | | Merge pull request #5935 from jamessan/dictwatcher-crashJames McCoy2017-01-12
|\ \ \ | |/ / |/| | eval: Remove dictwatcher from watchers queue before freeing it
| * | eval: Remove dictwatcher from watchers queue before freeing itJames McCoy2017-01-12
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes a use-after-free noticed by ASAN which would occur when a dictwatcher was still active on a dictionary when the dictionary was freed. fun! MakeWatch() let d = {'foo': 'bar'} call dictwatcheradd(d, 'foo', function('...')) endfun Patch-by: oni-link Closes #5930
* | Merge pull request #5932 from jamessan/icm-fixesJames McCoy2017-01-12
|\ \ | | | | | | inccommand: Ignore errors during preview and make cmd_can_preview stricter
| * | inccommand: Preview :sub commands only after the delimiter is presentJames McCoy2017-01-11
| | | | | | | | | | | | Closes #5888
| * | inccommand: Suppress error reporting when previewing commandsJames McCoy2017-01-11
|/ / | | | | | | Closes #5912
* | Windows: vim_getenv(): Find runtime relative to nvim. #3303 (#5929)Justin M. Keyes2017-01-11
| | | | | | | | | | | | | | | | | | | | | | | | In Windows we cannot rely on absolute install paths to point to the location of the runtime. Vim uses the path of the current binary as a possible location for the runtime folder. In Neovim the install location places the runtime folder in ../share/nvim/runtime. In Vim this logic is guarded by USE_EXE_NAME, which is defined for win32 and macOS. TODO: We may need to incorporate similar logic for macOS: https://github.com/vim/vim/blob/0cdb72aa38c4a0140c94d56bf8bc17cb30260ebf/src/misc1.c#L4287-L4308
generated by cgit (git 2.34.1) at 2025-06-01 18:45:43 +0000