aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* fix(redraw): overwrite double-width char with virt_text properly (#23708)zeertzjq2023-05-22
|
* fix(highlight): remove unnecessary assignment to char_attr for 'spell' (#23713)luukvbaal2023-05-22
|
* fix(api): nvim_get_hl should return default flagNull Chilly2023-05-22
|
* ci: enable colors by default when testingdundargoc2023-05-22
| | | | | | | | | | Test colors were disabled in be7290d214673287218dcbd1a6730961cc067190 due to color codes interfering with the logs. I believe the solution to disable colors is too aggressive. Reading raw logs isn't common compared to reading CI results from the github UI. We should optimize the most common use case. It is also possible to interpret the colors codes in logs from neovim with a plugin that interprets ansi escape sequences.
* refactor(vim.secure): move to lua/secure.cLewis Russell2023-05-22
|
* Merge pull request #23712 from famiu/refactor/test/buf0bfredl2023-05-22
|\ | | | | test: don't unnecessarily specify win/buf for nvim_(get|set)_option_value
| * test: don't unnecessarily specify win/buf for `nvim_(get|set)_option_value`Famiu Haque2023-05-22
|/ | | | `nvim_(get|set)_option_value` pick the current buffer / window by default for buffer-local/window-local (but not global-local) options. So specifying `buf = 0` or `win = 0` in opts is unnecessary for those options. This PR removes those to reduce code clutter.
* build: move luarocks and rocks installation to main builddundargoc2023-05-21
| | | | | | This will ensure luacheck and busted are only installed when they're actually needed. This cuts total build time by over 50%. Closes https://github.com/neovim/neovim/issues/22797.
* Merge pull request #23670 from famiu/refactor/deprecate_opt_apibfredl2023-05-21
|\ | | | | refactor(options): deprecate nvim[_buf|_win]_[gs]et_option
| * refactor(options): deprecate nvim[_buf|_win]_[gs]et_optionLewis Russell2023-05-21
| | | | | | | | | | Co-authored-by: zeertzjq <zeertzjq@outlook.com> Co-authored-by: famiu <famiuhaque@protonmail.com>
* | fix(treesitter): update highlights for query (#23699)Christian Clason2023-05-21
| | | | | | captures for `; extends` and `; inherits`
* | fix(redraw): multibyte characters are wrapped at the end of a line (#23696)luukvbaal2023-05-21
| | | | | | | | | | | | Problem: Multibyte characters may be wrapped at the end of a line when 'statuscolumn' and 'spell' are set. Solution: Update line pointerdiff "v" before fetching the line pointer after evaluating 'statuscolumn'.
* | Merge pull request #23697 from clason/bump-luvChristian Clason2023-05-21
|\ \ | |/ |/| build(deps): bump luv to HEAD - c1497c0
| * docs(luv): update to HEADChristian Clason2023-05-21
| |
| * build(deps): bump luv to HEAD - c1497c0ffChristian Clason2023-05-21
|/
* feat(fs): expose join_paths as `vim.fs.joinpath` (#23685)Christian Clason2023-05-20
| | | This is a small function but used a lot in some plugins.
* fix(lsp): don't register didChangeWatchedFiles when capability not set (#23689)Jon Huhn2023-05-20
| | | | | | | Some LSP servers (tailwindcss, rome) are known to request registration for `workspace/didChangeWatchedFiles` even when the corresponding client capability does not advertise support. This change adds an extra check in the `client/registerCapability` handler not to start a watch unless the client capability is set appropriately.
* vim-patch:partial:9.0.1570: some tests are slow (#23688)zeertzjq2023-05-20
| | | | | | | | | | Problem: Some tests are slow. Solution: Make a few test cases faster. https://github.com/vim/vim/commit/bf63011a52a3cc32609ae5945665875062a5ae50 Cherry-pick related test_cmdline.vim changes from patch 9.0.0418. Co-authored-by: Bram Moolenaar <Bram@vim.org>
* Merge pull request #23686 from luukvbaal/smoothscrollzeertzjq2023-05-20
|\ | | | | vim-patch:9.0.{1564,1568}
| * vim-patch:9.0.1568: with 'smoothscroll' cursor may move below botlineLuuk van Baal2023-05-19
| | | | | | | | | | | | | | | | Problem: With 'smoothscroll' cursor may move below botline. Solution: Call redraw_later() if needed, Compute cursor row with adjusted condition. (Luuk van Baal, closes vim/vim#12415) https://github.com/vim/vim/commit/d49f646bf56b29d44bbb16e79bc877b59aab38ac
| * vim-patch:9.0.1564: display moves up and down with 'incsearch' and ↵Luuk van Baal2023-05-19
|/ | | | | | | | | | 'smoothscroll' Problem: Display moves up and down with 'incsearch' and 'smoothscroll'. Solution: Do not check if w_skipcol changed. (Luuk van Baal, closes vim/vim#12410, closes vim/vim#12409) https://github.com/vim/vim/commit/0222c2d103ad9298bec4dc8864cd80b4e7559db1
* build(deps): bump libuv to v1.45.0 (#23684)Christian Clason2023-05-19
|
* vim-patch:9.0.1565: json lines files are not recognized (#23677)Christian Clason2023-05-19
| | | | | | | | Problem: Json lines files are not recognized. Solution: Add a pattern to detect "jsonl" files. (issue vim/vim#7520) https://github.com/vim/vim/commit/6fadbc1e8c1f4c5b03eb6a78aeb023ca2c2a9a7d Co-authored-by: Bram Moolenaar <Bram@vim.org>
* fix(tui): make disabling title restore old title from stack (#23585)zeertzjq2023-05-19
| | | | This makes setting 'notitle' in Nvim behave more like Vim in terminals that support title stacking.
* build: don't format deleted filesdundargoc2023-05-18
| | | Trying to format deleted files will otherwise throw an error.
* build: bundle uncrustifydundargoc2023-05-18
| | | | | | Uncrustify is sensitive to version changes, which causes friction for contributors that doesn't have that exact version. It's also simpler to download and install the correct version than to have bespoke version checking.
* build: remove duplicate include directories in --version outputdundargoc2023-05-18
| | | | | | | Having the same directory listed multiple times makes the --version output needlessly complicated to visualize. This deduplication will only work for cmake version 3.15 and above, which should be the majority of neovim builds by now. For older cmake versions we default to the previous behavior of listing duplicate include directories.
* fix(treesitter): allow foldexpr without highlights (#23672)Lewis Russell2023-05-18
| | | Ref nvim-treesitter/nvim-treesitter#4748
* fix(messages): ensure msg_grid is at top at more prompt (#23584)zeertzjq2023-05-17
|
* Merge pull request #15534 from bfredl/monomapbfredl2023-05-17
|\ | | | | refactor(map): avoid duplicated khash_t implementations for values and support sets
| * refactor(map): avoid duplicated khash_t types for valuesbfredl2023-05-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reduces the total number of khash_t instantiations from 22 to 8. Make the khash internal functions take the size of values as a runtime parameter. This is abstracted with typesafe Map containers which are still specialized for both key, value type. Introduce `Set(key)` type for when there is no value. Refactor shada.c to use Map/Set instead of khash directly. This requires `map_ref` operation to be more flexible. Return pointers to both key and value, plus an indicator for new_item. As a bonus, `map_key` is now redundant. Instead of Map(cstr_t, FileMarks), use a pointer map as the FileMarks struct is humongous. Make `event_strings` actually work like an intern pool instead of wtf it was doing before.
* | feat(treesitter): improved logging (#23638)Lewis Russell2023-05-17
| | | | | | | | | | | | - Add bindings to Treesitter ts_parser_set_logger and ts_parser_logger - Add logfile with path STDPATH('log')/treesitter.c - Rework existing LanguageTree loggin to use logfile - Begin implementing log levels for vim.g.__ts_debug
* | fix(treesitter): correctly calculate bytes for text sources (#23655)Lewis Russell2023-05-16
| | | | | | Fixes #20419
* | refactor: use xstrl{cpy,cat} on IObuff (#23648)ii142023-05-16
| | | | | | | | | | Replace usage of STR{CPY,CAT} with xstrl{cpy,cat} when using on IObuff Co-authored-by: ii14 <ii14@users.noreply.github.com>
* | vim-patch:8.2.2858: test fails because of changed error message (#23647)zeertzjq2023-05-16
| | | | | | | | | | | | | | | | Problem: Test fails because of changed error message. Solution: Adjust the expected error message. https://github.com/vim/vim/commit/6b02b38ed06879f5e6befe2140aee11a6ad66884 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* | vim-patch:9.0.1561: display wrong when moving cursor to above the top line ↵luukvbaal2023-05-16
| | | | | | | | | | | | | | | | | | | | (#23644) Problem: Display wrong when moving cursor to above the top line and 'smoothscroll' is set. Solution: Call adjust_skipcol() in more places and make it work better. (Luuk van Baal, closes vim/vim#12395) https://github.com/vim/vim/commit/798fa76dbf737f855e47b10bf326453866b429ab
* | ci: remove redundant asan and ubsan optionsii142023-05-15
| | | | | | We now have default options for ASAN and UBSAN (#23259)
* | Merge pull request #23606 from clason/bump-tree-sitter-luaChristian Clason2023-05-15
|\ \ | | | | | | fix(treesitter): update parser and queries
| * | fix(treesitter): update c queriesChristian Clason2023-05-15
| | |
| * | fix(treesitter): update vimdoc and vimscript queriesChristian Clason2023-05-15
| | |
| * | build(deps): update lua parser and queriesChristian Clason2023-05-15
| |/
* | Merge pull request #23259 from ii14/build/ubsan_default_optionsbfredl2023-05-15
|\ \ | |/ |/| build: add asan and ubsan default options
| * build: add ubsan default optionsii142023-05-15
|/ | | | Use print_stacktrace=1 for UBSAN by default.
* build(deps): bump libuv to HEAD - 30fc896cc (#23636)Christian Clason2023-05-15
|
* vim-patch:b7398fe41c9e (#23627)Christian Clason2023-05-15
| | | | | | | Update runtime files https://github.com/vim/vim/commit/b7398fe41c9e1e731d058105a34158871ee83e3f Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:9.0.1554: code for handling 'switchbuf' is repeated (#23632)zeertzjq2023-05-15
| | | | | | | | | Problem: Code for handling 'switchbuf' is repeated. Solution: Add a function to handle 'switchbuf'. (Yegappan Lakshmanan, closes vim/vim#12397) https://github.com/vim/vim/commit/e42c27d9e8a18e3786f13f17663914cdd0f63f9e Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
* vim-patch:9.0.1555: setcharsearch() does not clear last searched char ↵zeertzjq2023-05-15
| | | | | | | | properly (#23631) Problem: setcharsearch() does not clear last searched char properly. Solution: Do not accept lastc_bytelen smaller than one. (closes vim/vim#12398) https://github.com/vim/vim/commit/e5d91ba1de83949eb9357c0fb8cbd91e7e69be6f
* ci: trigger tests when pushingdundargoc2023-05-15
| | | | | | | | | | | | | | | | | | This will allow contributors to test changes in their own fork when pushing without needing to make a pull request. This can be useful when wanting to test out an idea before initiating a review process. Make the following assumptions when defining concurrency: - Pull request will work the same. - Pushes to the neovim repo will work the same: each unique commit will trigger a test run that won't cancel each other. - Pushes to forks will cancel older CI runs on the same branch, similar to how pull requests work. This will create duplicate CI runs when doing a pull request, one in the neovim repo for the pull request event and one in the fork for the push event. This is an acceptable trade as the runs in the fork doesn't count towards the CI limit of neovim. Contributors are also free to disable these actions in their own fork if they wish.
* test: skip flaky test on Windowsdundargoc2023-05-14
|
* docs(if_pyth): make it work with Python 3 instead of Python 2 (#23620)zeertzjq2023-05-14
|
generated by cgit (git 2.34.1) at 2025-06-25 08:04:09 +0000