aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* feat(float): implement footerEvgeni Chasnovski2023-08-26
| | | | | | | | Problem: Now way to show text at the bottom part of floating window border (a.k.a. "footer"). Solution: Allows `footer` and `footer_pos` config fields similar to `title` and `title_pos`.
* refactor(float): extract "title" and "title_pos" handlingEvgeni Chasnovski2023-08-26
|
* fix(statuscolumn): force full redraw when signcolumn is invalid (#24859)luukvbaal2023-08-26
| | | Fix #24655
* Merge pull request #24399 from lambdalisue/fix-messagepack-rpcbfredl2023-08-26
|\ | | | | feat(msgpack_rpc): add a new `msgpack-rpc` client type to fix behavior with MessagePack-RPC compliant clients
| * docs(megpack_rpc): add news entry for msgpack-rpc client typeAlisue2023-08-26
| |
| * docs(msgpack_rpc): add "msgpack-rpc" client typeAlisue2023-08-26
| |
| * feat(msgpack_rpc): support out-of-order responses on `msgpack-rpc`Alisue2023-08-26
| | | | | | | | | | | | | | | | | | | | | | | | | | Added to support MessagePack-RPC fully compliant clients that do not return responses in request order. Although it is currently not an efficient implementation for full compliance and full compliance cannot be guaranteed, the addition of the new client type `msgpack-rpc` creates a situation where "if the client type is `msgpack-rpc`, then backward compatibility is ignored and full compliance with MessagePack- RPC compliance is justified even if backward compatibility is ignored if the client type is `msgpack-rpc`.
| * feat(msgpack-rpc): show actual request id in error messageAlisue2023-08-26
| |
* | fix(extmarks): wrong display when changing text with virt_lines (#24879)Ibby2023-08-26
| |
* | Merge pull request #24824 from bfredl/nocurbufbfredl2023-08-26
|\ \ | |/ |/| refactor(change): do API changes to buffer without curbuf switch
| * refactor(change): do API changes to buffer without curbuf switchbfredl2023-08-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Most of the messy things when changing a non-current buffer is not about the buffer, it is about windows. In particular, it is about `curwin`. When editing a non-current buffer which is displayed in some other window in the current tabpage, one such window will be "borrowed" as the curwin. But this means if two or more non-current windows displayed the buffers, one of them will be treated differenty. this is not desirable. In particular, with nvim_buf_set_text, cursor _column_ position was only corrected for one single window. Two new tests are added: the test with just one non-current window passes, but the one with two didn't. Two corresponding such tests were also added for nvim_buf_set_lines. This already worked correctly on master, but make sure this is well-tested for future refactors. Also, nvim_create_buf no longer invokes autocmds just because you happened to use `scratch=true`. No option value was changed, therefore OptionSet must not be fired.
* | build: fix "make iwyu" not working (#24873)zeertzjq2023-08-26
|/
* refactor: move some structs out of buffer_defs.h (#24878)zeertzjq2023-08-26
|
* docs: various clarifications (#24876)zeertzjq2023-08-26
|
* feat(treesitter): add a query editor (#24703)Maria José Solano2023-08-25
|
* Merge pull request #24872 from zeertzjq/plineszeertzjq2023-08-25
|\ | | | | some plines.c refactors
| * refactor(plines.c): deduplicate code for virtual text cursor offsetzeertzjq2023-08-25
| |
| * refactor: move virtcol functions to plines.czeertzjq2023-08-25
| | | | | | | | | | | | Problem: Functions for virtcol and chartabsize are similar (both compute horizontal size), but appear in two different source files. Solution: Move virtcol functions to plines.c.
| * refactor(plines.c): move vertical size functions to the bottomzeertzjq2023-08-25
|/ | | | | | Problem: It may be unclear what "below" in first comment refers to. Solution: Move vertical size functions to the bottom so that it can be changed to "above".
* Merge pull request #24821 from seandewar/vim-9f2962141514Sean Dewar2023-08-25
|\ | | | | vim-patch:9f2962141514,f6fb52b667ee,19968fc4ec2c,a76f3221cdcf,2ae7ffe0bc3c,3d3a9152fa6d - Termdebug stuff
| * refactor(termdebug): reindent some thingsSean Dewar2023-08-25
| | | | | | | | Mostly to make it more consistent and to match Vim more where applicable.
| * vim-patch:3d3a9152fa6dSean Dewar2023-08-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(termdebug): more termdebug fixes and improvements (vim/vim#12892) - Fix and attempt to simplify :Frame/:Up/:Down documentation. - Accept a count instead for :Up/:Down/+/-. - Update the "Last Change" dates. - Fix a missing :let (caused an error if gdb fails to start). - Wipe the prompt buffer when ending prompt mode (if it exists and wasn't wiped by the user first). Avoids issues with stale prompt buffers (such as E95 when starting a new prompt mode session). - Kill the gdb job if the prompt buffer is unloaded (similar to what's done for a terminal buffer). Fixes not being able to start a new termdebug session if the buffer was wiped by the user, for example. https://github.com/vim/vim/commit/3d3a9152fa6de7038fdfd6d6de25230ed825552a
| * vim-patch:2ae7ffe0bc3cSean Dewar2023-08-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(termdebug): add frame related commands (vim/vim#12511) implementing `:Frame`, `:Up` and `:Down' https://github.com/vim/vim/commit/2ae7ffe0bc3c3ed9fcae35ef23a2b78908580201 Use maparg() for saving K as it's since been ported (and supports Lua callbacks and the other API fields). Use the 3 argument variant of mapset(), as the single argument one isn't ported yet (v8.2.4861). Co-authored-by: Simon Sobisch <simonsobisch@web.de>
| * fix(termdebug): send SIGINT when interrupting prompt modeSean Dewar2023-08-25
| | | | | | | | | | | | | | | | | | | | | | | | | | Unlike Vim's job_stop(), Nvim's jobstop() does not take a signal argument, and always sends SIGTERM/KILL. :Stop and Ctrl-C in prompt mode is supposed to interrupt the program like in terminal mode, not kill GDB. Also, maybe libuv's kill() works on Windows? If so, the logic above could be removed, but I don't have a Windows machine available to test that. Also "set nomodified" when ending prompt mode, like Vim (avoids E37).
| * vim-patch:a76f3221cdcfSean Dewar2023-08-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(termdebug): Fix various Termdebug issues (vim/vim#12875) * Fix some Termdebug issues after vim/vim#12403 * Fix :Asm in Termdebug prompt mode * Fix Termdebug s:DecodeMessage escaping logic https://github.com/vim/vim/commit/a76f3221cdcfff6880213839de4d04cf0c7c60f8 Adjust disassembly message forwarding for Nvim, as its callback can receive many lines at once. Currently, just forward each disassembly line individually to s:CommOutput(); it's possible to do this in batch instead, but this is simpler. I suggested moving to a GDB MI-based approach for the disassemble stuff upstream, which should simplify the logic a lot if implemented (and possibly allow for getting rid of the `&"disassemble ...` special-casing). Also, correct "(gdb)" to include a trailing space; the stray GDB prompts were being ignored by s:CommOutput() anyway, so this had caused no ill effects.
| * fix(termdebug): prompt mode breaks with &splitbelow setSean Dewar2023-08-25
| | | | | | | | | | Unlike Vim, termopen() doesn't split, so you can't use the modifier like that. Remove the fragile :wincmd shenanigans.
| * fix(termdebug): trim suffixed "\r" in CommOutputSean Dewar2023-08-25
| | | | | | | | | | | | | | | | | | Vim splits lines on "\r", then trims any prefixed "\n". But in Nvim, job output lines are split on "\n" (like readfile() in binary mode), so trim any suffixed "\r" instead. This gets rid of the trailing "^M" character in messages parsed from the jobs.
| * vim-patch:19968fc4ec2cSean Dewar2023-08-25
| | | | | | | | | | | | | | | | runtime(termdebug): re-indent lines (vim/vim#12857) https://github.com/vim/vim/commit/19968fc4ec2c36c7d528c7326acf43e5d663ba39 Co-authored-by: Shane-XB-Qian <shane.qian@foxmail.com>
| * vim-patch:f6fb52b667eeSean Dewar2023-08-25
| | | | | | | | | | | | | | | | | | | | runtime(termdebug): refactor error printing (vim/vim#12856) // vs not act like exception from vim or termdebug https://github.com/vim/vim/commit/f6fb52b667eecb58bdd9b26bd462d5da61697cf7 Co-authored-by: Shane-XB-Qian <shane.qian@foxmail.com>
| * vim-patch:9f2962141514Sean Dewar2023-08-25
|/ | | | | | | | | | | | | | | | Runtime(termdebug): Add support to view local and argument variables closes: 12403 https://github.com/vim/vim/commit/9f29621415146abc046471440515e9e34f3e57a1 Rename the existing "s:running" (#16790) to "s:gdb_running" to not clash with the "s:running" introduced in this patch (which instead relates to whether the debugged program is currently running in gdb). Keep the file `:retab`bed as before. Co-authored-by: laburnumT <flo.striker@gmail.com>
* Merge pull request #24864 from gpanders/filetype-on-detect-orderGregory Anders2023-08-24
|\
| * fix(filetype): return on_detect function when matching by file contentsGregory Anders2023-08-24
| |
| * fix(filetype): call on_detect before setting buffer filetypeGregory Anders2023-08-24
| | | | | | | | | | | | | | | | | | | | | | | | The on_detect functions returned by filetype.lua set buffer local variables which are often used by filetype plugins. For example, the on_detect function for shell buffers sets variables such as b:is_bash or b:is_sh, which are used by the sh ftplugin. When called after setting the buffer's filetype, these variables cannot be used by the ftplugin (because they are not yet defined). Instead, call on_detect before setting the buffer filetype so that any buffer variables set by on_detect can be used in the ftplugin.
* | Merge pull request #24862 from bfredl/ml_get_bufbfredl2023-08-24
|\ \ | |/ |/| refactor(memline): distinguish mutating uses of ml_get_buf()
| * refactor(memline): distinguish mutating uses of ml_get_buf()bfredl2023-08-24
|/ | | | | | | | | | | | | | ml_get_buf() takes a third parameters to indicate whether the caller wants to mutate the memline data in place. However the vast majority of the call sites is using this function just to specify a buffer but without any mutation. This makes it harder to grep for the places which actually perform mutation. Solution: Remove the bool param from ml_get_buf(). it now works like ml_get() except for a non-current buffer. Add a new ml_get_buf_mut() function for the mutating use-case, which can be grepped along with the other ml_replace() etc functions which can modify the memline.
* docs(builtin): small fixes (#24861)Sean Dewar2023-08-24
| | | | Also make gen_eval_files.lua render vimdoc helpExamples properly if the line begins with the `>` marker.
* Merge pull request #24702 from seandewar/vim-1688938dd5acSean Dewar2023-08-24
|\ | | | | vim-patch:1688938dd5ac,96d6c4aabed1,e8d6f03f6a61
| * vim-patch:e8d6f03f6a61Sean Dewar2023-08-23
| | | | | | | | | | | | | | | | | | | | | | | | | | runtime: Remove Brams name from a few more runtime files (vim/vim#12780) syntax/model.vim: minor wording improvement https://github.com/vim/vim/commit/e8d6f03f6a61f60de6893253621d057f63dd6a23 Use the updated "Last Change" date for all. Co-authored-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Adri Verhoef <a3@a3.xs4all.nl>
| * vim-patch:96d6c4aabed1Sean Dewar2023-08-23
| | | | | | | | | | | | | | | | runtime: Remove Brams email in indent/README.txt https://github.com/vim/vim/commit/96d6c4aabed15266bc4acfa66f9b35c2820dfa59 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * vim-patch:1688938dd5acSean Dewar2023-08-23
| | | | | | | | | | | | | | | | runtime: Add a few more remarks about Bram and new runtime files https://github.com/vim/vim/commit/1688938dd5ac78ab67e54299b9d5b93499dba762 Co-authored-by: Christian Brabandt <cb@256bit.org>
* | fix(plines.c): initialize cts_max_head_vcol (#24855)zeertzjq2023-08-24
| |
* | fix(ui): wrong display with 0-width inline virt_text at eol (#24854)zeertzjq2023-08-24
| |
* | vim-patch:2f25e40b1f54Christian Clason2023-08-24
| | | | | | | | | | | | | | | | runtime: configure keywordpg for some file types (vim/vim#5566) https://github.com/vim/vim/commit/2f25e40b1f545f4aa38377f0c25effb112b5d1ef Co-authored-by: Enno <Konfekt@users.noreply.github.com>
* | vim-patch:3fc7a7e44abdChristian Clason2023-08-24
| | | | | | | | | | | | | | | | | | | | runtime: Fix typos in various files closes: vim/vim#12836 https://github.com/vim/vim/commit/3fc7a7e44abda6505ccd39a6d067db6e5173cbf6 Co-authored-by: Viktor Szépe <viktor@szepe.net>
* | vim-patch:e059fae10044Christian Clason2023-08-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(menu): define shortcut for File->Open Tab (vim/vim#12895) Seems missing as noted by Antonio Giovanni Colombo. So add it and use the 'T' as shortcut, which does not seem to be used in the File dialog. Verified on Windows. https://github.com/vim/vim/commit/e059fae100448fee4b581dd5d90ee853ea18de7e Co-authored-by: Christian Brabandt <cb@256bit.org> Co-authored-by: Antonio Giovanni Colombo <azc100@gmail.com>
* | vim-patch:6e93689bde73Christian Clason2023-08-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(bindzone): updated syntax file - Add support for APL type in runtime/syntax/bindzone.vim - all values between 0- 4294967295 are valid serials closes: vim/vim#9743 closes: vim/vim#8382 https://github.com/vim/vim/commit/6e93689bde7321ce974ae99ec6c74efb08d78842 vim-patch:544b209a2d4b runtime(scala): Link Scala highlighting groups using 'hi def link' in syntax script (vim/vim#9594) They were linked using 'hi link' which made it impossible for color schemes to override highlight groups. https://github.com/vim/vim/commit/544b209a2d4b10e0a4874c925036def30d33d708 Co-authored-by: Oskar Stenman <oskar@cetex.se> Co-authored-by: Job Noorman <job@noorman.info>
* | vim-patch:118f8e9da39eChristian Clason2023-08-24
| | | | | | | | | | | | | | | | runtime(cmake) Recognize add_compile_definitions in syntax script (vim/vim#10416) https://github.com/vim/vim/commit/118f8e9da39e6cec5ffe644d5b87a7772418ed0c Co-authored-by: MichaWiedenmann <mw-r1@gmx.de>
* | vim-patch:cdd934439d08Christian Clason2023-08-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | runtime(crontab): add support for BSD specifics in syntax script (vim/vim#11196) * OpenBSD supports the use of `~` as alias for "random valid value" * FreeBSD supports `@every_{minute,second}` See: * https://man.openbsd.org/crontab.5 * https://www.freebsd.org/cgi/man.cgi?query=crontab&sektion=5 https://github.com/vim/vim/commit/cdd934439d08768235be04817ee214f067e8cf56 Co-authored-by: Moviuro <moviuro@users.noreply.github.com>
* | vim-patch:b0d584d97ab6Christian Clason2023-08-24
| | | | | | | | | | | | | | | | | | | | runtime(go): Update Go syntax file with 1.21 builtins (vim/vim#12876) * Update Go syntax file with 1.21 builtins https://github.com/vim/vim/commit/b0d584d97ab6f5cb070caba3882ba387b81448c1 Co-authored-by: José-Paul D <fixed.combinator@gmail.com>
* | vim-patch:e34b51e95fd0Christian Clason2023-08-24
| | | | | | | | | | | | | | | | | | | | | | | | | | runtime(solidity): add new ftplugin (vim/vim#12877) Set undo_{ftplugin,indent} closes vim/vim#11240 https://github.com/vim/vim/commit/e34b51e95fd0ea7b0e34a625db0f9ed7e051e0dd Co-authored-by: dkearns <dougkearns@gmail.com> Co-authored-by: cothi <jiungdev@gmail.com>
generated by cgit (git 2.34.1) at 2025-06-24 14:37:47 +0000