aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Merge pull request #10703 from ngortheone/clang_dead2Björn Linse2019-08-07
|\ | | | | | | | | | | clang/"dead assignment": suppessed getchar.c Possibly invalid, read on line 1972: if (keylen >= 0 && keylen <= typebuf.tb_len) {
| * clang/"dead assignment": suppessedIhor Antonov2019-08-05
| | | | | | | | | | To ensure consistency and avoid possible errors in the code the assigment is considered to be legit.
* | Merge pull request #10513 from bfredl/bytecountBjörn Linse2019-08-06
|\ \ | | | | | | api/lua: add {byte_count} parameter to line region change event
| * | lua: support getting UTF-32 and UTF-16 sizes of replaced textBjörn Linse2019-08-06
| | |
| * | lua: add {old_byte_size} to on_lines buffer change eventBjörn Linse2019-08-06
| | |
* | | Fix list_features to include space after first feature (#10711)Daniel Hahler2019-08-06
|/ / | | | | | | | | | | | | | | | | Regressed in e134cc9d4a: the use of list_in_columns was not adding a space after the first features, because we do not start on a new line: > Features: -acl+iconv +tui This moves all the related code to `list_features`, and just joins them with spaces.
* | f_environ: cleanup/refactorDaniel Hahler2019-08-06
| | | | | | | | | | - use os_getenvname_at_index / os_getenv - f_getenv: empty (*p == NUL) is not null (undefined)
* | vim-patch:8.1.1305: there is no easy way to manipulate environment variablesDaniel Hahler2019-08-06
| | | | | | | | | | | | | | Problem: There is no easy way to manipulate environment variables. Solution: Add environ(), getenv() and setenv(). (Yasuhiro Matsumoto, closes vim/vim#2875) https://github.com/vim/vim/commit/691ddeefb545d8488e5a495af61caba2e57b3de9
* | clang/"dead assignment": screen.c #10702Ihor Antonov2019-08-06
| | | | | | | | | | | | | | Suppress the warning. mb_c and mb_l describe a char together, they are not independent variables. The coupled assignments are good practice to avoid future confusion, even if the current code doesn't use an assigned value.
* | vim-patch:8.1.1439: ga_grow(): 1.5x growth rate #10699Jan Edmund Lazo2019-08-05
|/ | | | | | Problem: Json_encode() is very slow for large results. Solution: In the growarray use a growth of at least 50%. (Ken Takata, closes vim/vim#4461) https://github.com/vim/vim/commit/c47ed44be76a520ded90913099771999c8a79eeb
* Merge pull request #10690 from bfredl/lua_printBjörn Linse2019-08-05
|\ | | | | lua: laundry list (crashes and additions)
| * lua: add vim.in_fast_event() to check if we are in a luv callbackBjörn Linse2019-08-05
| |
| * lua: do not crash on syntax error in debug.debug()Björn Linse2019-08-05
| |
| * lua: immediate-callback safe print()Björn Linse2019-08-05
| |
* | vim-patch:8.1.1383: warning for size_t/int mixup (#10694)Jan Edmund Lazo2019-08-05
| | | | | | | | | | Problem: Warning for size_t/int mixup. Solution: Change type. (Mike Williams) https://github.com/vim/vim/commit/d33a764123a8aedb20cd84aeff3b94810ee67c4c
* | :doautocmd : Never show "No matching autocommands" #10689Justin M. Keyes2019-08-05
| | | | | | | | | | | | | | | | The message is useless, it doesn't even mention the event name. vim_dev discussion: https://groups.google.com/forum/#!msg/vim_dev/RTbq58TMq9w/Xr4rSoUTCgAJ ref: https://github.com/vim/vim/issues/4300
* | vim-patch:8.1.1311: test: abort autocmd with exception #10692Jan Edmund Lazo2019-08-05
| | | | | | | | | | | | Problem: Aborting an autocmd with an exception is not tested. Solution: Add a test. Also shows how to abort a command by throwing an exception. https://github.com/vim/vim/commit/23b5139234a79567097ca73aba15ea134381b934
* | vim-patch:8.1.1251: test completion of mapping keys #10691Jan Edmund Lazo2019-08-05
|/ | | | | Problem: No test for completion of mapping keys. Solution: Add a test. Also clean up the code. https://github.com/vim/vim/commit/2cb9f0253228478ec27265ff40f59c629874d695
* provider: check #Call() if g:loaded_xx_provider=2Justin M. Keyes2019-08-04
|
* provider: skip non-provider has() feature-namesJustin M. Keyes2019-08-04
| | | | | We don't want to retry autoload sourcing (slow) for every random has() query that finds it way to eval_call_provider().
* provider: g:loaded_xx_provider=2 means "enabled and working"Justin M. Keyes2019-08-04
| | | | | Value of 1 cannot be used, because users might set that in their vimrc to _disable_ a provider, which would confuse :checkhealth and has().
* provider: decide status by g:loaded_xx_providerJustin M. Keyes2019-08-04
|
* 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
generated by cgit (git 2.34.1) at 2025-06-25 03:23:19 +0000