aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/eval.c
Commit message (Collapse)AuthorAge
...
* vim-patch:8.1.1319: computing function length name in many placesJan Edmund Lazo2020-09-30
| | | | | | | | | | | Problem: Computing function length name in many places. Solution: compute name length in call_func(). https://github.com/vim/vim/commit/6ed8819822994512c160006bd1204aa11ae3c494 In call_func(), reassign "len" param to (int)STRLEN(funcname) instead of using vim_strsave() which runs strlen(). "len" param is checked for v:lua functions. call_func() states that strlen() is used if "len" is set to -1.
* vim-patch:8.2.0824: still not enough memory allocated when converting stringJan Edmund Lazo2020-09-19
| | | | | | | Problem: Still not enough memory allocated when converting string with special character. Solution: Reserve space for expanding K_SPECIAL. (closes vim/vim#6130) https://github.com/vim/vim/commit/1919371b2b9ddb1a645f40b59adbd89317530882
* vim-patch:8.2.0817: not enough memory allocated when converting stringJan Edmund Lazo2020-09-19
| | | | | | | | | Problem: Not enough memory allocated when converting string with special character. Solution: Reserve space for modifier code. (closes vim/vim#6130) https://github.com/vim/vim/commit/f7271e831614d15d173c7f562cc26f48c2554ce9 Cherry-pick Test_eval(), Test_nr2char() from patch 8.2.0448.
* buf_attach: fix buffer updates with setline()Björn Linse2020-09-16
|
* win/env: fix stdpath()/XDG_* initialization, parsing #12829erw72020-09-07
| | | | | | | | - Windows environment variables are semicolon-separated, but some logic was assuming colon (:). This broke initialization and parsing of XDG_CONFIG_DIRS, XDG_DATA_DIRS, 'runtimepath', stdpath(), etc. - test/defaults_spec: enable tests on Windows ref #12793
* eval_call_provider(): free unused return value #12819Jacques Germishuys2020-09-01
| | | Caller can pass discard=true to free the unwanted return value.
* vim-patch:8.2.0607: gcc warns for using uninitialized variableJan Edmund Lazo2020-08-19
| | | | | | Problem: Gcc warns for using uninitialized variable. (John Marriott) Solution: Set name_end also for environment variables. https://github.com/vim/vim/commit/2bb76accc66d17f2c027c04396082c46f410bfea
* vim-patch:8.2.1471: :const only locks the variable, not the value (#12765)Jan Edmund Lazo2020-08-16
| | | | | Problem: :const only locks the variable, not the value. Solution: Lock the value as ":lockvar 1 var" would do. (closes vim/vim#6719) https://github.com/vim/vim/commit/241572794f7e93d2f8b762de2300e5f7e4f07628
* vim-patch:8.2.1379: curly braces expression ending in " }" does not workJan Edmund Lazo2020-08-14
| | | | | | Problem: Curly braces expression ending in " }" does not work. Solution: Skip over white space when checking for "}". (closes vim/vim#6634) https://github.com/vim/vim/commit/ae95a3946b012d4e68bcb20b28f691f6d3b9caaf
* vim-patch:8.2.1361: error for white space after expression in assignmentJan Edmund Lazo2020-08-14
| | | | | | Problem: Error for white space after expression in assignment. Solution: Skip over white space. (closes vim/vim#6617) https://github.com/vim/vim/commit/6a25026262e2cdbbd8738361c5bd6ebef8862d87
* vim-patch:8.2.1360: stray error for white space after expressionJan Edmund Lazo2020-08-14
| | | | | | Problem: Stray error for white space after expression. Solution: Ignore trailing white space. (closes vim/vim#6608) https://github.com/vim/vim/commit/f96e9dec636d7d105b015680d8c5d6b47d936e01
* eval: improve ex_execute (#12445)erw72020-07-20
|
* vim-patch:8.2.0899: assert_equalfile() does not give a hint about the differenceJan Edmund Lazo2020-07-19
| | | | | | Problem: Assert_equalfile() does not give a hint about the difference. Solution: Display the last seen text. https://github.com/vim/vim/commit/30cc44a97f0ba1349e1a522dab22b11f47888183
* vim-patch:8.2.0893: assert_equalfile() does not take a third argumentJan Edmund Lazo2020-07-19
| | | | | | Problem: Assert_equalfile() does not take a third argument. Solution: Implement the third argument. (Gary Johnson) https://github.com/vim/vim/commit/fb517bac2384798bb5142ed1f75f965f93984c0a
* vim-patch:8.1.0819: a failed assert with a long string is hard to readJan Edmund Lazo2020-07-19
| | | | | | Problem: A failed assert with a long string is hard to read. Solution: Shorten the assert message. https://github.com/vim/vim/commit/865767126e97d9ac65e052a657b29bbc32dcb512
* lua: Add ability to pass tables with __callTJ DeVries2020-07-10
| | | | | | | | | | | | vim-patch:8.2.1054: not so easy to pass a lua function to Vim vim-patch:8.2.1084: Lua: registering function has useless code I think I have also opened up the possibility for people to use these callbacks elsewhere, since I've added a new struct that we should be able to use. Also, this should allow us to determine what the state of a list is in Lua or a dictionary in Lua, since we now can track the luaref as we go.
* vim-patch:8.1.1372: when evaluating 'statusline' the current window is unknownJan Edmund Lazo2020-07-04
| | | | | | | | Problem: When evaluating 'statusline' the current window is unknown. (Daniel Hahler) Solution: Set "g:actual_curwin" for %{} items. Set "g:statusline_winid" when evaluationg %!. (closes vim/vim#4406, closes vim/vim#3299) https://github.com/vim/vim/commit/1c6fd1e100fd0457375642ec50d483bcc0f61bb2
* eval: fix pvs/v547Jan Edmund Lazo2020-06-18
|
* vim-patch:8.2.0629: setting a boolean option to v:false does not workBilly Su2020-06-06
| | | | | | | Problem: Setting a boolean option to v:false does not work. Solution: Do not use the string representation of the value. (Christian Brabandt, closes vim/vim#5974) https://github.com/vim/vim/commit/65d032c779a43b767497e15e6a32d04a6a8fa65d
* vim-patch:8.2.0111: VAR_SPECIAL is also used for booleansBilly Su2020-06-06
| | | | | | Problem: VAR_SPECIAL is also used for booleans. Solution: Add VAR_BOOL for better type checking. https://github.com/vim/vim/commit/9b4a15d5dba354d2e1e02871470bad103f34769a
* vim-patch:8.1.2335: error message for function arguments may use NULL pointerJan Edmund Lazo2020-06-04
| | | | | | | Problem: Error message for function arguments may use NULL pointer. (Coverity) Solution: Use the original function name. https://github.com/vim/vim/commit/2118a302957dea352174722bf355376901f49b9b
* vim-patch:8.2.0491: cannot recognize a <script> mapping using maparg()Jan Edmund Lazo2020-06-04
| | | | | | Problem: Cannot recognize a <script> mapping using maparg(). Solution: Add the "script" key. (closes vim/vim#5873) https://github.com/vim/vim/commit/2da0f0c445da3c9b35b2a0cd595d10e81ad2a6f9
* Merge pull request #10905 from erw7/vim-8.1.0475Matthieu Coudron2020-05-25
|\ | | | | vim-patch:8.1.{475,800,868,1007,1027,1031,1033,1037,1058,1435,1484,1485}
| * eval: fix problem with free_unref_funccal not being callederw72020-05-25
| |
| * vim-patch:8.1.1485: double free when garbage_collect() is used in autocommanderw72020-05-25
| | | | | | | | | | | | Problem: Double free when garbage_collect() is used in autocommand. Solution: Have garbage collection also set the copyID in funccal_stack. https://github.com/vim/vim/commit/c07f67ad0e9c48a07d49f2d67eb63e183a22386a
| * vim-patch:8.1.1484: some tests are slowDaniel Hahler2020-05-25
| | | | | | | | | | | | | | Problem: Some tests are slow. Solution: Add timing to the test messages. Fix double free when quitting in VimLeavePre autocmd. https://github.com/vim/vim/commit/75ee544f99ca66be8105570c6309d95435ad30d1
| * vim-patch:8.1.1007: using closure may consume a lot of memoryerw72020-05-07
| | | | | | | | | | | | | | Problem: Using closure may consume a lot of memory. Solution: unreference items that are no longer needed. Add a test. (Ozaki Kiichi, closes vim/vim#3961) https://github.com/vim/vim/commit/209b8e3e3bf7a4a3d102134124120f6c7f57d560
| * vim-patch:8.1.0475: memory not freed on exit when quit in autocmderw72020-05-07
| | | | | | | | | | | | Problem: Memory not freed on exit when quit in autocmd. Solution: Remember funccal stack when executing autocmd. https://github.com/vim/vim/commit/27e80c885bcb5c5cf6a6462d71d6c81b06ba2451
* | vim-patch:8.1.2233: cannot get the Vim command line arguments (#12117)kuuote2020-05-24
| | | | | | | | | | Problem: Cannot get the Vim command line arguments. Solution: Add v:argv. (Dmitri Vereshchagin, closes vim/vim#1322) https://github.com/vim/vim/commit/69bf634858a2a75f2984e42b1e4017bc529a040a
* | vim-patch:8.1.1084: cannot delete a match from another window (#12325)Shougo2020-05-16
|/ | | | | | Problem: Cannot delete a match from another window. (Paul Jolly) Solution: Add window ID argument to matchdelete(), clearmatches(), getmatches() and setmatches(). (Andy Massimino, closes vim/vim#4178) https://github.com/vim/vim/commit/aff749145e23c0f20b5158d1d3a942948ed138e3
* vim-patch:8.1.1120: cannot easily get directory entry matches #12222Hennadii Chernyshchyk2020-05-05
| | | | | | | Problem: Cannot easily get directory entry matches. Solution: Add the readdir() function. (Yasuhiro Matsumoto, closes vim/vim#2439) https://github.com/vim/vim/commit/543c9b1921d7605498b54afdef518e312f1b4515 closes #12212
* Merge pull request #12018 from janlazo/vim-8.0.1123Matthieu Coudron2020-04-27
|\ | | | | [RFC]vim-patch:8.0.{1123,1125,1138,1139,1142,1292,1334,1375},8.1.1264
| * vim-patch:8.0.1123: cannot define a toolbar for a windowJan Edmund Lazo2020-04-26
| | | | | | | | | | | | | | | | | | | | Problem: Cannot define a toolbar for a window. Solution: Add a window-local toolbar. https://github.com/vim/vim/commit/1b9645de3c05f37b5c30e78f999351b0cf486ade "WinBar" code in "screen.c" was not ported. Fix https://github.com/neovim/neovim/issues/11513#issuecomment-562012827
* | Merge #11851 'eval.c: factor out eval/userfunc.c'Justin M. Keyes2020-04-27
|\ \ | | | | | | vim-patch:7.4.2058
| * \ Merge #11851 'eval.c: factor out eval/userfunc.c'Justin M. Keyes2020-04-26
| |\ \ | | |/ | |/| | | | vim-patch:7.4.2058
| | * rename: user_funcs -> userfuncJakub Łuczyński2020-02-13
| | | | | | | | | | | | Lets stick with vim for now
| | * fix: moved some static inline functionJakub Łuczyński2020-02-13
| | |
| | * fix: vvlua_partialJakub Łuczyński2020-02-13
| | |
| | * fix: made eval_lavars_used globalJakub Łuczyński2020-02-13
| | |
| | * Removed redundant defineJakub Łuczyński2020-02-13
| | |
| | * fix: factor out make_partialJakub Łuczyński2020-02-13
| | |
| | * fix: prof functionsJakub Łuczyński2020-02-13
| | |
| | * fix: var_set_globalJakub Łuczyński2020-02-13
| | |
| | * fix: find_var_ht_dictJakub Łuczyński2020-02-13
| | |
| | * fix: factor out new functionsJakub Łuczyński2020-02-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | free_unref_funccal get_funccal_local_var get_funccal_args_var get_current_funccal_dict set_ref_in_previous_funccal set_ref_in_call_stack set_ref_in_func_args note: In vim semantic for garbage_collect was changed (the result of free_unref_funccal is ignored, bug or intentional?) For nvim I did leave previous behavior thus did_free = did_free || free_unref_funccal(copyID, testing); instead of just free_unref_funccal(copyID, testing);
| | * fix: func_initJakub Łuczyński2020-02-13
| | |
| | * unstatic some functionsJakub Łuczyński2020-02-13
| | |
| | * moved more stuffJakub Łuczyński2020-02-13
| | |
| | * moved functions to user_funcs.c (no code changes)Jakub Łuczyński2020-02-13
| | |
* | | vim-patch:8.1.2225: the "last used" info of a buffer is under usedRob Pilling2020-04-21
|/ / | | | | | | | | | | | | Problem: The "last used" info of a buffer is under used. Solution: Add "lastused" to getbufinfo(). List buffers sorted by last-used field. (Andi Massimino, closes vim/vim#4722) https://github.com/vim/vim/commit/52410575be50d5c40bbe6380159df48cfc382ceb
generated by cgit (git 2.34.1) at 2025-04-30 23:19:38 +0000