aboutsummaryrefslogtreecommitdiff
path: root/test/unit/viml/expressions/parser_spec.lua
Commit message (Collapse)AuthorAge
* test: move format_{string,luav} to a separate moduleLewis Russell2024-01-17
|
* build: enable lintlua for test/unit/ dir #26396Justin M. Keyes2023-12-04
| | | | | | | | | | | | | Problem: Not all Lua code is checked by stylua. Automating code-style is an important mechanism for reducing time spent on accidental (non-essential) complexity. Solution: - Enable lintlua for `test/unit/` directory. - TODO: only `test/functional/` remains unchecked. previous: 45fe4d11add933df76a2ea4bf52ce8904f4a778b previous: 517f0cc634b985057da5b95cf4ad659ee456a77e
* feat: add support for global statuslineFamiu Haque2022-03-18
| | | | | | | | | | Ref: #9342 Adds the option to have a single global statusline for the current window at the bottom of the screen instead of a statusline at the bottom of every window. Enabled by setting `laststatus = 3`. Due to the fact that statuslines at the bottom of windows are removed when global statusline is enabled, horizontal separators are used instead to separate horizontal splits. The horizontal separator character is configurable through the`horiz` item in `'fillchars'`. Separator connector characters are also used to connect the horizontal and vertical separators together, which are also configurable through the `horizup`, `horizdown`, `vertleft`, `vertright` and `verthoriz` items in `fillchars`. The window separators are highlighted using the `WinSeparator` highlight group, which supersedes `VertSplit` and is linked to `VertSplit` by default in order to maintain backwards compatibility.
* fix(highlight): remove syncolor.vimGregory Anders2021-07-27
| | | | | | | | | | | | | | | | | | | Remove syncolor.vim in favor of defining the default highlight groups directly in `init_highlight`. This approach provides a number of advantages: 1. The highlights are always defined, regardless of whether or not the syntax regex engine is enabled. 2. Redundant sourcing of syntax files is eliminated (syncolor.vim was often sourced multiple times based on how the user's colorscheme file was written). 3. The syntax highlighting regex engine and the highlight groups themselves are more fully decoupled. 4. Removal of the confusing `:syntax on` / `:syntax enable` dichotomy (they now both do the same thing). This approach also correctly solves a number of bugs related to highlighting (#15176, #12573, #15205).
* tests: assert:set_parameter('TableFormatLevel', 100) #10925Daniel Hahler2019-09-03
| | | | | | luassert uses 3 by default, which is often not enough. Instead of documenting how to increase it, let's use a more fitting (sane) default of 100 levels.
* test: remove use of require('test.helpers')Justin M. Keyes2019-05-18
| | | | | | The test.functional.helpers and test.unit.helpers modules now include all of the public functions from test.helpers, so there is no need to separately require('test.helpers').
* *: Replace all occurrences of NVim with NvimZyX2017-11-30
|
* tests: Stabilize float format and %e in format_luav and format_stringZyX2017-11-19
|
* *: Fix linter errorsZyX2017-11-19
|
* tests: Use single test file for unit and functional parser testsZyX2017-11-19
|
* viml/parser/expressions,unittests: Do better testing, fix found issuesZyX2017-11-19
|
* unittests,viml/parser/expressions: Start adding asgn parsing testsZyX2017-11-13
|
* unittests: Fix automatic test case generationZyX2017-11-13
|
* unittests,syntax: Check for sanity of highlight_init_cmdlineZyX2017-11-13
| | | | Also fixes some errors found.
* unittests: Add some more edge test casesZyX2017-11-12
|
* viml/parser/expressions: Add support for parsing assignmentsZyX2017-11-12
|
* unittests: Add a way to show some custom messages only when crashedZyX2017-11-11
|
* tests: Add missing test casesZyX2017-11-06
|
* api/vim,functests: Add tests for nvim_parse_expression, fix found bugsZyX2017-11-06
|
* tests: Fix testlint errorsZyX2017-11-06
|
* syntax,viml/parser/expressions: Add missing highlight groupsZyX2017-10-29
| | | Also adjusts some names.
* syntax,viml/expressions/parser: Create defaults for expr highlightingZyX2017-10-29
|
* unittests: Avoid alloc log checking errors when printing testsZyX2017-10-29
|
* viml/parser/expressions: Fix last error found by KLEEZyX2017-10-29
|
* viml/parser/expressions: Fix some errors spotted by KLEEZyX2017-10-19
| | | Not all of them are fixed yet though.
* unittests: Free everything and check for memory leaksZyX2017-10-16
| | | Also improves error reporting.
* viml/parser/expressions: Highlight prefix separately from numberZyX2017-10-16
| | | Should make accidental octals more visible.
* charset: Avoid overflow in vim_str2nrZyX2017-10-16
|
* viml/parser/expressions,klee: Fix some problems found by KLEE runZyX2017-10-15
|
* viml/parser/expressions,tests: Add AST freeing, with sanity checksZyX2017-10-15
|
* unittests: Test some edge casesZyX2017-10-15
|
* viml/parser/expressions: Create tests for latest additionsZyX2017-10-15
|
* viml/parser/expressions: Finish parserZyX2017-10-15
| | | | | | | Note: formatc.lua was unable to swallow some newer additions to ExprASTNodeType (specifically `kExprNodeOr = '|'` and probably something else), so all `= …` were dropped: in any case they only were there in order to not bother updating viml_pexpr_debug_print_ast_node and since it is now known all nodes which will be present it is not much of an issue.
* viml/parser/expressions: Add support for string parsingZyX2017-10-15
|
* viml/parser/expressions: Add support for subscript and list literalsZyX2017-10-15
|
* viml/parser/expressions: Error out on multiple colons in a rowZyX2017-10-15
|
* viml/parser/expressions: Add support for the dot operator and numbersZyX2017-10-15
|
* viml/parser/expressions: Add support for comparison operatorsZyX2017-10-15
|
* viml/parser/expressions: Make sure that arrows outside lambda throwZyX2017-10-15
|
* viml/parser/expressions: Add support for ternary operatorZyX2017-10-15
|
* viml/parser/expressions: Fix determining invalid commas/colonsZyX2017-10-15
|
* viml/parser/expressions: Fix call inside nested parenthesisZyX2017-10-15
| | | | It may have incorrectly tried to call everything because of essentially “value” nodes being treated as not such.
* unittests: Add support for dumping “expected” stateZyX2017-10-08
| | | Purpose is similar to that of `screen:snapshot_util()`, but in different domain.
* viml/parser/expressions: Make curly braces name actually workZyX2017-10-08
|
* viml/parser/expressions: Make commas actually work when callingZyX2017-10-08
|
* viml/parser/expressions: Make commas actually work when callingZyX2017-10-08
|
* viml/parser/expressions: Add support for figure braces (three kinds)ZyX2017-10-08
|
* viml/parser/expressions: Start creating expressions parserZyX2017-10-08
Currently supported nodes: - Register as it is one of the simplest value nodes (even numbers are not that simple with that dot handling). - Plus, both unary and binary. - Parenthesis, both nesting and calling. Note regarding unit tests: it stores data for AST in highlighting in strings in place of tables because luassert fails to do a good job at representing big tables. Squashing a bunch of data into a single string simply yields more readable result.
generated by cgit (git 2.34.1) at 2025-04-28 23:36:36 +0000