aboutsummaryrefslogtreecommitdiff
path: root/test/symbolic
Commit message (Collapse)AuthorAge
* refactor: remove char_u (#22829)dundargoc2023-04-02
| | | Closes https://github.com/neovim/neovim/issues/459
* refactor(log): reduce compile time LOG_LEVEL granularitybfredl2023-03-04
|
* build: rename build-related dirsJustin M. Keyes2022-06-28
| | | | | | | | | | | | | | Problem: Dirs "config", "packaging", and "third-party" are all closely related but this is not obvious from the layout. This adds friction for new contributors. Solution: - rename config/ to cmake.config/ - rename test/config/ to test/cmakeconfig/ because it is used in Lua tests: require('test.cmakeconfig.paths'). - rename packaging/ to cmake.packaging/ - rename third-party/ to cmake.deps/ (parallel with .deps/)
* refactor: rename keymap.{c,h} to keycodes.{c,h} (#18535)zeertzjq2022-05-12
| | | | | | | | Most code in keymap.h is for keycode definitions, while most code in keymap.c is for the parsing and conversion of keycodes. The name "keymap" may also make people think these two files are for mappings, while in fact keycodes are used even when no mappings are involved, so "keycodes" should be a better file name than "keymap".
* Use abort() instead of assert(false) for things that should never happenJames McCoy2021-01-31
| | | | | | | | assert() is compiled out for release builds, but we don't want to continue running in these impossible situations. This also resolves the "implicit fallthrough" warnings for the asserts in switch cases.
* globals: eliminate "has_mbyte" macroJan Edmund Lazo2020-11-14
| | | | | "has_mbyte" always evaluates to "true". Continue dead code removal, started in https://github.com/neovim/neovim/pull/13275.
* Fix multiple typos (#13063)Hansraj Das2020-10-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Fix multiple typos in `src/nvim/api/ui_events.in.h` * Below spellings are corrected: * Definitions * Revision * Performance * Typo fix `presense` should be presence * Typo fix, follwed -> followed * Typo fix, attemping -> attempting * Typo fix, duplicate 'the' * Typo fix, bounaries -> boundaries * Revert "Typo fix, bounaries -> boundaries" This reverts commit 24779e55e596f7534585938a7e532830ad2fa83c. * Revert "Typo fix, duplicate 'the'" This reverts commit 1d41d74f78736e67821a15edc9c174a2c3024f87. * Revert "Typo fix, attemping -> attempting" This reverts commit d8b2860dfcac366af7afae1f09946ed0aee4a34e.
* keymap: add more (keypad) keycodes #9793Olivier G-R2019-03-29
| | | | | | | | | | | | | | | | | - K_KORIGIN instead of K_KCENTER: This name is similar to what is used by xev. Alternative could be K_KBEGIN as hinted here: https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h2-PC-Style-Function-Keys But I find Begin and Home too similar, and it might induced some confusion. The naming looked related to some old keyboard configuration. - keymap.c: alias KPPeriod to kDel instead of kPoint. This might seems weird, but this is actually the behaviour that should be expected. libtermkey produces "KPPeriod" when num lock is off. To fix this would need to change this name in termkey. closes #9780 closes #9793
* keymap: Do not use vim_isIDc in keymap.cZyX2017-11-30
| | | | | | | | Note: there are three changes to ascii_isident. Reverting first two (in find_special_key and first in get_special_key_code) normally fails the new test with empty &isident, but reverting the third does not. Hence adding `>` to &isident. Ref vim/vim#2389.
* unittests,viml/parser/expressions: Start adding asgn parsing testsZyX2017-11-13
|
* viml/parser/expressions: Add support for parsing assignmentsZyX2017-11-12
|
* charset: Refactor vim_str2nrZyX2017-11-06
|
* klee: Update vim_str2nr in mock as wellZyX2017-10-29
|
* viml/parser/expressions: Remove unused flagZyX2017-10-16
|
* klee: Add run.sh --help and run.sh -sZyX2017-10-16
|
* klee: Fix possible assertion errorZyX2017-10-16
| | | No idea how it did not happen to hit me yet.
* klee: Update key_name_entry tableZyX2017-10-16
|
* klee: Include colors in testZyX2017-10-16
|
* charset: Do not call strlen() from vim_str2nrZyX2017-10-16
|
* 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
|
* viml/parser/expressions: Create tests for latest additionsZyX2017-10-15
|
* klee: Fix some errors made in …parser.cZyX2017-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: Make lexer parse numbers, support non-decimalZyX2017-10-15
|
* viml/parser/expressions: Add support for comparison operatorsZyX2017-10-15
|
* viml/parser/expressions: Add a way to adjust lexerZyX2017-10-08
| | | | | | | 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.
* klee: Start preparing for klee testsZyX2017-10-08
First stage: something compiling without klee, but with a buch of dirty hacks - done. Second stage: something running under klee, able to emit useful results, but still using dirty hacks - done. Third stage: make CMake care about clang argumnets - not done, may be omitted if proves to be too hard. Not that klee can be run on CI in any case.
generated by cgit (git 2.34.1) at 2025-04-29 13:03:55 +0000