aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* refactor(api): move extmark API to its own fileBjörn Linse2021-10-25
|
* Merge pull request #16124 from mjlbach/feat/bjorn-baitBjörn Linse2021-10-24
|\ | | | | feat: add vim.str_utf_pos
| * feat: add vim.str_utf_pos functionMichael Lingelbach2021-10-24
| | | | | | | | | | vim.str_utf_pos returns the codepoints for all utf-8 chars (only, currently) in a string
* | vim-patch:8.2.3547: opening the quickfix window triggers BufWinEnter twice ↵Yorick Peterse2021-10-23
| | | | | | | | | | | | | | | | (#16108) Problem: Opening the quickfix window triggers BufWinEnter twice. (Yorick Peterse) Solution: Only trigger BufWinEnter with "quickfix". (closes vim/vim#9022) https://github.com/vim/vim/commit/1d30fde3c989a962e0e1af4cbcf90e1ea483f1f4
* | vim-patch:partial 079ba76ae7a7 (#16126)Christian Clason2021-10-23
| | | | | | | | | | | | | | | | Update runtime files https://github.com/vim/vim/commit/079ba76ae7a7d0ef404cb9b41dff2663ff41f51b skip optwin.vim (needs 8.2.3520) skip doc/options.txt (needs 8.2.1535) skip doc/insert.txt (needs 8.2.3528)
* | Merge pull request #16128 from bfredl/vluapackBjörn Linse2021-10-23
|\ \ | | | | | | feat(lua): document support of packages with v:lua syntax
| * | feat(lua): document support of packages with v:lua syntaxBjörn Linse2021-10-23
| | | | | | | | | | | | this already worked in 0.5 but was not properly documented or tested
* | | vim-patch:8.2.3542: too many comments are old style (#16096)dundargoc2021-10-23
| | | | | | | | | | | | | | | Problem: Too many comments are old style. Solution: Change comments to // style. (closes vim/vim#9021) https://github.com/vim/vim/commit/c5935a859ee31d56a565878d7a231fc59b7ddc01
* | | vim-patch:8.2.0026: still some /* */ comments (#16088)dundargoc2021-10-23
| | | | | | | | | | | | | | | Problem: Still some /* */ comments. Solution: Convert to // comments. https://github.com/vim/vim/commit/85a2002adb0eda9a9309c2fab4a79edaa91fb834
* | | Merge pull request #16111 from dundargoc/vim-patch/commentsJan Edmund Lazo2021-10-23
|\ \ \ | |/ / |/| | vim-patch:8.1.2368,8.1.2378,8.1.2379,8.1.2380,8.1.2387,8.1.2388,8.1.2392,8.1.2394,8.1.2395,8.1.2396
| * | vim-patch:8.1.2396: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/e38eab22c1fb950127f0307a9904de6d4561dc70
| * | vim-patch:8.1.2395: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/0d6f5d9740dbad1b0207f3ab257de806169dd905
| * | vim-patch:8.1.2394: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/63d9e730f726341bf41ee4f4b829253cb9879110
| * | vim-patch:8.1.2392: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/6e0ce171e19d0118ecd7c2b16e2a1bd50aa76013
| * | vim-patch:8.1.2388: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/4ba37b5833de99db9e9afe8928b31c864182405c
| * | vim-patch:8.1.2387: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/2ab2e8608f9b2c85432715bb9a7f226fdbf8cd35
| * | vim-patch:8.1.2380: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/306139005c31ea7e6f892dd119beba3c94dcb982
| * | vim-patch:8.1.2379: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/217e1b8359447f5550dcb0d1ee43380a90c253c5
| * | vim-patch:8.1.2378: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/5d18efecfd6c45d69f55268948a22cd0465bb955
| * | vim-patch:8.1.2368: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/c667da5185ce5dce914d2006d62da2be0cedb384
* | | Merge pull request #16029 from bfredl/multilineBjörn Linse2021-10-23
|\ \ \ | |_|/ |/| | feat(decorations): support more than one virt_lines block
| * | feat(decorations): support more than one virt_lines blockBjörn Linse2021-10-23
| | |
| * | refactor(decorations): mark decorations directly on the marktreeBjörn Linse2021-10-23
| |/ | | | | | | | | | | | | | | | | | | | | | | | | This allows to more quickly skip though regions which has non-decorative marks when redrawing. This might seem like a gratuitous micro-optimization in isolation. But! Soon decorations are gonna crop into other hot inner-loop paths, including the plines.c code for calculating the horizontal and vertical space of text. Then we want to quickly skip over regions with "only" overlaying decorations (which do not affect text size)
* | fix(lsp): cleanup progress messages for the correct client (#16110)Folke Lemaitre2021-10-21
| |
* | feat(lsp): add exit_timeout flag (#16070)Michael Lingelbach2021-10-21
| | | | | | | | | | | | | | * This flag allows customizing the time before sending kill -15 to the server. If set to false, neovim exits immediately after sending request('shutdown'). Otherwise, polls until all servers have shutdown, and then kills remaining servers via kill -15 at exit_timeout duration. Defaults to 500 ms.
* | vim-patch:8.2.3550: completion() does not work properly (#16112)Christian Clason2021-10-21
|/ | | | | | | | | | * vim-patch:8.2.3550: completion() does not work properly Problem: completion() does not work properly. Solution: Set xp_line and add WILD_HOME_REPLACE. (Shougo Matsushita, closes vim/vim#9016) https://github.com/vim/vim/commit/ae38a9db7770b38889fbf06908cc69d42b463a73 Co-authored-by: Sean Dewar <seandewar@users.noreply.github.com>
* Merge pull request #14794 from BK1603/gdbserver_fixMatthieu Coudron2021-10-20
|\ | | | | functionaltest: fix running tests under gdbserver
| * test: close timers in vim_spec.lua functional testShreyansh Chouhan2021-09-20
| | | | | | | | | | | | | | Close the timer started during tests before closing the session. This fixes the uv_loop_close hangs happening in the functional tests. Signed-off-by: Shreyansh Chouhan <chouhan.shreyansh2702@gmail.com>
| * test: fix running functional tests under gdbserverShreyansh Chouhan2021-09-20
| | | | | | | | | | | | | | | | | | | | | | It was not possible to run the tests under the gdbserver because we were not closing the old session before starting a new one. This caused the server to not to be able to bind to the given address and crashing the tests. This commit closes the session before starting a new one. Signed-off-by: Shreyansh Chouhan <chouhan.shreyansh2702@gmail.com>
* | vim-patch:8.1.2243: typos in comments (#16104)dundargoc2021-10-20
| | | | | | | | | | | | Problem: Typos in comments. Solution: Fix the typos. (Dominique Pelle, closes vim/vim#5160) Also adjust formatting a bit. https://github.com/vim/vim/commit/32aa10203bd0b4b270def03311a4599f9ffdecc4
* | fix(lsp): avoid duplicates in client attached buffers (#16099)Michael Lingelbach2021-10-20
| | | | | | | | | | | | | | closes https://github.com/neovim/neovim/issues/16058 * add client.attached_buffers * only update client.attached_buffers in on_attach * use table instead of list for attached_buffers to avoid duplication
* | fix(lsp): adjust legacy show diagnostic functions to use correct scope (#16106)Mathias Fußenegger2021-10-20
| | | | | | * `where` was renamed to `scope`
* | Merge pull request #16086 from bfredl/termpipe_inputBjörn Linse2021-10-20
|\ \ | | | | | | feat(nvim_open_term): support input callback in lua
| * | feat(nvim_open_term): support input callback in luaBjörn Linse2021-10-20
| | |
* | | build: update cmake min version to 3.10 #16065Jakub Łuczyński2021-10-19
| | | | | | | | | | | | | | | | | | * build(cmake): update cmake min version to 3.10 * ci: test cmake minimum required version * build(cmake): remove some legacy includes * Since version 3.5 cmake_parse_arguments is implemented natively.
* | | fix(diagnostic): allow floats to be focusable (#16093)Gregory Anders2021-10-19
| | | | | | | | | | | | Setting focus_id allows the float to be focused by calling the function a second time (a feature of open_floating_preview).
* | | fix(diagnostic): handle diagnostics placed past the end of line (#16095)Gregory Anders2021-10-19
| | |
* | | Merge pull request #15767 from lewis6991/lua_var_indexBjörn Linse2021-10-19
|\ \ \ | | | | | | | | feat(lua): allow passing handles to `vim.b/w/t`
| * | | feat(lua): allow passing handles to vim.b/w/tLewis Russell2021-10-19
| | | | | | | | | | | | | | | | | | | | | | | | vim.bo can target a specific buffer by indexing with a number, e.g: `vim.bo[2].filetype` can get/set the filetype for buffer 2. This change replicates that behaviour for the variable namespace.
* | | | fix(gen_vimdoc.py): spacing around inline elements #16092Gregory Anders2021-10-19
|/ / / | | | | | | | | | | | | The spacing fix drew attention to a couple of places that were using incorrect formatting such as the key listing for `nvim_open_win`, so those were fixed too.
* | | refactor(diagnostic)!: replace 'show_*' functions with 'open_float' (#16057)Gregory Anders2021-10-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 'show_line_diagnostics()' and 'show_position_diagnostics()' are almost identical; they differ only in the fact that the latter also accepts a column to form a full position, rather than just a line. This is not enough to justify two separate interfaces for this common functionality. Renaming this to simply 'show_diagnostics()' is one step forward, but that is also not a good name as the '_diagnostics()' suffix is redundant. However, we cannot name it simply 'show()' since that function already exists with entirely different semantics. Instead, combine these two into a single 'open_float()' function that handles all of the cases of showing diagnostics in a floating window. Also add a "float" key to 'vim.diagnostic.config()' to provide global values of configuration options that can be overridden ephemerally. This makes the float API consistent with the rest of the diagnostic API. BREAKING CHANGE
* | | feat(lsp): set codelens virtual text hl_mode to combine (#16048)sim2021-10-19
| | | | | | | | | | | | | | | It looks a bit off with the extmark going over the cursorline. (With hl_mode combine it keeps the background of the cursorline under the codelens virtualtext)
* | | vim-patch:8.2.3537: wrong mode() during 'operatorfunc' #16087zeertzjq2021-10-19
| | | | | | | | | | | | | | | Problem: mode() does not return the right value in 'operatorfunc'. Solution: Reset finish_op while calling 'operatorfunc'. https://github.com/vim/vim/commit/75c30e96cf280a8cc01ac01c41a9252db3e503cc
* | | docs: clarify chdir/CWD behaviors #16083zeertzjq2021-10-19
| | |
* | | fix(api/nvim_eval_statusline): allow maxwidth=0 #16080Famiu Haque2021-10-19
| | | | | | | | | | | | Allows disabling statusline truncation by allowing maxwidth to be set to 0 in `nvim_eval_statusline`.
* | | feat(man.vim): convert spaces to underscores #16068William Chargin2021-10-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | PostgreSQL ships with man pages for SQL statements like `CREATE TABLE`, which are provided with underscores as `man 7 CREATE_TABLE`. This patch updates `man#open_page` (as used by `:Man`) such that visually selecting the words `CREATE TABLE` in SQL code and pressing `K` properly opens the desired man page. Writing `:Man CREATE TABLE` still does not work, since `CREATE` is interpreted as a section name. (Similarly, `:Man CREATE TABLE AS` fails because there are too many arguments to `:Man`.) But this is okay, because if you're typing it anyway then you can just enter underscores and also tab-completion properly suggests `:Man CREATE_TABLE(7)`. This is a bit bespoke, but my box has over 9000 man pages (as reported by `man -k '' | wc -l`), and not one of them has a space in the man page name, whereas the Postgres manuals do exist and are actually useful. Test Plan: On a machine with Postgres manual pages, running nvim -u NORC +'exe "norm iCREATE TABLE foo(x int);" | norm 0veeK' should open the appropriate man page. wchargin-branch: man-spaces-to-underscores
* | | Merge #16000 refactor: uncrustifyJustin M. Keyes2021-10-19
|\ \ \
| * | | refactor: remove space after starDundar Göc2021-10-19
| | | |
| * | | refactor: make commas trail in enumsDundar Göc2021-10-19
| | | |
| * | | refactor: enable formatting for files under libDundar Göc2021-10-19
|/ / /
generated by cgit (git 2.34.1) at 2025-06-24 17:36:14 +0000