aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Merge #15402 fix(terminal): close without ! if the job is stoppedJustin M. Keyes2021-08-31
|\
| * fix(jobwait): always drain process event queues #15402Gregory Anders2021-08-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: jobwait() returns early if the job was stopped, but the job might have pending callbacks on its event queue which are required to complete its teardown. State such as term->closed might not be updated yet (by the pending callbacks), so codepaths such as :bdelete think the job is still running. Solution: Always flush the job's event queue before returning from jobwait(). ref #15349
| * fix(terminal): close without ! if the job is stoppedGregory Anders2021-08-31
|/ | | | | | - If the terminal job is still running then ! is still required. Closes #4683
* Merge pull request #15526 from bfredl/f_metaBjörn Linse2021-08-30
|\ | | | | fix(lua): make core vim module not dependent on $VIMRUNTIME modules
| * fix(lua): make core vim module not dependent on $VIMRUNTIME functionsBjörn Linse2021-08-30
| | | | | | | | | | | | | | | | | | | | fixes #15524 Note: this is obviously a quickfix. A scalabe solution will involve being able to specify a _list_ of modules to be put into packages.preload, without needing to manually copypasta a blurb of C code. Perhaps even involving bytecode for static builds (to speedup initialization)
* | fix(tutor): formatting, layout #15098Oliver Marriott2021-08-30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * fix(tutor): adjust over-80ch lines and corresponding expect file * fix(tutor): standardise indentation and formatting, add nowrap modeline - unifies the formatting/layout, which was a bit inconsistent, - adds a nowrap modeline Since the tutor uses a lot of conceals, which are included in the character count when calculating line wrapping, lines were breaking at what looked like odd spots, which gives a poor first impression and lowered readability. I have adjusted some lines to be over 80ch in the source, but once they're rendered out with conceals, they're actually under 80, so even with nowrap we don't visually extend past 80. fix #15088
* | fix(lsp): resolve bufnr in buf_is_attached (#15523)Jose Alvarez2021-08-30
|/
* chore(flake): fix for recent nixpkgs (#15520)Matthieu Coudron2021-08-30
| | | | | https://github.com/NixOS/nixpkgs/pull/134463 made keepDebugInfo obsolete for generic packages. This copies what keepDebugInfo used to do.
* Merge pull request #15498 from neovim/marvim/api-doc-update/masterThomas Vigouroux2021-08-30
|\ | | | | docs: regenerate
| * docs: regeneratemarvim2021-08-29
| |
* | vim-patch:8.2.2938: after using motion force from feedkeys() it sticks (#15240)Xiao2021-08-29
|/ | | | | Problem: After using motion force from feedkeys() it may not be reset. Solution: Clear motion_force in clearop(). (closes vim/vim#8323) https://github.com/vim/vim/commit/21492743e80c6740bac65a91311c28bede8ef2f8
* Merge pull request #15304 from bfredl/quantumtheoryBjörn Linse2021-08-29
|\ | | | | fix(lua): preserve argument list ... which has not the same length as #{...}
| * fix(lua): preserve argument lists which are not listsBjörn Linse2021-08-29
| |
* | docs: .git-blame-ignore-revs #15510Justin M. Keyes2021-08-28
|/
* Merge pull request #15509 from bfredl/miniperfBjörn Linse2021-08-28
|\ | | | | perf(api): avoid spurious allocations when converting small objects
| * perf(api): avoid spurious allocations when converting small objectsBjörn Linse2021-08-28
| | | | | | | | | | | | | | Converter functions use a heap-allocated stack to handle complex nested objects. However, these are often called with simple, primitive values like integers or bools wrapped in an Object. Avoid the memory allocation in this case using kvec_withinit_t
| * refactor(lua): rename nlua_msgpack_ => nlua_api_Björn Linse2021-08-28
| | | | | | | | | | | | These functions do not involve msgpack. Initially the nvim api was sometimes called the "msgpack API", but entry points from vim script and lua are equally valid (and don't need to reference "msgpack")
* | Merge pull request #15465 from dundargoc/refactor/uncrustifyBjörn Linse2021-08-28
|\ \ | | | | | | | | | | | | | | | refactor(codebase): Update uncrustify config and apply it on one file screen.c The plan is to go through the codebase in batches, and remove the most egregious "make lint" backlog failures, by applying this config.
| * | refactor: format screen.c with uncrustifyDundar Göc2021-08-28
| | |
| * | refactor: update uncrustify config file to better fit neovim style guideDundar Göc2021-08-28
|/ /
* / fix(lsp): check if buffer is valid in changetracking (#15505)Jose Alvarez2021-08-28
|/
* fix(process_wait): drain proc.events directly #15501Gregory Anders2021-08-27
| | | | | | | | | | After a process's refcnt is decremented to zero, it enqueues a `process_close_event` on its own event queue. In `process_wait`, this event should be processed immediately so that any process close callbacks are executed before `process_wait` returns. Update `process_wait` to always process the process's event queue after the process is freed, rather than the event queue passed in as an argument.
* Merge #15433 defaults: auto-create backup dirJustin M. Keyes2021-08-27
|\
| * docs: update 'backupdir' and 'undodir' descriptionsGregory Anders2021-08-27
| |
| * fix: remove trailing slashes before making directoryGregory Anders2021-08-27
| | | | | | | | | | | | Remove the trailing slashes from 'undofile' and 'backupdir' before creating directories. They cause problems on Windows which doesn't recognize these slashes as proper path separators.
| * feat: defaults: auto-create backup dirGregory Anders2021-08-27
|/ | | | | | | | | | | | | | | | | Copy the behavior of 'undodir' and create the last specified directory in the 'backupdir' option if it doesn't exist. Use trailing slashes for 'backupdir' as well as 'viewdir' and 'undodir' by default. Note that 'undodir' always behaves as though it has the trailing slashes, regardless of whether or not they are present. They are added to the default option value to minimize surprise. The '.' value in 'backupdir' is kept because the default behavior for backups is solely to have a backup if the save of the main file to disk fails. As soon as that save is completed the backup file is removed, so generally there is no need to put them in a central location. Co-authored by: murphy66 <murphy66@gmail.com>
* vim-patch:8.1.2229: color number column above/below cursor #15409zeertzjq2021-08-27
| | | | | Problem: Cannot color number column above/below cursor differently. Solution: Add LineNrAbove and LineNrBelow. (Shaun Brady, closes vim/vim#624) https://github.com/vim/vim/commit/efae76ab1a43d5a628d8c2fa4218ace6ba597f5d
* tests(lua/on_yank): assert conditions that fail correctly #15495notomo2021-08-27
| | | | The test added in 274a3504a790a799b28ee89c75e29fb4dbdff41f does not fail if the code changes are reverted.
* feat(lsp): get_border_size(): support repeating border char list #15474zeertzjq2021-08-27
|
* fix(lua): verify buffer in highlight.on_yank (#15482)notomo2021-08-26
| | | | | Resolve an issue with deferred clearing of highlight failing if the buffer is deleted before the timeout by checking whether the buffer is valid first.
* fix(man.vim): use -addr=other instead of -range=-1 #15172zeertzjq2021-08-26
| | | | | -range=-1 requires the current file to have at least <count> lines, whereas -addr=other doesn't. -addr=other also sets <count> to -1 by default when it is not specified, though this feature seems undocumented.
* fix(man.vim): reduce false positives for manReference #14242zeertzjq2021-08-26
| | | Co-authored-by: Anmol Sethi <hi@nhooyr.io>
* Merge #15293 Vimscript "method" syntaxJustin M. Keyes2021-08-26
|\ | | | | Port VimL's method call syntax - vim-patch:8.1.{1638,1800,1803,1807,1809,1816,1820,1821,1828,1834,1835,1861,1863,1878,1879,1888,1909,1911,1912}
| * feat(v:lua): support calling v:lua as a methodSean Dewar2021-08-13
| |
| * fix(v:lua): fix emsg when calling v:lua directlySean Dewar2021-08-12
| | | | | | | | | | | | | | | | | | | | v:lua expressions are represented using vvlua_partial. As v:lua isn't intended to be called directly, it's given an empty pt_name. Because of this, calling v:lua directly like "v:lua()" will cause "E117: Unknown function: ", with an empty name. Instead, have call_func() show the name "v:lua" in the emsg.
| * fix(eval_lambda): cherry-pick leak fix from v8.1.2107Sean Dewar2021-08-12
| | | | | | | | | | That patch also includes a test using test_refcount() for lambdas, but such test functions are N/A for Nvim.
| * feat(eval): partially port v8.1.1915Sean Dewar2021-08-12
| | | | | | | | Cannot be fully ported as chdir() hasn't been ported yet.
| * vim-patch:8.1.1911: more functions can be used as methodsSean Dewar2021-08-12
| | | | | | | | | | | | | | | | | | | | | | Problem: More functions can be used as methods. Solution: Make a few more functions usable as a method. https://github.com/vim/vim/commit/64b4d73524b9a2304d89b87529cd8d3cef14b856 Note that the old-style version of Test_byteidx() was already translated to a Lua test in 069_multibyte_formatting_spec.lua. Keep both versions, using Test_byteidx() to mainly test the method call syntax for byteidx() and byteidxcomp().
| * vim-patch:8.1.1909: more functions can be used as methodsSean Dewar2021-08-12
| | | | | | | | | | | | Problem: More functions can be used as methods. Solution: Make a few more functions usable as a method. https://github.com/vim/vim/commit/e49fbff384e45dd17fed72321c26937edf6de16b
| * vim-patch:8.1.1888: more functions can be used as methodsSean Dewar2021-08-12
| | | | | | | | | | | | | | | | | | Problem: More functions can be used as methods. Solution: Make various functions usable as a method. https://github.com/vim/vim/commit/073e4b92e613d22ce7b16e0fbf5c0e40cb5f9b2c test_popup.vim already has the changes from this patch (they're N/A anyway).
| * vim-patch:8.1.1879: more functions can be used as methodsSean Dewar2021-08-12
| | | | | | | | | | | | | | | | | | Problem: More functions can be used as methods. Solution: Make float functions usable as a method. https://github.com/vim/vim/commit/93cf85f9ef02931de3f8c8e536a137da0b48b7dc Fix atan2() doc typo (patch referred to it as atan()). Adjust Test_fmod() method test to expect "str2float('nan')".
| * vim-patch:8.1.1878: negative float before method not parsed correctlySean Dewar2021-08-12
| | | | | | | | | | | | Problem: Negative float before method not parsed correctly. Solution: Apply "!" and "-" in front of expression before using ->. https://github.com/vim/vim/commit/9cfe8f6e68de4bfb5942d84f4465de914a747b3f
| * vim-patch:8.1.1863: confusing error when using a builtin function as methodSean Dewar2021-08-12
| | | | | | | | | | | | | | Problem: Confusing error when using a builtin function as method while it does not support that. Solution: Add a specific error message. https://github.com/vim/vim/commit/9174639a82799011cfa0013cbc4c4709b3833bf0
| * vim-patch:8.1.1861: only some assert functions can be used as a methodSean Dewar2021-08-12
| | | | | | | | | | | | | | | | Problem: Only some assert functions can be used as a method. Solution: Allow using most assert functions as a method. https://github.com/vim/vim/commit/24278d2407dfbc8d93eb36593cdd006ff5d86f94 Port tests to assert_spec.lua.
| * vim-patch:8.1.1835: cannot use printf() as a methodSean Dewar2021-08-12
| | | | | | | | | | | | Problem: Cannot use printf() as a method. Solution: Pass the base as the second argument to printf(). https://github.com/vim/vim/commit/fd8ca21b3ff207e44891aef922935d4adcd140cf
| * vim-patch:8.1.1834: cannot use a lambda as a methodSean Dewar2021-08-12
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Cannot use a lambda as a method. Solution: Implement ->{lambda}(). (closes vim/vim#4768) https://github.com/vim/vim/commit/22a0c0c4ecd23b6c43f79ba9b92899ca0b426e29 Add an additional lua_funcname argument to call_func_rettv() to maintain support for v:lua. A memory leak was introduced with this patch that was fixed in v8.1.2107.
| * vim-patch:8.1.1828: not strict enough checking syntax of method invocationSean Dewar2021-08-12
| | | | | | | | | | | | Problem: Not strict enough checking syntax of method invocation. Solution: Check there is no white space inside ->method(. https://github.com/vim/vim/commit/5184132ec015f5889a3195d911e609d214f06bed
| * vim-patch:8.1.1821: no test for wrong number of method argumentsSean Dewar2021-08-12
| | | | | | | | | | | | Problem: No test for wrong number of method arguments. Solution: Add a test. https://github.com/vim/vim/commit/f97d46f816e84edb6899a903a1c334a50a6d31bb
| * vim-patch:8.1.1820: using expr->FuncRef() does not workSean Dewar2021-08-12
| | | | | | | | | | | | Problem: Using expr->FuncRef() does not work. Solution: Make FuncRef work as a method. https://github.com/vim/vim/commit/761fdf01c6e307c448cec2684f8b315ba6d1f454
| * vim-patch:8.1.1816: cannot use a user defined function as a methodSean Dewar2021-08-12
| | | | | | | | | | | | | | Problem: Cannot use a user defined function as a method. Solution: Pass the base as the first argument to the user defined function after "->". (partly by FUJIWARA Takuya) https://github.com/vim/vim/commit/fcfe1a9b8950b8b211ab3b24d84b17c6847ea43f
generated by cgit (git 2.34.1) at 2025-05-21 04:12:07 +0000