aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* | | | fix(mouse.c): fix mouse drag positions on multigrid #12667Ville Hakulinen2021-09-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, multigrid mouse drag positions are handled incorrectly if the drag event is not in the top left grid. Fix this by not adjusting the position of the event in jump_to_mouse. related: #15091
* | | | refactor: format files with uncrustify #15607dundargoc2021-09-10
|/ / /
* | | vim-patch:8.2.3399: Octave files are not recognized (#15622)Christian Clason2021-09-10
| | | | | | | | | | | | | | | Problem: Octave files are not recognized. Solution: Detect Octave files. (Doug Kearns) https://github.com/vim/vim/commit/deba5eb195d6ac70171d4973091fa884809fa3fa
* | | vim-patch:partial 2346a6378483 (#15599)Christian Clason2021-09-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update runtime files https://github.com/vim/vim/commit/2346a6378483c9871016f9fc821ec5cbea638f13 omit doc/vim.man omit doc/vim9.txt omit doc/vimdiff.txt omit doc/vimdiff.man skip doc/eval.txt (missing patch 8.2.2324) skip doc/help.txt (missing patch 8.2.2344)
* | | Merge pull request #15566 from bfredl/mpackBjörn Linse2021-09-09
|\ \ \ | | | | | | | | libs: vendor libmpack and libmpack-lua
| * | | fix(ci): don't enrage the CI Gods by calling a file 'core.*'Björn Linse2021-09-09
| | | |
| * | | feat(lua): make vim.mpack support vim.NIL and vim.empty_dict()Björn Linse2021-09-09
| | | |
| * | | feat(lua): add vim.mpack for msgpack support in luaBjörn Linse2021-09-09
| | | |
| * | | fix(build): make vendored libmpack and libmpack-lua build properlyBjörn Linse2021-09-09
| | | |
| * | | build: vendor libmpack/libmpack-lua sources from ↵Björn Linse2021-09-09
| | | | | | | | | | | | | | | | b593809d93b5299bbee4e1d18e2e2d55f9fa53a6
| * | | build: vendor libmpack source from libmpack/libmpack ↵Björn Linse2021-09-09
| | | | | | | | | | | | | | | | 22b1fd90285117c995728511f9525d29520a8c82
* | | | Merge pull request #15091 from yatli/mouse_drag_fixBjörn Linse2021-09-09
|\ \ \ \ | |/ / / |/| | | fix #15075 (mouse crash in multigrid)
| * | | fix(multigrid): #15075 mouse events crash neovimYatao Li2021-09-08
| | | |
* | | | docs: naming conventionsJustin M. Keyes2021-09-09
| | | |
* | | | feat(lua)!: register_keystroke_callback => on_keyJustin M. Keyes2021-09-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Analogous to nodejs's `on('data', …)` interface, here on_key is the "add listener" interface. ref 3ccdbc570d85 #12536 BREAKING_CHANGE: vim.register_keystroke_callback() is now an error.
* | | | build: move src/nvim/xdiff to src/xdiffChristian Clason2021-09-08
| | | | | | | | | | | | | | | | Closes #11239
* | | | vim-patch:8.2.3390: included xdiff code is outdatedChristian Clason2021-09-08
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Included xdiff code is outdated. Solution: Sync with xdiff in git 2.33. (Christian Brabandt, closes vim/vim#8431) https://github.com/vim/vim/commit/ba02e4720f863fdb456e7023520f0a354eec0dcf
* | | | vim-patch:d2ea7cf10a4d #15571Christian Clason2021-09-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update runtime files https://github.com/vim/vim/commit/d2ea7cf10a4d026ebd402594d656af7d5c811c24 omit `runtime/doc/if_tcl.txt` omit `runtime/doc/textprop.txt` omit `runtime/tutor/*` omit `runtime/syntax/vim.vim` (cherry-picked in https://github.com/neovim/neovim/commit/2dd7828511d04a8b7f1ac4331c719a751a5db869) manual merge of `runtime/pack/dist/opt/termdebug/plugin/termdebug.vim`
* | | | refactor: format files with uncrustifyDundar Göc2021-09-07
|/ / /
* | | fix(screen): missing search highlights when redrawing from timer #15380Jit2021-09-06
| | | | | | | | | | | | | | | | | | | | | * Revert "vim-patch:8.1.2294: cursor pos wrong with concealing and search causes a scroll" * Add a test which covers #13074 910bbc3cca796f7fa941e0f6176cd0061de0e01c while reverting the screen.c code changes from there. Fixes #14064
* | | Merge pull request #15569 from bfredl/end_fillBjörn Linse2021-09-05
|\ \ \ | | | | | | | | refactor(screen): let win_line() always handle fillers after last line
| * | | refactor(screen): let win_line() always handle fillers after last lineBjörn Linse2021-09-05
| | | |
* | | | build: fix fpclassify -Wfloat-conversion warning #15570Ben Noordhuis2021-09-05
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Work around a glibc bug where it truncates the argument to fpclassify() from double to float by implementing fpclassify() ourselves. Correctness test (Note that the FP_SUBNORMAL test depends on an atof() that knows how to parse subnormals. Glibc does, not sure about other libcs.): #include <math.h> #include <stdint.h> #include <string.h> int xfpclassify(double d) { uint64_t m; int e; memcpy(&m, &d, sizeof(m)); e = 0x7ff & (m >> 52); m = 0xfffffffffffffULL & m; switch (e) { default: return FP_NORMAL; case 0x000: return m ? FP_SUBNORMAL : FP_ZERO; case 0x7ff: return m ? FP_NAN : FP_INFINITE; } } #include <assert.h> #include <stdlib.h> int main(void) { assert(FP_ZERO == xfpclassify(atof("0.0"))); assert(FP_ZERO == xfpclassify(atof("-0.0"))); assert(FP_NORMAL == xfpclassify(atof("1.0"))); assert(FP_NORMAL == xfpclassify(atof("-1.0"))); assert(FP_INFINITE == xfpclassify(atof("inf"))); assert(FP_INFINITE == xfpclassify(atof("-inf"))); assert(FP_NAN == xfpclassify(atof("nan"))); assert(FP_NAN == xfpclassify(atof("-nan"))); assert(FP_SUBNORMAL == xfpclassify(atof("1.8011670033376514e-308"))); return 0; }
* | | refactor: update uncrustify config and format screen.cDundar Göc2021-09-03
| | | | | | | | | | | | | | | Also set new option cmt_trailing_single_line_c_to_cpp to true. It converts trailing, single-line c-comments (/**/) into cpp-comments (//).
* | | fix(defaults): "syntax sync maxlines=1" on CmdwinEnter #15552Justin M. Keyes2021-09-02
| | | | | | | | | | | | | | | | | | | | | I mistakenly suggested maxlines=&cmdwinheight, forgetting that it is calculated from topline, not cursor. maxlines=1 makes the most sense in cmdwin. ref #15401 622a36b1f1c652a8de433028bc4a03a1216db23f
* | | feat(defaults): limit syntax cost on CmdwinEnter #15401Gregory Anders2021-09-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | Add a new default autocommand to limit syntax highlighting synchronization in the command window. This refactors the nvim_terminal autocommand out of main() and into a new init_default_autocmds() function, which is now part of the startup process and can be further extended with more default autocommands down the road. ref #6289 #6399
* | | feat(api): nvim_get_chan_info: include "argv" for jobs #15537Justin M. Keyes2021-09-01
| |/ |/| | | ref #15440
* | 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
* | 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)
* | 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
* | fix(lua): preserve argument lists which are not listsBjörn Linse2021-08-29
| |
* | 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")
* | | refactor: format screen.c with uncrustifyDundar Göc2021-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.
* | 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
* | 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
generated by cgit (git 2.34.1) at 2025-06-28 00:53:12 +0000