aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* provider: let providers decide their statusRui Abreu Ferreira2019-08-04
| | | | | | | | | | | | | | | | | | | | | | | | | | Instead of deciding provider status in eval_has_provider, move the decision to the provider Vim scripts. Previously, provider loading worked as follows: 1. eval_has_provider() verified provider availability by searching for the provider#providername#Call function and cached this verificaion as a static variable for some providers 2. providers short-circuited on loading to prevent the definition of the Call function (with the exception of the node provider that did not) This commit changes the expected interface between nvim and its providers to facilitate provider reloading, by splitting the verification of the provider from the availability of the Call function. eval_has_provider() now checks for a provider#providername#enabled variable. It is up to the provider script to set this to 0 or 1 accordingly. eval_call_provider() remains unchanged. All providers hosting a Call function were updated to respect this. The clipboard provider now has a Reload function to reload the provider.
* vim-patch:8.1.1237: error for using "compl", reserved word in C++Jan Edmund Lazo2019-08-03
| | | | | | Problem: Error for using "compl", reserved word in C++. Solution: Rename to "complp". (suggestion by Ken Takata) https://github.com/vim/vim/commit/52111f82318dfbeb6a0b06230c0609abff509250
* vim-patch:8.1.1796: :argdo is not testedJan Edmund Lazo2019-08-03
| | | | | | Problem: :argdo is not tested Solution: Add a test. https://github.com/vim/vim/commit/72e1b39111389001a20fbe8aa344ce2fe0a7e1a4
* vim-patch:8.1.1775: error message may be empty in filetype testJan Edmund Lazo2019-08-02
| | | | | | Problem: Error message may be empty in filetype test. Solution: Use v:exception instead. (Daniel Hahler, closs vim/vim#4744) https://github.com/vim/vim/commit/eee9f65b2a213e9031f172d9d3b22adad6cb985d
* vim-patch:8.1.1762: some filetype rules are in the wrong placeJan Edmund Lazo2019-08-02
| | | | | | Problem: Some filetype rules are in the wrong place. Solution: Move to the right place. Add a few more tests. https://github.com/vim/vim/commit/c273405188cc2f19e949089cda1f92bd81610dac
* vim-patch:8.1.1761: filetype "vuejs" causes problems for some usersJan Edmund Lazo2019-08-02
| | | | | | Problem: Filetype "vuejs" causes problems for some users. Solution: Rename to "vue". https://github.com/vim/vim/commit/4248111497ab78f45d3d48576740949778a1e76b
* vim-patch:8.1.1187: cannot recognize PipfileJan Edmund Lazo2019-08-02
| | | | | | Problem: Cannot recognize Pipfile. Solution: Use existing filetypes. (Charles Ross, closes vim/vim#4280) https://github.com/vim/vim/commit/3a4c53ba51c01b8fea68972453a71c55cf32edbe
* terminfo_start: use unibi_from_term, skip without TERM (#10670)Daniel Hahler2019-08-02
| | | | | This is clearer/more explicit and avoids potential mismatch between what unibilium thinks vs what Nvim thinks. For reference: https://github.com/mauke/unibilium/blob/e3b16d6219ca1cb92d98b1d9cc416b49a3ac468e/uniutil.c#L203-L211
* Merge #10664 from janlazo/vim-8.1.1780Justin M. Keyes2019-08-02
|\ | | | | vim-patch:8.1.{1374,1780}
| * fileio: port hotfix from patch 8.1.1379Jan Edmund Lazo2019-08-01
| | | | | | | | | | | | Patch 8.1.1379 includes a change to a test, added in Patch 8.1.0815. Patch 8.1.0815 includes runtime doc changes to Blob. Neovim does not support Blobs yet.
| * vim-patch:8.1.1374: check for file changed triggers too oftenJan Edmund Lazo2019-08-01
| | | | | | | | | | | | Problem: Check for file changed triggers too often. Solution: Don't use "b_p_ar" when it is negative. https://github.com/vim/vim/commit/c97582b0296cb6f63f3c2e5a0eb954f5920a8e42
| * lintJan Edmund Lazo2019-08-01
| |
| * vim-patch:8.1.1780: warning for file no longer available is repeatedJan Edmund Lazo2019-07-31
| | | | | | | | | | | | | | Problem: Warning for file no longer available is repeated every time Vim is focused. (Brian Armstrong) Solution: Only give the message once. (closes vim/vim#4748) https://github.com/vim/vim/commit/674e2bde6e7b0c468f304713aa8f97a45e1fcc89
* | stream: log unwritten bytes, if any #10663Justin M. Keyes2019-08-01
| |
* | process_stop: uv: do not close stdin first/explicitly #10584Daniel Hahler2019-08-01
|/ | | | | | | | | | - process_stop: do not close stdin explicitly. The "close stdin" step was from aa9cb48, before we fixed/reworked the SIGTERM timing logic. So it's probably outdated / no longer needed. - win: jobstop: exit_code 15 GetExitCodeProcess appears to return the used signal. https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-getexitcodeprocess ref #10573
* Merge #10654 from ngortheone/clang/npd_helptags_oneJustin M. Keyes2019-07-31
|\ | | | | clang/"null pointer dereference": ex_cmds.c
| * lint: helptags_oneIhor Antonov2019-07-30
| |
| * clang/"null pointer dereference": ex_cmds.cIhor Antonov2019-07-29
| |
* | vim-patch:8.1.0572: stopping a job does not work properly on OpenBSDDaniel Hahler2019-07-30
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Stopping a job does not work properly on OpenBSD. Solution: Do not use getpgid() to check the process group of the job processs ID, always pass the negative process ID to kill(). (George Koehler, closes vim/vim#3656) https://github.com/vim/vim/commit/76ab4fd61901090e6af3451ca6c5ca0fc370571f Ref: https://github.com/neovim/neovim/issues/9704 Ref: https://github.com/neovim/neovim/issues/10182#issuecomment-514450069 Closes https://github.com/neovim/neovim/pull/10660
* | tests: runnvim.vim: do not call jobstop() (#10659)Daniel Hahler2019-07-30
| | | | | | | | | | | | | | | | | | | | | | It should be done for timeouts only (-1, not != -1), but the job is stopped via `:bwipeout!` already also in that case. Fixes E900 with timing out tests: "test_xxx.tlog" "test_xxx.tlog" [New] 183L, 13375C written Error detected while processing function Main: line 37: E900: Invalid channel id================================================================================
* | gen_eval.lua: use correct name in usageDaniel Hahler2019-07-30
| |
* | tests: use Vim's version for patch 8.1.0005Daniel Hahler2019-07-30
| | | | | | | | | | Not sure what happened in daca22f5b / #8821, but Vim used assert_match / no expand in vim/vim@d19b23415 (8.1.0005) already.
* | py: flake8 fixesDaniel Hahler2019-07-29
|/
* Merge #10645 from janlazo/vim-8.1.0999Justin M. Keyes2019-07-29
|\ | | | | vim-patch:8.1.{1005,1041,1049,1052,1053,1086,1394}
| * vim-patch:8.1.1086: too many curly bracesJan Edmund Lazo2019-07-28
| | | | | | | | | | | | | | | | | | | | Problem: Too many curly braces. Solution: Remove curly braces where they are not needed. (Hirohito Higashi, closes vim/vim#3982) https://github.com/vim/vim/commit/abab0b0fdd6535969447b03a4fffc1947918cf6c Neovim code style requires the opposite. Add curly braces to minimize lint errors when applying Vim patches.
| * buffer: add attributes to pure functionsJan Edmund Lazo2019-07-28
| |
| * vim-patch:8.1.1049: when user tries to exit with CTRL-C message is confusingJan Edmund Lazo2019-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: When user tries to exit with CTRL-C message is confusing. Solution: Only mention ":qa!" when there is a changed buffer. (closes vim/vim#4163) https://github.com/vim/vim/commit/a84a3dd6635fcd2e07f510cba6a999585dcc381a vim-patch:8.1.1052: test for CTRL-C message sometimes fails Problem: test for CTRL-C message sometimes fails Solution: Make sure there are no changed buffers. https://github.com/vim/vim/commit/553e5a5c568e7d175b65b0472cd6d9843b25f4c8 vim-patch:8.1.1053: warning for missing return statement Problem: Warning for missing return statement. (Dominique Pelle) Solution: Add return statement. https://github.com/vim/vim/commit/d6c3f1fa2b5e1dd7dc87cf608d72b84ad696b58f
| * vim-patch:8.1.1041: test for Arabic no longer neededJan Edmund Lazo2019-07-28
| | | | | | | | | | | | Problem: Test for Arabic no longer needed. Solution: Remove the test for something that was intentionally left out. https://github.com/vim/vim/commit/295e3ba31f76818f195c654df506c88cb65f9289
| * vim-patch:8.1.1394: not restoring t_F2 in registers testJan Edmund Lazo2019-07-28
| | | | | | | | | | | | Problem: Not restoring t_F2 in registers test. Solution: Assign to &t_F2 instead of t_F2. (Andy Massimino, closes vim/vim#4434) https://github.com/vim/vim/commit/a5e44600ebb02057fb15ae7a2f15c5cae8f63bcc
| * vim-patch:8.1.1005: test fails because t_F2 is not setJan Edmund Lazo2019-07-28
| | | | | | | | | | | | Problem: Test fails because t_F2 is not set. Solution: Add try-catch. https://github.com/vim/vim/commit/55d81cd2a15d93dba89b2ff1c988d82789919b6b
* | Merge #10615 'vim-patch:8.1.0053'Justin M. Keyes2019-07-29
|\ \ | | | | | | fix #10604
| * | vim-patch:8.1.0053 use typval_T in the caller of call_vim_functioncangscop2019-07-29
| | | | | | | | | | | | | | | | | | Problem: unreliable types for complete function arguments Solution: fix argument type for functions w/ unreliable type conversion(Ozaki Kiichi) vim/vim#2993
| * | vim-patch:8.1.0053 use typval_T in the caller of call_vim_functioncangscop2019-07-28
| | | | | | | | | | | | | | | | | | Problem: unreliable types for complete function arguments Solution: fix argument type for functions w/ unreliable type conversion(Ozaki Kiichi) vim/vim#2993
| * | vim-patch:8.1.53 use typval_T in the caller of call_vim_functioncangscop2019-07-27
| | | | | | | | | | | | | | | | | | Problem: unreliable types for complete function arguments Solution: fix argument type for functions w/ unreliable type conversion(Ozaki Kiichi) vim/vim#2993
* | | PVS/V507: suppress false positive #10647Ihor Antonov2019-07-29
| | | | | | | | | | | | The pointer does not outlive the value in local scope as it gets reassigned immediately after scope.
* | | build/macOS: enable fallthrough attribute #10653Gavin D. Howard2019-07-29
| |/ |/|
* | lint: makemapIhor Antonov2019-07-28
| | | | | | | | | | | | | | * if braces * spaces * post increments * comment style
* | pvs/V560: part of conditional expression is always falseIhor Antonov2019-07-28
| | | | | | | | makemap: same condition is used to skip outer loop cycle
* | vim-patch:8.1.1138: add CompleteChanged #10644Justin M. Keyes2019-07-29
| | | | | | | | | | | | (This was originally a Neovim patch, but this commit merges some changes from the Vim patch.) https://github.com/vim/vim/commit/d7f246c68cfb97406bcd4b098a2df2d870b3ef92
* | vim-patch:8.1.0017: shell command completion has duplicates #10616erw72019-07-29
| | | | | | | | | | Problem: Shell command completion has duplicates. (Yegappan Lakshmanan) Solution: Use a hash table to avoid duplicates. (Ozaki Kiichi, closes vim/vim#539, closes vim/vim#2733) https://github.com/vim/vim/commit/62fe66f251263715968442e237742d9d3dfd5fa1
* | clang/"dead assignments" #10620Bartosz Miera2019-07-29
| | | | | | | | Also revert possibly-wrong change in f_sign_getplaced() from 652be3cb0040.
* | TextYankPost: spurious/too-early dispatch during delete #10392Jit2019-07-29
| | | | | | | | | | | | Problem: delete-with-register dispatches TextYankPost before updating yank registers Solution: Add flag to op_yank(). Fixes #10225
* | Merge #10643 from janlazo/vim-8.1.1765Justin M. Keyes2019-07-29
|\ \ | | | | | | vim-patch:8.1.{990,992,1765}
| * | vim-patch:8.1.0990: floating point exception with "%= 0" and "/= 0"Jan Edmund Lazo2019-07-28
| | | | | | | | | | | | | | | | | | Problem: Floating point exception with "%= 0" and "/= 0". Solution: Avoid dividing by zero. (Dominique Pelle, closes vim/vim#4058) https://github.com/vim/vim/commit/e21c1580b7acb598a6e3c38565434fe5d0e2ad7a
| * | vim-patch:8.1.1765: get(func, dict, def) does not work properlyJan Edmund Lazo2019-07-28
| | | | | | | | | | | | | | | | | | Problem: get(func, dict, def) does not work properly. Solution: Handle NULL dict better. (Takuya Fujiwara, closes vim/vim#4734) https://github.com/vim/vim/commit/f91aac5e3e3b8b1633d84eac2687ebbd76d8133b
* | | PVS/V547: expression is always true/false #10640Ihor Antonov2019-07-29
| | | | | | | | | | | | Functions marked with FUNC_ATTR_NONNULL_RET do not return NULL. Remove redundant checks.
* | | PVS/V512: memcpy overflow/underflow #10642Ihor Antonov2019-07-28
|/ / | | | | | | | | problem: bfredl: pvs thinks the type of the pointed at item is too small. solution: refactored address calculation.
* | PVS/V560: condition is always false #10638Ihor Antonov2019-07-28
| | | | | | * shorten_buf_name: condition inside outer if-branch with inverse condition
* | vim-patch:8.0.1753: fix various warnings #10639Ihor Antonov2019-07-28
| | | | | | | | | | | | vim-patch:8.0.1753: various warnings from a static analyser Problem: Various warnings from a static analyser Solution: Remove unneeded conditions. https://github.com/vim/vim/commit/1c17ffa4611f4efe68c61f7cdd9ed692a866ba75
* | context: shada_encode_regs(): init WriteMergerState #10637Justin M. Keyes2019-07-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Check shada_pack_xx() result, abort on failure. - Use xcalloc() to zero-initialize `wms`, fixes below ASAN failure. ASAN failure (running vim_spec.lua in a loop): ../src/nvim/shada.c:1773:13: runtime error: load of value 224, which is not a valid value for type 'bool' SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../src/nvim/shada.c:1773:13 Adding an explicit check just before the ASAN failed line: case kSDItemRegister: { if (*((int *)(void *)&entry.data.reg.is_unnamed) != 1 && *((int *)(void *)&entry.data.reg.is_unnamed) != 0) { abort(); (gdb) p entry.data.reg +p entry.data.reg $5 = {name = 49 '1', type = kMTLineWise, contents = 0x60200000c250, is_unnamed = true, contents_size = 1, width = 0, additional_data = 0x0} (gdb) p *((uint8_t *)(void *)&entry.data.reg.is_unnamed) +p *((uint8_t *)(void *)&entry.data.reg.is_unnamed) $7 = 2049
generated by cgit (git 2.34.1) at 2025-06-25 14:06:51 +0000