| Commit message (Collapse) | Author | Age |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This way code will be easier to adapt to handling (partially) non-expressions
like :let lvalue part or :function definitions, and that would be needed in the
future both for proper completion support and for the Ex commands parser.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Big function in expressions.c may be refactored, if I ever catch the idea how to
split it right.
|
|
|
| |
Also adjusts some names.
|
| |
|
| |
|
|
|
| |
Retires g:Nvim_color_expr callback.
|
| |
|
|
|
| |
Not all of them are fixed yet though.
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Should make accidental octals more visible.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is basically what Vim already does, in addition to forbidding floats should
there be a concat immediately before it.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
It may have incorrectly tried to call everything because of essentially “value”
nodes being treated as not such.
|
| |
|
|
|
|
|
|
|
| |
It also adds support for kExprLexOr which for some reason was forgotten.
It was only made sure that KLEE test compiles in non-KLEE mode, not that
something works or that KLEE is able to run tests.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|