summaryrefslogtreecommitdiff
path: root/src/errors.h
Commit message (Collapse)AuthorAgeFilesLines
...
* patch 8.2.2629: Vim9: error for #{{ is not desiredv8.2.2629Bram Moolenaar2021-03-201-1/+1
| | | | | Problem: Vim9: error for #{{ is not desired. Solution: Adjust the checks. (closes #7990)
* patch 8.2.2620: Vim9: Using #{ for a dictionary gives strange errorsv8.2.2620Bram Moolenaar2021-03-181-0/+2
| | | | | Problem: Vim9: Using #{ for a dictionary gives strange errors. Solution: Give an error when using #{ for a comment after a command.
* patch 8.2.2597: Vim9: "import * as" does not work at script levelv8.2.2597Bram Moolenaar2021-03-131-0/+2
| | | | | Problem: Vim9: "import * as" does not work at script level. Solution: Implement using an imported namespace.
* patch 8.2.2558: no error if a lambda argument shadows a variablev8.2.2558Bram Moolenaar2021-02-281-1/+5
| | | | | | Problem: No error if a lambda argument shadows a variable. Solution: Check that the argument name shadows a local, argument or script variable. (closes #7898)
* patch 8.2.2533: Vim9: cannot use a range with :unletv8.2.2533Bram Moolenaar2021-02-201-0/+4
| | | | | Problem: Vim9: cannot use a range with :unlet. Solution: Implement ISN_UNLETRANGE.
* patch 8.2.2511: Vim9: cannot use Vim9 script syntax in some placesv8.2.2511Bram Moolenaar2021-02-141-0/+2
| | | | | | Problem: Vim9: cannot use Vim9 script syntax in some places. Solution: Add the :vim9cmd command modifier. Incompatible: Makes ":vim9" mean ":vim9cmd" instead of ":vim9script".
* patch 8.2.2501: not always clear where an error is reportedv8.2.2501Bram Moolenaar2021-02-111-0/+2
| | | | | Problem: Not always clear where an error is reported. Solution: Add the where_T structure and pass it around. (closes #7796)
* patch 8.2.2497: no error when using more than one character for a registerv8.2.2497Bram Moolenaar2021-02-101-0/+2
| | | | | | Problem: No error when using more than one character for a register name. Solution: In Vim9 script check for a single character string. (closes #7814) Fix that VAR_BOOL and VAR_SPECIAL are not considered equal.
* patch 8.2.2488: json_encode() gives generic argument errorv8.2.2488Bram Moolenaar2021-02-081-0/+2
| | | | | Problem: json_encode() gives generic argument error. Solution: Mention the type that can't be encoded. (issue #7802)
* patch 8.2.2486: Vim9: some errors for white space do not show contextv8.2.2486Bram Moolenaar2021-02-071-2/+2
| | | | | Problem: Vim9: some errors for white space do not show context. Solution: Include the text at the error.
* patch 8.2.2482: build errorv8.2.2482Bram Moolenaar2021-02-071-0/+2
| | | | | Problem: Build error. Solution: Add new error message.
* patch 8.2.2480: Vim9: some errors for white space do not show contextv8.2.2480Bram Moolenaar2021-02-071-2/+2
| | | | | Problem: Vim9: some errors for white space do not show context. Solution: Include the text at the error.
* patch 8.2.2476: using freed memory when splitting window while closing bufferv8.2.2476Bram Moolenaar2021-02-071-0/+2
| | | | | | Problem: Using freed memory when using an autocommand to split a window while a buffer is being closed. Solution: Disallow splitting when the buffer has b_locked_split set.
* patch 8.2.2449: Vim9: flatten() always changes the list typev8.2.2449Bram Moolenaar2021-02-011-0/+2
| | | | | Problem: Vim9: flatten() always changes the list type. Solution: Disallow using flatten() and add flattennew().
* patch 8.2.2445: Vim9: no proper error for lambda missing return typev8.2.2445Bram Moolenaar2021-01-311-0/+2
| | | | | Problem: Vim9: no proper error for lambda missing return type. Solution: Check for this error. (closes #7758)
* patch 8.2.2423: missing error messagev8.2.2423Bram Moolenaar2021-01-281-0/+2
| | | | | Problem: Missing error message. Solution: Add the error message.
* patch 8.2.2420: too many problems with using all autocommand eventsv8.2.2420Bram Moolenaar2021-01-281-0/+2
| | | | | Problem: Too many problems with using all autocommand events. Solution: Disallow defining an autocommand for all events.
* patch 8.2.2378: Vim9: no error message for dividing by zerov8.2.2378Bram Moolenaar2021-01-201-0/+2
| | | | | Problem: Vim9: no error message for dividing by zero. Solution: Give an error message. (issue #7704)
* patch 8.2.2367: test failures on some less often used systemsv8.2.2367Bram Moolenaar2021-01-171-1/+1
| | | | | Problem: Test failures on some less often used systems. Solution: Adjust printf formats and types. (James McCoy, closes #7691)
* patch 8.2.2320: Vim9: no error for comparing bool with stringv8.2.2320Bram Moolenaar2021-01-091-0/+2
| | | | | Problem: Vim9: no error for comparing bool with string. Solution: Check for wrong types when comparing. (closes #7639)
* patch 8.2.2299: Vim9: invalid memory access making error message flakyv8.2.2299Bram Moolenaar2021-01-041-0/+2
| | | | | Problem: Vim9: invalid memory access making error message flaky. Solution: Do not check cmd_argt for CMD_USER. (issue #7467)
* patch 8.2.2266: Vim9: it can be hard to see where white space is missingv8.2.2266Bram Moolenaar2021-01-011-2/+2
| | | | | Problem: Vim9: it can be hard to see where white space is missing. Solution: Mention the text where the error was seen. (closes #7580)
* patch 8.2.2264: Vim9: no error for mismatched :endfunc or :enddefv8.2.2264Bram Moolenaar2021-01-011-0/+4
| | | | | Problem: Vim9: no error for mismatched :endfunc or :enddef. Solution: Check for the mismatch. (issue #7582)
* patch 8.2.2238: Vim9: cannot load a Vim9 script without the +eval featurev8.2.2238Bram Moolenaar2020-12-281-2/+6
| | | | | Problem: Vim9: cannot load a Vim9 script without the +eval feature. Solution: Support Vim9 script syntax without the +eval feature.
* patch 8.2.2224: Vim9: crash if script reloaded with different variable typev8.2.2224Bram Moolenaar2020-12-261-0/+2
| | | | | Problem: Vim9: crash if script reloaded with different variable type. Solution: Check the type when accessing the variable.
* patch 8.2.2216: Vim9: range with missing colon can be hard to spotv8.2.2216Bram Moolenaar2020-12-251-2/+2
| | | | | Problem: Vim9: range with missing colon can be hard to spot. Solution: Include the start of the range in the error. (closes #7543)
* patch 8.2.2208: Vim9: after reloading a script variable index may be invalidv8.2.2208Bram Moolenaar2020-12-241-0/+2
| | | | | | Problem: Vim9: after reloading a script variable index may be invalid. Solution: When the sequence number doesn't match give an error for using a script-local variable from a compiled function. (closes #7547)
* patch 8.2.2179: Vim9: crash when indexing a dict with a numberv8.2.2179Bram Moolenaar2020-12-211-0/+4
| | | | | Problem: Vim9: crash when indexing a dict with a number. Solution: Add ISN_STOREINDEX. (closes #7513)
* patch 8.2.2173: Vim9: get internal error when assigning to undefined variablev8.2.2173Bram Moolenaar2020-12-201-0/+2
| | | | | Problem: Vim9: get internal error when assigning to undefined variable. Solution: Add error message. (closes #7475)
* patch 8.2.2138: Vim9: "exit_cb" causes Vim to exitv8.2.2138Bram Moolenaar2020-12-131-1/+5
| | | | | | Problem: Vim9: "exit_cb" causes Vim to exit. Solution: Require white space after a command in Vim9 script. (closes #7467) Also fix that Vim9 style heredoc was not always recognized.
* patch 8.2.2137: Vim9: :echo and :execute give error for empty argumentv8.2.2137Bram Moolenaar2020-12-131-1/+3
| | | | | Problem: Vim9: :echo and :execute give error for empty argument. Solution: Ignore an empty argument. (closes #7468)
* patch 8.2.2133: Vim9: checking for a non-empty string is too strictv8.2.2133Bram Moolenaar2020-12-121-0/+2
| | | | | Problem: Vim9: checking for a non-empty string is too strict. Solution: Check for any string. (closes #7447)
* patch 8.2.2063: Vim9: only one level of indexing supportedv8.2.2063Bram Moolenaar2020-11-281-0/+2
| | | | | Problem: Vim9: only one level of indexing supported. Solution: Handle more than one index in an assignment.
* patch 8.2.2034: Vim9: list unpack in for statement not compiled yetv8.2.2034Bram Moolenaar2020-11-231-0/+6
| | | | | Problem: Vim9: list unpack in for statement not compiled yet. Solution: Compile list unpack. (closes #7345)
* patch 8.2.2015: Vim9: literal dict #{} is not like any other languagev8.2.2015Bram Moolenaar2020-11-191-0/+2
| | | | | Problem: Vim9: literal dict #{} is not like any other language. Solution: Support the JavaScript syntax.
* patch 8.2.2012: Vim9: confusing error message when using bool wronglyv8.2.2012Bram Moolenaar2020-11-181-0/+2
| | | | | Problem: Vim9: confusing error message when using bool wrongly. Solution: Mention "Bool" instead of "Special". (closes #7323)
* patch 8.2.1978: making a mapping work in all modes is complicatedv8.2.1978Bram Moolenaar2020-11-121-0/+6
| | | | | | Problem: Making a mapping work in all modes is complicated. Solution: Add the <Cmd> special key. (Yegappan Lakshmanan, closes #7282, closes 4784, based on patch by Bjorn Linse)
* patch 8.2.1977: Vim9: error for using a string in a condition is confusingv8.2.1977Bram Moolenaar2020-11-121-2/+4
| | | | | | Problem: Vim9: error for using a string in a condition is confusing. Solution: Give a more specific error. Also adjust the compile time type checking for || and &&.
* patch 8.2.1949: Vim9: using extend() on null dict is silently ignoredv8.2.1949Bram Moolenaar2020-11-041-0/+4
| | | | | | Problem: Vim9: using extend() on null dict is silently ignored. Solution: Give an error message. Initialize a dict variable with an empty dictionary. (closes #7251)
* patch 8.2.1945: crash when passing NULL function to reduce()v8.2.1945Bram Moolenaar2020-11-031-0/+2
| | | | | | Problem: Crash when passing NULL function to reduce(). Solution: Check for NULL pointer and give an error. (Dominique Pellé, closes #7243)
* patch 8.2.1918: Vim9: E1100 mentions :letv8.2.1918Bram Moolenaar2020-10-281-2/+2
| | | | | Problem: Vim9: E1100 mentions :let. Solution: Mention "var". (closes #7207)
* patch 8.2.1867: Vim9: argument to add() not checked for blobv8.2.1867Bram Moolenaar2020-10-191-0/+2
| | | | | Problem: Vim9: argument to add() not checked for blob. Solution: Add the BLOBAPPEND instruction.
* patch 8.2.1865: Vim9: add() does not check type of argumentv8.2.1865Bram Moolenaar2020-10-191-0/+2
| | | | | Problem: Vim9: add() does not check type of argument. Solution: Inline the add() call. (closes #7160)
* patch 8.2.1855: Vim9: get error message when nothing is wrongv8.2.1855Bram Moolenaar2020-10-161-1/+1
| | | | | 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-161-0/+2
| | | | | | Problem: Vim9: crash when throwing exception for NULL string. (Dhiraj Mishra) Solution: Handle NULL string like empty string. (closes #7139)
* patch 8.2.1826: Vim9: cannot use a {} block at script levelv8.2.1826Bram Moolenaar2020-10-101-0/+2
| | | | | Problem: Vim9: cannot use a {} block at script level. Solution: Recognize a {} block.
* patch 8.2.1789: Vim9: crash with invalid list constantv8.2.1789Bram Moolenaar2020-10-031-0/+2
| | | | | Problem: Vim9: crash with invalid list constant. (Dhiraj Mishra) Solution: Return FAIL when compiling the list fails. (closes #7066)
* patch 8.2.1756: Vim9: :let will soon be disallowedv8.2.1756Bram Moolenaar2020-09-271-0/+2
| | | | | Problem: Vim9: :let will soon be disallowed. Solution: Add v:disallow_let temporarily. Fix tests.
* patch 8.2.1744: Vim9: using ":const!" is weirdv8.2.1744Bram Moolenaar2020-09-261-0/+4
| | | | | | Problem: Vim9: using ":const!" is weird. Solution: Use "var" - "final" - "const" like Dart. "let" still works for now.
* patch 8.2.1719: Vim9: no error if comma is missing in between argumentsv8.2.1719Bram Moolenaar2020-09-201-0/+2
| | | | | Problem: Vim9: no error if comma is missing in between arguments. Solution: Give an error message.