summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* patch 8.2.1882: Vim9: v:disallow_let is no longer neededv8.2.1882Bram Moolenaar2020-10-214-14/+6
| | | | | Problem: Vim9: v:disallow_let is no longer needed. Solution: Remove v:disallow_let.
* patch 8.2.1881: cannot build with GTK3v8.2.1881Bram Moolenaar2020-10-212-10/+21
| | | | | Problem: Cannot build with GTK3. Solution: Adjust form functions.
* patch 8.2.1880: Vim9: asan complains about adding zero to NULLv8.2.1880Bram Moolenaar2020-10-212-4/+8
| | | | | Problem: Vim9: Asan complains about adding zero to NULL. Solution: Check for argument count first.
* patch 8.2.1879: Vim9: argument types of insert() not checked when compilingv8.2.1879Bram Moolenaar2020-10-215-9/+59
| | | | | Problem: Vim9: argument types of insert() not checked when compiling. Solution: Add argument type checks for insert().
* patch 8.2.1878: GTK: error for redefining functionv8.2.1878Bram Moolenaar2020-10-215-128/+109
| | | | | | Problem: GTK: error for redefining function. (Tony Mechelynck) Solution: Remove "gtk_" prefix from local functions and prepend "gui_" to global functions.
* patch 8.2.1877: test for function list failsv8.2.1877Bram Moolenaar2020-10-212-14/+16
| | | | | Problem: Test for function list fails. Solution: Move "obsolete" comments one line up.
* patch 8.2.1876: Vim9: argument types are not checked at compile timev8.2.1876Bram Moolenaar2020-10-217-1051/+1644
| | | | | | | Problem: Vim9: argument types for builtin functions are not checked at compile time. Solution: Add an argument type checking mechanism. Implement type checks for one function.
* patch 8.2.1875: warning when building GTK guiv8.2.1875Bram Moolenaar2020-10-212-2/+4
| | | | | Problem: Warning when building GTK gui. Solution: Add missing function parameter.
* patch 8.2.1874: can't do something just before leaving Insert modev8.2.1874Bram Moolenaar2020-10-216-5/+27
| | | | | Problem: Can't do something just before leaving Insert mode. Solution: Add the InsertLeavePre autocommand event. (closes #7177)
* patch 8.2.1873: Vim9: missing white space when using <f-args>v8.2.1873Bram Moolenaar2020-10-203-1/+22
| | | | | Problem: Vim9: missing white space when using <f-args>. Solution: Add spaces. (Christian J. Robinson)
* patch 8.2.1872: matchfuzzy() does not prefer sequential matchesv8.2.1872Bram Moolenaar2020-10-203-7/+23
| | | | | | Problem: Matchfuzzy() does not prefer sequential matches. Solution: Give sequential matches a higher bonus. (Christian Brabandt, closes #7140)
* patch 8.2.1871: using %v in 'errorformat' may fail before %Zv8.2.1871Bram Moolenaar2020-10-203-1/+20
| | | | | Problem: Using %v in 'errorformat' may fail before %Z. Solution: Set qf_viscol only when qf_col is set. (closes #7169)
* patch 8.2.1870: Vim9: no need to keep all script variablesv8.2.1870Bram Moolenaar2020-10-207-19/+76
| | | | | | Problem: Vim9: no need to keep all script variables. Solution: Only keep script variables when a function was defined that could use them. Fix freeing static string on exit.
* patch 8.2.1869: Vim9: memory leak when using add()v8.2.1869Bram Moolenaar2020-10-192-0/+3
| | | | | Problem: Vim9: memory leak when using add(). Solution: Free the added item.
* patch 8.2.1868: Vim9: no error for missing space after comma in dictv8.2.1868Bram Moolenaar2020-10-193-0/+8
| | | | | Problem: Vim9: no error for missing space after comma in dict. Solution: Check for white space. (closes #6672)
* patch 8.2.1867: Vim9: argument to add() not checked for blobv8.2.1867Bram Moolenaar2020-10-197-5/+106
| | | | | Problem: Vim9: argument to add() not checked for blob. Solution: Add the BLOBAPPEND instruction.
* patch 8.2.1866: Vim9: appending to pushed blob gives wrong resultv8.2.1866Bram Moolenaar2020-10-193-0/+9
| | | | | Problem: Vim9: appending to pushed blob gives wrong result. Solution: Set ga_maxlen when copying a blob.
* patch 8.2.1865: Vim9: add() does not check type of argumentv8.2.1865Bram Moolenaar2020-10-197-4/+122
| | | | | Problem: Vim9: add() does not check type of argument. Solution: Inline the add() call. (closes #7160)
* patch 8.2.1864: Vim9: no error for wrong list typev8.2.1864Bram Moolenaar2020-10-193-41/+103
| | | | | Problem: Vim9: no error for wrong list type. Solution: Add flag to indicate a constant. (closes #7160)
* patch 8.2.1863: json code not sufficiently testedv8.2.1863Bram Moolenaar2020-10-192-1/+13
| | | | | Problem: Json code not sufficiently tested. Solution: Add more test cases. (Dominique Pellé, closes #7166)
* patch 8.2.1862: vim9: memory leak when compiling lambda failsv8.2.1862Bram Moolenaar2020-10-182-0/+5
| | | | | Problem: vim9: memory leak when compiling lambda fails. Solution: Call clear_evalarg().
* patch 8.2.1861: Vim9: no specific error when parsing lambda failsv8.2.1861Bram Moolenaar2020-10-183-19/+20
| | | | | Problem: Vim9: no specific error when parsing lambda fails. Solution: Also give syntax errors when not evaluating. (closes #7154)
* patch 8.2.1860: Vim9: memory leak when throwing empty stringv8.2.1860Bram Moolenaar2020-10-172-0/+3
| | | | | Problem: Vim9: memory leak when throwing empty string. Solution: Free the empty string.
* patch 8.2.1859: Vim9: crash in unpack assignmentv8.2.1859Bram Moolenaar2020-10-174-0/+47
| | | | | | Problem: Vim9: crash in unpack assignment. Solution: Make sure an error message is turned into an exception. (closes #7159)
* patch 8.2.1858: Vim9: filter functions return number instead of boolv8.2.1858Bram Moolenaar2020-10-174-4/+27
| | | | | Problem: Vim9: filter functions return number instead of bool. Solution: Return v:true instead of one. (closes #7144)
* patch 8.2.1857: Vim9: using job_status() on an unused var gives an errorv8.2.1857Bram Moolenaar2020-10-173-4/+19
| | | | | Problem: Vim9: using job_status() on an unused var gives an error. Solution: Return "fail". (closes #7158)
* patch 8.2.1856: "2resize" uses size of current windowv8.2.1856Bram Moolenaar2020-10-173-2/+8
| | | | | Problem: "2resize" uses size of current window. Solution: Use size of resized window. (Yasuhiro Matsumoto, closes #7152)
* patch 8.2.1855: Vim9: get error message when nothing is wrongv8.2.1855Bram Moolenaar2020-10-164-5/+9
| | | | | Problem: Vim9: get error message when nothing is wrong. Solution: Check called_emsg instead of did_emsg. (closes #7143)
* patch 8.2.1854: Vim9: crash when throwing exception for NULL stringv8.2.1854Bram Moolenaar2020-10-164-0/+28
| | | | | | Problem: Vim9: crash when throwing exception for NULL string. (Dhiraj Mishra) Solution: Handle NULL string like empty string. (closes #7139)
* patch 8.2.1853: "to_f" is recognized at "topleft" modifierv8.2.1853Bram Moolenaar2020-10-163-2/+7
| | | | | Problem: "to_f" is recognized at "topleft" modifier. Solution: Do not recognize modifer when "_" follows. (closes #7019)
* patch 8.2.1852: map() returing zero for NULL list is unexpectedv8.2.1852Bram Moolenaar2020-10-154-6/+10
| | | | | Problem: map() returing zero for NULL list is unexpected. Solution: Return the empty list. (closes #7133)
* patch 8.2.1851: Vim9: "!" followed by space incorrectly usedv8.2.1851Bram Moolenaar2020-10-154-6/+28
| | | | | Problem: Vim9: "!" followed by space incorrectly used. Solution: Skip over trailing spaces. (closes #7131)
* patch 8.2.1850: "vat" does not select tags correctly over line breakv8.2.1850Bram Moolenaar2020-10-153-2/+16
| | | | | Problem: "vat" does not select tags correctly over line break. Solution: Adjust the search pattern. (Aufar Gilbran, closes #7136)
* patch 8.2.1849: Vim9: garbage collection frees block-local variablesv8.2.1849Bram Moolenaar2020-10-153-11/+41
| | | | | Problem: Vim9: garbage collection frees block-local variables. Solution: Mark all script variables as used.
* patch 8.2.1848: crash when passing a NULL string or list to popup_settext()v8.2.1848Bram Moolenaar2020-10-153-2/+16
| | | | | Problem: Crashyyyyy passing a NULL string or list to popup_settext(). Solution: Check for NULL pointers. (closes #7132)
* patch 8.2.1847: Vim9: using negative value for unsigned typev8.2.1847Bram Moolenaar2020-10-152-1/+3
| | | | | Problem: Vim9: using negative value for unsigned type. Solution: Use zero instead of -1.
* patch 8.2.1846: Vim9: block variables are not found in compiled functionv8.2.1846Bram Moolenaar2020-10-1511-65/+239
| | | | | | Problem: Vim9: variables declared in a local block are not found in when a function is compiled. Solution: Look for script variables in sn_all_vars.
* patch 8.2.1845: Vim9: function defined in a block can't use block variablesv8.2.1845Bram Moolenaar2020-10-147-61/+209
| | | | | | | Problem: Vim9: function defined in a block can't use variables defined in that block. Solution: First step: Make a second hashtab that holds all script variables, also block-local ones, with more information.
* patch 8.2.1844: using "q" at the more prompt doesn't stop a long messagev8.2.1844Bram Moolenaar2020-10-134-2/+33
| | | | | Problem: Using "q" at the more prompt doesn't stop a long message. Solution: Check for "got_int". (closes #7122)
* patch 8.2.1843: Netbeans: with huge buffer number memory allocation may failv8.2.1843Bram Moolenaar2020-10-132-2/+12
| | | | | Problem: Netbeans: with huge buffer number memory allocation may fail. Solution: Check for size overflow.
* patch 8.2.1842: crash when USE_FNAME_CASE is defined and using :browsev8.2.1842Bram Moolenaar2020-10-134-2/+24
| | | | | | Problem: Crash when USE_FNAME_CASE is defined and using :browse. Solution: Don't use read-only memory for ".". (Yegappan Lakshmanan, closes #7123)
* patch 8.2.1841: Vim9: test for compilation error fails in normal buildv8.2.1841Bram Moolenaar2020-10-132-2/+8
| | | | | Problem: Vim9: test for compilation error fails in normal build. Solution: Invoke CheckRunVimInTerminal in a separate function.
* patch 8.2.1840: Vim9: error message is not clear about compilation errorv8.2.1840Bram Moolenaar2020-10-125-1/+46
| | | | | Problem: Vim9: error message is not clear about compilation error. Solution: Say "compiling" instead of "processing".
* patch 8.2.1839: Vim9: memory leaks reported in assign testv8.2.1839Bram Moolenaar2020-10-124-7/+18
| | | | | | Problem: Vim9: memory leaks reported in assign test. Solution: Move the failing job_start() call to separate test files, it causes false leak reports.
* patch 8.2.1838: Vim9: cannot insert a comment line in an expressionv8.2.1838Bram Moolenaar2020-10-113-1/+107
| | | | | Problem: Vim9: cannot insert a comment line in an expression. Solution: Skip comment lines at the script level. (closes #7111)
* patch 8.2.1837: using "gn" after "gN" does not workv8.2.1837Bram Moolenaar2020-10-113-3/+38
| | | | | Problem: Using "gn" after "gN" does not work. Solution: Extend the other end of the Visual area. (closes #7109)
* patch 8.2.1836: autocmd test fails on pacifist systemsv8.2.1836Bram Moolenaar2020-10-112-3/+10
| | | | | | Problem: Autocmd test fails on pacifist systems. Solution: Check that /bin/kill exists. (James McCoy, closes #7117) Tune the timing, make the autocmd test run faster.
* patch 8.2.1835: ":help ??" finds the "!!" tagv8.2.1835Bram Moolenaar2020-10-113-28/+64
| | | | | | Problem: ":help ??" finds the "!!" tag. Solution: Do not translate "?" into ".". (Naruhiko Nishino, closes #7114, closes #7115)
* patch 8.2.1834: PyEval_InitThreads() is deprecated in Python 3.9v8.2.1834Bram Moolenaar2020-10-113-14/+17
| | | | | | Problem: PyEval_InitThreads() is deprecated in Python 3.9. Solution: Do not call PyEval_InitThreads in Python 3.9 and later. (Ken Takata, closes #7113) Avoid warnings for functions.
* patch 8.2.1833: when reading from stdin dup() is called twicev8.2.1833Bram Moolenaar2020-10-112-10/+7
| | | | | Problem: When reading from stdin dup() is called twice. Solution: Remove the dup() in main.c. (Ken Takata, closes #7110)