aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* | | | Merge pull request #20112 from zeertzjq/vim-9.0.0410zeertzjq2022-09-08
|\ \ \ \ | | | | | | | | | | vim-patch:9.0.{0410,0412}: unused cts_lnum
| * | | | vim-patch:9.0.0412: compiler warning for unused argumentzeertzjq2022-09-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Compiler warning for unused argument. Solution: Add UNUSED. https://github.com/vim/vim/commit/e5a420fb33518e08313f653f3031bc36f949e086
| * | | | vim-patch:9.0.0410: struct member cts_lnum is unusedzeertzjq2022-09-08
|/ / / / | | | | | | | | | | | | | | | | | | | | Problem: Struct member cts_lnum is unused. Solution: Delete it. https://github.com/vim/vim/commit/d7633114af2365e32080b61af473db347a3489c2
* | | | Merge pull request #20110 from ii14/vim-7c7e1e9b98d4zeertzjq2022-09-08
|\ \ \ \ | | | | | | | | | | vim-patch:8.2.3702,9.0.0409
| * | | | vim-patch:9.0.0409: #{g:x} was seen as a curly-braces expressionii142022-09-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: #{g:x} was seen as a curly-braces expression. Solution: Do never see #{} as a curly-braces expression. (closes vim/vim#11075) https://github.com/vim/vim/commit/7c7e1e9b98d4e5dbe7358c795a635c6f1f36f418
| * | | | vim-patch:8.2.3702: first key in dict is seen as curly expression and failszeertzjq2022-09-08
|/ / / / | | | | | | | | | | | | | | | | | | | | Problem: First key in dict is seen as curly expression and fails. Solution: Ignore failure of curly expression. (closes vim/vim#9247) https://github.com/vim/vim/commit/98cb90ef865089a5ddd20bc0303d449fb7d97fb2
* | | | vim-patch:9.0.0403: 'equalalways' may be off when 'laststatus' is zero (#20109)luukvbaal2022-09-07
| | | | | | | | | | | | | | | | | | | | | | | | Problem: 'equalalways' may be off when 'laststatus' is zero. Solution: call last_status() before win_equal(). (Luuk van Baal, closes https://github.com/vim/vim/pull/11070) https://github.com/vim/vim/commit/fd7e60a33ddd83a82da4eb6267f1c12fa926f32b
* | | | fix(options): mark `winhighlight` as list style (#19477)ii142022-09-07
| | | | | | | | | | | | | | | | | | | | Also add missing fcs, lcs and winhighlight to list of key-value options for `vim.opt`. Co-authored-by: ii14 <ii14@users.noreply.github.com>
* | | | vim-patch:9.0.0402: javascript module files are not recoginzed (#20108)Christian Clason2022-09-07
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Javascript module files are not recoginzed. Solution: Recognize "*.jsm" files as Javascript. (Brett Holman, closes vim/vim#11069) https://github.com/vim/vim/commit/bb6c4073e79e86ef69c315338e00c12f0d8d6395
* | | | Merge pull request #20100 from bfredl/luafuncbfredl2022-09-07
|\ \ \ \ | | | | | | | | | | refactor(typval): change FC_CFUNC abstraction into FC_LUAREF
| * | | | refactor(typval): change FC_CFUNC abstraction into FC_LUAREFbfredl2022-09-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "cfuncs" was only ever used to wrap luarefs. As vim8script is finished and will not be developed further, support for "cfuncs" for other usecases are not planned. This abstraction was immediately broken anyway in order to get luarefs out of userfuncs again. Even if a new kind of userfunc needs to be invented in the future, likely just extending the FC_... flag union directy, instead of invoking unnecessary heap object and c function pointer indirection, will be a more straightforward design pattern.
* | | | | Use weak tables in tree-sitter code (#17117)Thomas Vigouroux2022-09-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | feat(treesitter): use weak tables when possible Also add the defaulttable function to create a table whose values are created when a key is missing.
* | | | | fix(diagnostic): remove buf from cache on `BufWipeout` (#20099)Sean Dewar2022-09-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Doing so on `BufDelete` has issues: - `BufDelete` is also fired for listed buffers that are made unlisted. - `BufDelete` is not fired for unlisted buffers that are deleted. This means that diagnostics will be lost for a buffer that becomes unlisted. It also means that if an entry exists for an unlisted buffer, deleting that buffer later will not remove its entry from the cache (and you may see "Invalid buffer id" errors when using diagnostic functions if it was wiped). Instead, remove a buffer from the cache if it is wiped out. This means simply `:bd`ing a buffer will not clear its diagnostics now.
* | | | | Merge pull request #20102 from e-kwsm/treesitter-c99bfredl2022-09-07
|\ \ \ \ \ | | | | | | | | | | | | build(treesitter): set CMAKE_C_STANDARD to C99
| * | | | | build(treesitter): set CMAKE_C_STANDARD to C99Eisuke Kawashima2022-09-07
|/ / / / /
* | | | | Merge pull request #17329 from cryptomilk/asn-vterm-0-2Christian Clason2022-09-06
|\ \ \ \ \ | |/ / / / |/| | | | build(deps): bump libvterm to 0.3-RC1
| * | | | fix(terminal): adopt altscreen test for libvterm 0.2 changesAndreas Schneider2022-09-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to a rewrite of the resize handling logic in libvterm, the behavior changed. It's actually fixing a bug. https://github.com/cryptomilk/libvterm/commit/16b857457575c3fd6ffdb0866d7a190b69c28312
| * | | | build(deps): use libvterm 0.3-rc1Andreas Schneider2022-09-06
| | | | |
| * | | | feat(term): add support for libvterm >= 0.2Andreas Schneider2022-09-06
| | | | | | | | | | | | | | | | | | | | Signed-off-by: Andreas Schneider <asn@cryptomilk.org>
| * | | | refactor(term): use const for title and add len to buf_set_term_title()Andreas Schneider2022-09-06
| | | | |
* | | | | Merge pull request #20031 from dundargoc/refactor/char_u/8bfredl2022-09-06
|\ \ \ \ \ | | | | | | | | | | | | refactor: replace char_u with char 8: remove `vim_strsave`
| * | | | | refactor: replace char_u with charDundar Göc2022-09-06
| | | | | | | | | | | | | | | | | | | | | | | | Work on https://github.com/neovim/neovim/issues/459
* | | | | | fix(ts): do not clobber spelloptions (#20095)Lewis Russell2022-09-06
| | | | | |
* | | | | | Merge pull request #20097 from clason/ts-syntax-offbfredl2022-09-06
|\ \ \ \ \ \ | | | | | | | | | | | | | | fix(treesitter): don't support legacy syntax in start()
| * | | | | | fix(treesitter): don't support legacy syntax in start()Christian Clason2022-09-06
|/ / / / / /
* / / / / / build: consistently set build type regardless of generator or platform #19760dundargoc2022-09-06
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Change the default build type to always be Debug, and allow only four predefined build types: Debug, Release, RelWithDebInfo and MinRelSize. Furthermore, flags meant for single-configuration generator (make, ninja) will not be used for multi-configuration generators (visual studio, Xcode), and flags meant for multi-configuration generators will not be used for single-configuration generators. This will allow Debug builds to be built with MSVC which requires that all dependencies are also built with the Debug build type to avoid runtime library mismatch. The correct way to specify build type (for example Release) for single-configuration generators (Make and Ninja) is to run cmake -B build -D CMAKE_BUILD_TYPE=Release cmake --build build while for multi-configuration generators (Visual Studio, Xcode and Ninja Multi-Config) is to run cmake -B build cmake --build build --config Release Passing CMAKE_BUILD_TYPE for multi-config generators will now not only not be used, but also generate a warning for the user. Co-authored-by: dundargoc <gocundar@gmail.com>
* | | | | fix(cmdheight=0): various issues part3 #19816Shougo2022-09-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | And fixed in https://github.com/neovim/neovim/pull/19801 regression. Fix #19834 Fix #19184
* | | | | refactor: migrate comment style 2 #20080dundargoc2022-09-06
|/ / / /
* | | | Merge pull request #19419 from vigoux/extmark_spellLewis Russell2022-09-06
|\ \ \ \ | | | | | | | | | | | | | | | Co-authored-by: Lewis Russell <lewis6991@gmail.com> Co-authored-by: Björn Linse <bjorn.linse@gmail.com>
| * | | | feat(extmarks,ts,spell): full support for spellingThomas Vigouroux2022-09-06
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Added 'spell' option to extmarks: Extmarks with this set will have the region spellchecked. - Added 'noplainbuffer' option to 'spelloptions': This is used to tell Neovim not to spellcheck the buffer. The old behaviour was to spell check the whole buffer unless :syntax was set. - Added spelling support to the treesitter highlighter: @spell captures in highlights.scm are used to define regions which should be spell checked. - Added support for navigating spell errors for extmarks: Works for both ephemeral and static extmarks - Added '_on_spell_nav' callback for decoration providers: Since ephemeral callbacks are only drawn for the visible screen, providers must implement this callback to instruct Neovim which regions in the buffer need can be spell checked. The callback takes a start position and an end position. Note: this callback is subject to change hence the _ prefix. - Added spell captures for built-in support languages Co-authored-by: Lewis Russell <lewis6991@gmail.com> Co-authored-by: Björn Linse <bjorn.linse@gmail.com>
* | | | Merge pull request #20039 from zeertzjq/cmod-tabbfredl2022-09-06
|\ \ \ \ | |/ / / |/| | | fix(api)!: correctly deal with number before :tab
| * | | fix(api)!: correctly deal with number before :tabzeertzjq2022-09-02
| | | | | | | | | | | | | | | | | | | | | | | | Now nvim_parse_cmd and nvim_create_user_command use a "tab" value which is the same as the number passed before :tab modifier instead of the number plus 1, and "tab" value is -1 if :tab modifier is not used.
* | | | Merge pull request #15391 from vigoux/ts-lua-builtinbfredl2022-09-06
|\ \ \ \ | | | | | | | | | | feat(treesitter): highlighting for core languages, enabled for Lua
| * | | | feat(treesitter): add vim.treesitter.start(), enable for LuaChristian Clason2022-09-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add vim.treesitter.start() for starting treesitter highlighting via ftplugin or autocommand (can be extended later for fold, indent, matchpairs, ...) * Add vim.treesitter.stop() for manually stopping treesitter highlighting * Enable treesitter highlighting for Lua if `vim.g.ts_highlight_lua = true` is set in `init.lua`
| * | | | fix(treesitter): do not link @error by defaultChristian Clason2022-09-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The @error capture is used for tree-sitter's ERROR node, which indicates a parsing error -- which can be quite frequent (and jarring) while typing. Users can still manually `hi link @error Error` in their config.
| * | | | feat(treesitter): add injectionsChristian Clason2022-09-06
| | | | |
| * | | | feat(treesitter): add viml parser and queriesChristian Clason2022-09-06
| | | | |
| * | | | ci(tests): don't skip parsers on functionaltestChristian Clason2022-09-06
| | | | | | | | | | | | | | | | | | | | | | | | | Treesitter parsers are now a mandatory part of the installation and should be tested on all platforms. Remove `pending_c_parser` helper.
| * | | | feat(treesitter): bundle Lua parser and queriesThomas Vigouroux2022-09-06
| | | | | | | | | | | | | | | | | | | | | | | | | parser from https://github.com/MunifTanjim/tree-sitter-lua queries from nvim-treesitter
* | | | | vim-patch:partial 0daafaa7d99e (#20083)Christian Clason2022-09-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update runtime files https://github.com/vim/vim/commit/0daafaa7d99ef500f76b1b12f5fe8153e2fcaea0 skip vim9script ftplugin create userfunc.txt from Neovim content (skip section 3, needs 9.0.0379)
* | | | | docs: update .mailmap (#20086)Lewis Russell2022-09-06
| |_|_|/ |/| | | | | | | Co-authored-by: dundargoc <33953936+dundargoc@users.noreply.github.com>
* | | | Merge pull request #20088 from zeertzjq/vim-9.0.0386zeertzjq2022-09-05
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | vim-patch:9.0.0386: some code blocks are nested too deep N/A patches for version.c: vim-patch:9.0.0385: GUI: when CTRL-D is mapped in Insert mode it gets inserted
| * | | | refactor(ex_cd): add an early return to fix clint warningzeertzjq2022-09-05
| | | | | | | | | | | | | | | | | | | | The popupmenu.c change is unrelated.
| * | | | vim-patch:9.0.0386: some code blocks are nested too deepzeertzjq2022-09-05
|/ / / / | | | | | | | | | | | | | | | | | | | | Problem: Some code blocks are nested too deep. Solution: Bail out earlier. (Yegappan Lakshmanan, closes vim/vim#11058) https://github.com/vim/vim/commit/b1f471ee20b0fa783ecd6e29aa69067e6c821376
* | | | docs(contributing): fix broken link (#20044)UnkwUsr2022-09-05
| | | |
* | | | Merge pull request #19481 from zeertzjq/vim-8.2.4674zeertzjq2022-09-04
|\ \ \ \ | | | | | | | | | | Add 'mousemoveevent' as a UI option
| * | | | feat(pum): pretend 'mousemoveevent' is set when showing right-click menuzeertzjq2022-09-04
| | | | |
| * | | | feat(api): add "move" to nvim_input_mousezeertzjq2022-09-04
| | | | |
| * | | | feat(tui): support 'mousemoveevent'zeertzjq2022-09-04
| | | | |
| * | | | feat(ui-ext): make 'mousemoveevent' a ui_optionzeertzjq2022-09-04
| | | | |
generated by cgit (git 2.34.1) at 2025-06-23 20:05:39 +0000