aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Merge #8044 'build: improve Lua module checks'Justin M. Keyes2018-02-22
|\
| * cmake/LuaHelpers.cmake: check_lua_module: use 'lua -l'Daniel Hahler2018-02-22
| | | | | | | | | | | | It only shortens the traceback a bit for when a module is not found though, only removing the "(command line):1: in main chunk" (with lua5.2).
| * cmake/LuaHelpers.cmake: check_lua_module: display errorsDaniel Hahler2018-02-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This helps to figure out what the problem is, e.g. in my case I have lua51-mpack installed to be used with luajit, but it is broken (missing libmpack). With this patch you get: -- Checking Lua interpreter /usr/bin/luajit /usr/bin/luajit: error loading module 'mpack' from file '/usr/lib/lua/5.1/mpack.so': libmpack.so.0: cannot open shared object file: No such file or directory stack traceback: [C]: at 0x55fcf0166fb0 [C]: in function 'require' (command line):1: in main chunk [C]: at 0x55fcf01188a0 -- [/usr/bin/luajit] The 'mpack' lua package is required for building Neovim -- Checking Lua interpreter /usr/bin/lua5.1 /usr/bin/lua5.1: error loading module 'mpack' from file '/usr/lib/lua/5.1/mpack.so': libmpack.so.0: cannot open shared object file: No such file or directory stack traceback: [C]: ? [C]: in function 'require' (command line):1: in main chunk [C]: ? -- [/usr/bin/lua5.1] The 'mpack' lua package is required for building Neovim -- Checking Lua interpreter /usr/bin/lua5.2 /usr/bin/lua5.2: (command line):1: module 'mpack' not found: no field package.preload['mpack'] no file '/usr/share/lua/5.2/mpack.lua' no file '/usr/share/lua/5.2/mpack/init.lua' no file '/usr/lib/lua/5.2/mpack.lua' no file '/usr/lib/lua/5.2/mpack/init.lua' no file './mpack.lua' no file '/usr/lib/lua/5.2/mpack.so' no file '/usr/lib/lua/5.2/loadall.so' no file './mpack.so' stack traceback: [C]: in function 'require' (command line):1: in main chunk [C]: in ? -- [/usr/bin/lua5.2] The 'mpack' lua package is required for building Neovim -- Checking Lua interpreter /usr/bin/lua /usr/bin/lua: (command line):1: module 'mpack' not found: no field package.preload['mpack'] no file '/usr/share/lua/5.3/mpack.lua' no file '/usr/share/lua/5.3/mpack/init.lua' no file '/usr/lib/lua/5.3/mpack.lua' no file '/usr/lib/lua/5.3/mpack/init.lua' no file './mpack.lua' no file './mpack/init.lua' no file '/usr/lib/lua/5.3/mpack.so' no file '/usr/lib/lua/5.3/loadall.so' no file './mpack.so' stack traceback: [C]: in function 'require' (command line):1: in main chunk [C]: in ? -- [/usr/bin/lua] The 'mpack' lua package is required for building Neovim CMake Error at CMakeLists.txt:459 (message): A suitable Lua interpreter was not found. While this makes it more verbose for the expected error case ("module 'mpack' not found"), the behavior before this patch hides too much. This is the old output: -- Checking Lua interpreter /usr/bin/luajit -- [/usr/bin/luajit] The 'mpack' lua package is required for building Neovim -- Checking Lua interpreter /usr/bin/lua5.1 -- [/usr/bin/lua5.1] The 'mpack' lua package is required for building Neovim -- Checking Lua interpreter /usr/bin/lua5.2 -- [/usr/bin/lua5.2] The 'mpack' lua package is required for building Neovim -- Checking Lua interpreter /usr/bin/lua -- [/usr/bin/lua] The 'mpack' lua package is required for building Neovim CMake Error at CMakeLists.txt:459 (message): A suitable Lua interpreter was not found. This is for when the whole configuration runs (i.e. after `make distclean`), afterwards only one Lua interpreter gets checked only.
* | health.vim: minor cleanup (#8046)Daniel Hahler2018-02-22
| |
* | health/provider: check Python also with loaded_var (#8047)Daniel Hahler2018-02-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `g:loaded_python3_provider` gets set when the autoload file is sourced, but this might error out, e.g. with deoplete: [deoplete] Failed to load python3 host. You can try to see what happened by starting nvim with $NVIM_PYTHON_LOG_FILE set and opening the generated log file. Also, the host stderr is available in messages. [deoplete] function remote#define#FunctionBootstrap[1]..remote#host#Require[10]..provider#pythonx#Require[13]..provider#Poll, line 14 [deoplete] deoplete requires Python3 support("+python3"). [deoplete] deoplete failed to load. Try the :UpdateRemotePlugins command and restart Neovim. See also :checkhealth. It refers to `:checkhealth` from there explicitly, which would then (without this patch) say that Python 3 is disabled. This patch changes the reported info to include that it might have been disabled due to some error, and keeps on going.
* | checkhealth: python: do not report pythonx_errs twice (#8045)Daniel Hahler2018-02-22
| | | | | | They get reported unconditionally as errors below.
* | runtime/autoload/health/*.vim: fix vint warning (#8048)Daniel Hahler2018-02-22
| |
* | vim-patch:8.0.0225: put in Visual block mode terminates early (#8040)UTkarsh Maheshwari2018-02-21
| | | | | | | | | | | | | | Problem: When a block is visually selected and put is used on the end of the selection only one line is changed. Solution: Check for the end properly. (Christian Brabandt, neovim issue 5781) https://github.com/vim/vim/commit/9957a10d0f0c34d8083af6ed66e198e4796038e0
* | Merge pull request #8039 from bfredl/deadscreenBjörn Linse2018-02-21
|\ \ | |/ |/| remove dead code in screen.c for terminals without scroll regions
| * screen: win_del_lines/win_ins_lines cleanupBjörn Linse2018-02-21
| |
| * screen: remove dead code emulating terminals without scroll regionsBjörn Linse2018-02-21
|/ | | | This logic is now in tui/tui.c
* vim-patch:8.0.0222: blockwise put on multi-byte char (#8030)KunMing Xie2018-02-20
| | | | | | | | | Note: code change was covered by c2a18216114bae75b6d6a2c7f1a68db04578abce Problem: When a multi-byte character ends in a zero byte, putting blockwise text puts it before the character instead of after it. Solution: Use int instead of char for the character under the cursor. (Luchr, closes vim/vim#1403) Add a test. https://github.com/vim/vim/commit/c81299684b2b9045e56525d3da3f45e8440fbf0d
* Merge pull request #8031 from bfredl/gotintstatusBjörn Linse2018-02-20
|\ | | | | jobwait: return -2 on interrupt even with timeout
| * jobwait: return -2 on interrupt also with timeoutBjörn Linse2018-02-20
| |
* | Merge pull request #8019 from jamessan/invalid-provider-stderrJames McCoy2018-02-19
|\ \ | | | | | | Improve error handling and reduce duplication of providers' #Require()
| * | Add provider#Poll() to handle starting and polling the providerJames McCoy2018-02-16
| | |
| * | provider: Safely access job.stderr in #RequireJames McCoy2018-02-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If `jobstart()` fails, then the subsequent `rpcrequest()` will throw due to an invalid channel id. This causes `job.stderr` not to exist, so we throw another exception when trying to dump the job's stderr. Error detected while processing function remote#define#AutocmdBootstrap[1]..remote#host#Require[10]..provider#pythonx#Require: line 22: E716: Key not present in Dictionary: stderr This obfuscates the actual problem.
| * | provider: ruby: Use stderr_buffered to collect stderrJames McCoy2018-02-16
| |/
* | Merge #7412 'win: enable more tests'Justin M. Keyes2018-02-20
|\ \
| * | Resolve issues mentioned in PR reviewJan Edmund Lazo2018-02-19
| | |
| * | test: win: emulate yes with for loopJan Edmund Lazo2018-02-19
| | |
| * | test: win: enable ui/wildmode_spec.luaJan Edmund Lazo2018-02-19
| | |
| * | test: win: enable termclose_spec.luaJan Edmund Lazo2018-02-19
| | |
| * | test: enable ex_cmds/cd_spec.lua on WindowsJan Edmund Lazo2018-02-19
| | |
| * | test: enable legacy/fixeol_spec in WindowsJan Edmund Lazo2018-02-19
| | | | | | | | | | | | Try nvim's delete() for cross-platform file remove in Windows
| * | test: enable ex_cmds/write_spec.lua in WindowsJan Edmund Lazo2018-02-19
| | |
| * | win: enable legacy test 051Jan Edmund Lazo2018-02-19
| | |
| * | win: enable legacy test 059Jan Edmund Lazo2018-02-19
| | |
| * | win: enable legacy test 107Jan Edmund Lazo2018-02-19
| | |
| * | win: enable legacy test 093Jan Edmund Lazo2018-02-19
| | |
| * | win: enable legacy/arglist_spec.luaJan Edmund Lazo2018-02-19
| | |
| * | win: enable legacy test 30Jan Edmund Lazo2018-02-19
| | |
| * | win: enable legacy/getcwd_spec.luaJan Edmund Lazo2018-02-19
| | |
| * | win: enable legacy/wordcount_spec.luaJan Edmund Lazo2018-02-19
| | |
| * | win: enable legacy/packadd_spec.luaJan Edmund Lazo2018-02-19
| | |
| * | win: enable legacy test 011Jan Edmund Lazo2018-02-19
| | |
| * | win: enable legacy/delete_spec.luaJan Edmund Lazo2018-02-19
| | |
| * | win: enable legacy test 097Jan Edmund Lazo2018-02-19
| | |
| * | win: enable legacy test 025Jan Edmund Lazo2018-02-19
| | |
| * | win: enable job tests that use jobstart onlyJan Edmund Lazo2018-02-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - echo "" does not hang in powershell - cmd.exe's echo command does not hang. - job tests default to powershell (WHY?) - wait 5 seconds for powershell to create an empty file - powershell is slow - cannot reliably validate the id returned by jobstart via jobpid, jobstop - if using cmd.exe, waiting for a second should be enough - remaining job tests are unreliable in Windows because any build can pass/fail for same conditions without changes, especially if the error is in stderr
* | | vim-patch:8.0.0214 (#8010)KunMing Xie2018-02-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | vim-patch:8.0.0214: leaking memory when syntax cluster id is unknown Problem: Leaking memory when syntax cluster id is unknown. (Coverity) Solution: Free the memory. https://github.com/vim/vim/commit/d7a96151e0c86e8d4f9162c919cf3ff400a893b6
* | | build/gcc: disable -Warray-bounds entirely #7923Justin M. Keyes2018-02-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We need to disable -Warray-bounds locally for kbtree.h, but we can't because _Pragma("GCC diagnostic pop") is broken in GCC 5.x+. So this commit disables -Warray-bounds entirely (for GCC only). GCC bug: "_Pragma diagnostic 'ignored' in macro with strict-overflow not suppressing warning fully with -Werror" https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66099 ref https://github.com/neovim/neovim/pull/7083#issuecomment-326323599 closes #7921
* | | build: remove contents of build/runtime/doc/* surgically (#8024)Justin M. Keyes2018-02-19
|/ / | | | | | | | | | | | | | | | | | | | | | | Only remove the directory contents. If the directory itself is removed, then `sudo make install` creates a root-owned …/doc/ directory. That breaks the next non-root build. This was an accident of 0b1904d835a2. Note: the following does not work, because it misses renamed help files (which would no longer be in the build-tree definition) COMMAND ${CMAKE_COMMAND} -E remove ${BUILDDOCFILES} ${GENERATED_HELP_TAGS}
* | vim-patch:8.0.1493: completion items cannot be annotated (#8003)Shougo2018-02-18
| | | | | | | | | | | | | | Problem: Completion items cannot be annotated. Solution: Add a "user_data" entry to the completion item. (Ben Jackson, coses vim/vim#2608, closes vim/vim#2508) https://github.com/vim/vim/commit/9b56a57cdae31f7a2c85d440392bf63d3253a158
* | runtime/doc: modeline is mandatory in help docsJustin M. Keyes2018-02-18
| | | | | | | | see Vim 8.0.0650 e9134421ab8f
* | vim-patch:8.0.0212: buffer for key name may be too small (#8009)KunMing Xie2018-02-18
| | | | | | | | | | | | | | | | | | Problem: The buffer used to store a key name theoreticaly could be too small. (Coverity) Solution: Count all possible modifier characters. Add a check for the length just in case. https://github.com/vim/vim/commit/423977d3cebac2be1158b1d11da60fe96db4b750
* | Merge #8018 from justinmk/test-eq_anyJustin M. Keyes2018-02-18
|\ \
| * | test/util: remove eq_any()Justin M. Keyes2018-02-18
| | | | | | | | | | | | | | | | | | It was added in the parent commit, but ended up not being used. And I can't think of a case where it will be used: instead we would probably want to generalize expect_msg_seq() if necessary.
| * | test/util: expect_msg_seq()Justin M. Keyes2018-02-18
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | job_spec.lua on AppVeyor (Windows) often fails like this: FAILED ] C:/projects/neovim/test/functional\core\job_spec.lua @ 72: jobs changes to given `cwd` directory C:/projects/neovim/test/functional\core\job_spec.lua:81: Expected objects to be the same. Passed in: (table) { [1] = 'notification' [2] = 'stdout' *[3] = { [1] = 0 *[2] = { [1] = 'C:\projects\neovim\Xtest-tmpdir\nvimmSjq1S\0' } } } Expected: (table) { [1] = 'notification' [2] = 'stdout' *[3] = { [1] = 0 *[2] = { [1] = 'C:\projects\neovim\Xtest-tmpdir\nvimmSjq1S\0' *[2] = '' } } } stack traceback: Message chunking is non-deterministic, so we need to try different variants.
* | Merge pull request #8011 from nimitbhardwaj/vim-8.0.0649Björn Linse2018-02-17
|\ \ | | | | | | vim-patch:8.0.0649 and vim-patch:8.0.0650