aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * vim-patch:9.1.0573: ex: no implicit print for single addresseszeertzjq2024-07-14
|/ | | | | | | | | | | | | | | | Problem: ex: no implicit print for single addresses Solution: explicitly print even during single addresses, as requested by POSIX (Mohamed Akram) See the POSIX behaviour here: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/ex.html#tag_20_40_13_03 Section 6b closes: vim/vim#15230 https://github.com/vim/vim/commit/c25a7084e9ae1f78c28ddcbe1fa23374cfdf1e03 Co-authored-by: Mohamed Akram <mohd.akram@outlook.com>
* vim-patch:9.1.0580: :lmap mapping for keypad key not applied when typed in ↵zeertzjq2024-07-14
| | | | | | | | | | | | Select mode (#29693) Problem: An :lmap mapping for a printable keypad key is not applied when typing it in Select mode. Solution: Change keypad key to ASCII after setting vgetc_char. (zeertzjq) closes: vim/vim#15245 https://github.com/vim/vim/commit/90a800274ded86d5d79dbea7ba647cd69b029b4e
* vim-patch:9.1.0575: Wrong comments in alt_tabpage() (#29692)zeertzjq2024-07-14
| | | | | | | | | Problem: Wrong comments in alt_tabpage() (after v9.1.0572) Solution: Correct the comments (zeertzjq). closes: vim/vim#15235 https://github.com/vim/vim/commit/1a3dd7dc7847a3568fe96192a21e478f46c07929
* Merge pull request #29691 from zeertzjq/vim-9.1.0577zeertzjq2024-07-14
|\ | | | | vim-patch:8.2.{3716,4065},9.1.{0577,0579}
| * vim-patch:8.2.3716: Vim9: range without a command is not compiledzeertzjq2024-07-14
| | | | | | | | | | | | | | | | | | Problem: Vim9: range without a command is not compiled. Solution: Add the ISN_EXECRANGE byte code. https://github.com/vim/vim/commit/e4eed8c6db693a9183b776032570ce2f89dcffb6 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * vim-patch:9.1.0579: Ex command is still executed after giving E1247zeertzjq2024-07-14
| | | | | | | | | | | | | | | | | | | | Problem: Ex command is still executed after giving E1247. Solution: Indicate the error properly and set cmd to NULL. (zeertzjq) closes: vim/vim#15241 https://github.com/vim/vim/commit/d1b5ea984d41102d253ecdd9a76124cd4c58b97d
| * vim-patch:8.2.4065: computation overflow with large cound for :yankzeertzjq2024-07-14
| | | | | | | | | | | | | | | | | | Problem: Computation overflow with large cound for :yank. Solution: Avoid an overflow. https://github.com/vim/vim/commit/3cf21b305104e91a28e4ce3a473672b2e88a9469 Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * test(old): enable Test_address_line_overflow()zeertzjq2024-07-14
| | | | | | | | | | Nvim doesn't use atol() in getdigits() and doesn't need to check for size of long.
| * vim-patch:9.1.0577: Unnecessary checks for v:sizeoflong in test_put.vimzeertzjq2024-07-14
|/ | | | | | | | | | | Problem: Unnecessary checks for v:sizeoflong in test_put.vim. They are no longer necessary as patch 8.2.3661 has changed the count to be within 32-bit integer limit. Solution: Remove the checks (zeertzjq). closes: vim/vim#15239 https://github.com/vim/vim/commit/69a28f6c0861523b1a9c565b3c882f439ae73ef4
* Merge pull request #29315 from bfredl/staticinlinebfredl2024-07-13
|\ | | | | refactor(declarations): also generate prototypes for functions in headers
| * refactor(declarations): also generate prototypes for functions in headersbfredl2024-07-13
| | | | | | | | | | | | | | | | | | | | | | Before this change, "static inline" functions in headers needed to have their function attributes specified in a completely different way. The prototype had to be duplicated, and REAL_FATTR_ had to be used instead of the public FUNC_ATTR_ names. TODO: need a check that a "header.h.inline.generated.h" file is not forgotten when the first "static inline" function with attributes is added to a header (they would just be silently missing).
* | Merge pull request #29659 from amitds1997/fix/empty-dict-encodingbfredl2024-07-13
|\ \ | |/ |/| fix(lua)!: do not use typed table for empty dict
| * fix(lua)!: do not use typed table for empty dictAmit Singh2024-07-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Empty dictionaries are converted into typed tables of the form `{ [true] = 6}` instead of an empty dictionary representation `{}`. This leads to incorrect table representation, along with failure in JSON encoding of such tables as currently tables with only string and number type keys can be encoded. Solution: The typed table logic has been removed from `nlua_push_Dictionary`. The typed table logic is required only for float value conversions which is already handled in `nlua_push_Float`. So, it is(was) no longer required here. Fixes neovim/neovim#29218
* | Merge pull request #29632 from echasnovski/filetype-refactorLewis Russell2024-07-13
|\ \ | |/ |/| refactor(filetype): extract some functions, use more cache
| * refactor(filetype): use Lua patterns without implicit anchoringEvgeni Chasnovski2024-07-12
| |
| * refactor(filetype): extract expanding env. vars in separate functionEvgeni Chasnovski2024-07-12
| |
| * perf(filetype): cache (more) pattern data during "add" timeEvgeni Chasnovski2024-07-12
| |
| * refactor(filetype): unify matching patterns with pos/neg priorityEvgeni Chasnovski2024-07-12
| | | | | | | | | | | | | | | | | | | | | | Problem: due to single list of sorted patterns, their matching inside `vim.filetype.match()` was done very similarly but with extra checks to stop processing negative priority patterns before extensions. Solution: create separated sorted lists for patterns with non-negative and negative priorities. This allows to process them in a single extracted function making the main codeflow a bit nicer and more easily expandable.
* | vim-patch:9.1.0572: cannot specify tab page closing behaviour (#29682)zeertzjq2024-07-13
| | | | | | | | | | | | | | | | | | | | | | | | Problem: cannot specify tab page closing behaviour (Gianluca Pacchiella) Solution: Add the 'tabclose' option (LemonBoy). fixes: vim/vim#5967 closes: vim/vim#15204 https://github.com/vim/vim/commit/5247b0b92e191a046b034171a3b34031e317735f Co-authored-by: LemonBoy <thatlemon@gmail.com>
* | vim-patch:74703f1: runtime(doc): remove obsolete Ex insert behavior (#29678)zeertzjq2024-07-13
| | | | | | | | | | | | | | | | | | | | related: vim/vim#15120 closes: vim/vim#15228 https://github.com/vim/vim/commit/74703f1086e7815f356123736666d9930db8683a Nvim only supports Vim Ex mode, so this is long obsolete in Nvim. Co-authored-by: Mohamed Akram <mohd.akram@outlook.com>
* | fix(input): handle vim.on_key() properly with ALT and K_SPECIAL (#29677)zeertzjq2024-07-13
|/
* vim-patch:57f7d75: runtime(logindefs): update syntax with new keywordsChristian Clason2024-07-12
| | | | | | | | | | | * add keywords * enforce octal format for permissions closes: vim/vim#15222 https://github.com/vim/vim/commit/57f7d75591da0ec91068741eefbad295be8f78b4 Co-authored-by: Eisuke Kawashima <e-kwsm@users.noreply.github.com>
* vim-patch:fc533c9: runtime(mojo): include mojo ftplugin and indent scriptChristian Clason2024-07-12
| | | | | | | | | | | Taken from excerpts of the Python ftplugin and adapted, indent script simply sources the python indent script. closes: vim/vim#15171 https://github.com/vim/vim/commit/fc533c9f06aff579437f9f2348a21241a72c7967 Co-authored-by: Riley Bruins <ribru17@hotmail.com>
* vim-patch:7a22cb8: runtime(fstab): Add missing keywords to fstab syntaxChristian Clason2024-07-12
| | | | | | | | | | Added overlay, tracefs and fixed the "none" keyword in the fstab syntax definition. closes: vim/vim#15217 https://github.com/vim/vim/commit/7a22cb81415060215d28c1601a0b35755449bf87 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:9.1.0569: fnamemodify() treats ".." and "../" differently (#29673)zeertzjq2024-07-12
| | | | | | | | | Problem: fnamemodify() treats ".." and "../" differently. Solution: Expand ".." properly like how "/.." is treated in 8.2.3388. (zeertzjq) closes: vim/vim#15218 https://github.com/vim/vim/commit/1ee7420460768df67ea4bc73467f2d4f8b1555bd
* Merge pull request #29669 from zeertzjq/vim-9.1.0568zeertzjq2024-07-12
|\ | | | | vim-patch:partial:9.0.{0323,0418},9.1.0568
| * vim-patch:9.1.0568: Cannot expand paths from 'cdpath' settingzeertzjq2024-07-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Cannot expand paths from 'cdpath' setting (Daniel Hahler) Solution: Implement 'cdpath' completion, add the new 'dir_in_path' completion type (LemonBoy) fixes vim/vim#374 closes: vim/vim#15205 https://github.com/vim/vim/commit/a20bf69a3b32024cb7809be87af33bf9dc490a19 Co-authored-by: LemonBoy <thatlemon@gmail.com>
| * vim-patch:partial:9.0.0418: manually deleting temp test fileszeertzjq2024-07-12
| | | | | | | | | | | | | | | | | | | | | | Problem: Manually deleting temp test files. Solution: Use the 'D' flag of writefile() and mkdir(). https://github.com/vim/vim/commit/45bbaef0382c5468d9fac511775bd99ea7bf5b84 This only includes test_cd.vim changes. Co-authored-by: Bram Moolenaar <Bram@vim.org>
| * vim-patch:partial:9.0.0323: using common name in tests leads to flaky testszeertzjq2024-07-12
|/ | | | | | | | | | | Problem: Using common name in tests leads to flaky tests. Solution: Rename files and directories to be more specific. https://github.com/vim/vim/commit/3b0d70f4ff436cb144683dafd956e8a3ee485a90 This only includes test_cd.vim changes. Co-authored-by: Bram Moolenaar <Bram@vim.org>
* Merge pull request #29668 from zeertzjq/vim-9.1.0562zeertzjq2024-07-12
|\ | | | | vim-patch:9.1.{0562,0565,0566,0567}: file search fixes
| * vim-patch:9.1.0567: Cannot use relative paths as findfile() stop directorieszeertzjq2024-07-12
| | | | | | | | | | | | | | | | | | | | | | Problem: Cannot use relative paths as findfile() stop directories. Solution: Change a relative path to an absolute path. (zeertzjq) related: vim/vim#15200 closes: vim/vim#15202 https://github.com/vim/vim/commit/764526e2799fbed040fc867858ee2eb0677afe98
| * vim-patch:9.1.0566: Stop dir in findfile() doesn't work properly w/o ↵zeertzjq2024-07-12
| | | | | | | | | | | | | | | | | | | | | | | | | | trailing slash Problem: Stop directory in findfile() doesn't work properly without a trailing slash. Solution: Always use fnamencmp(), not fnamecmp(). related: vim/vim#15200 related: vim/vim#15202 https://github.com/vim/vim/commit/e6ab23bd4a41840860ae2904956c4d255a9dd528
| * vim-patch:9.1.0565: Stop directory doesn't work properly in 'tags'zeertzjq2024-07-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Stop directory doesn't work properly in 'tags'. (Jesse Pavel) Solution: Also move the stop directory forward by one byte. (zeertzjq) This doesn't support relative stop directories yet, as they are not supported in other places like findfile() either. fixes: vim/vim#15200 related: vim/vim#15202 https://github.com/vim/vim/commit/68819afb2cdd0f44baa080db589e1d8f77099e5f
| * vim-patch:partial:9.0.0323: using common name in tests leads to flaky testszeertzjq2024-07-12
|/ | | | | | | | | | | | | | | | | | | | | Problem: Using common name in tests leads to flaky tests. Solution: Rename files and directories to be more specific. https://github.com/vim/vim/commit/3b0d70f4ff436cb144683dafd956e8a3ee485a90 This only includes test_findfile.vim changes. vim-patch:9.1.0562: tests: inconsistency in test_findfile.vim Problem: tests: inconsistency in test_findfile.vim, it saves and restores 'shellslash', but doesn't actually set it Solution: Set shellslash explicitly (zeertzjq) closes: vim/vim#15217 https://github.com/vim/vim/commit/e7b98ab96e1f1bd12032c620615a2c69adbf018d Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:8.2.3388: fnamemodify('path/..', ':p') differs from using ↵zeertzjq2024-07-12
| | | | | | | | | | 'path/../' (#29667) Problem: fnamemodify('path/..', ':p') differs from using 'path/../'. Solution: Include the "/.." in the directory name. (closes vim/vim#8808) https://github.com/vim/vim/commit/4eaef9979fc5032606897963f1af37674ee0d422 Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:9.1.0557: moving in the buffer list doesn't work as documented ↵zeertzjq2024-07-11
| | | | | | | | | | | | | | | | | | | (#29653) Problem: moving in the buffer list doesn't work as documented (SenileFelineS) Solution: Skip non-help buffers, when run from normal buffers, else only move from help buffers to the next help buffer (LemonBoy) As explained in the help section for :bnext and :bprev the commands should jump from help buffers to help buffers (and from regular ones to regular ones). fixes: vim/vim#4478 closes: vim/vim#15198 https://github.com/vim/vim/commit/893eeeb44583ca33276e263165b2a6e50fd297d0 Co-authored-by: LemonBoy <thatlemon@gmail.com>
* vim-patch:9.1.0555: filetype: angular ft detection is still problematicChristian Clason2024-07-11
| | | | | | | | | | | | | | | | | | | | Problem: filetype: angular ft detection is still problematic (after 9.1.0551) Solution: detect htmlangular filetype only by inspecting the content, do not try to determine it from a generic name like '*.component.html' For the reasons mentioned here: https://github.com/vim/vim/pull/13594#issuecomment-1834465890 related: vim/vim#15190 related: vim/vim#13594 related: vim/vim#13604 https://github.com/vim/vim/commit/c03f631b7b01e672787b222a55898f8dcac8d859 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:a3a14d5: runtime(htmlangular): correct commentChristian Clason2024-07-11
| | | | | | | | related: vim/vim#15190 https://github.com/vim/vim/commit/a3a14d5469681676310d39c19e110a57cd8ac7c6 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:7a85e34: runtime(doc): fix inconsistencies in :h file-searching ↵zeertzjq2024-07-11
| | | | | | | (#29652) closes: vim/vim#15201 https://github.com/vim/vim/commit/7a85e343d29e502f66e2c3035808911e5a843e99
* vim-patch:9.1.0556: :bwipe doesn't remove file from jumplist of other ↵zeertzjq2024-07-11
| | | | | | | | | | | | | tabpages (#29651) Problem: :bwipe doesn't remove file from jumplist and tagstack of other tabpages. Time complexity of mark_forget_file() is O(n^2) when removing all entries (after v9.1.0554) Solution: Use FOR_ALL_TAB_WINDOWS(). Start the loops over the arrays from the end instead of the start (zeertzjq) closes: vim/vim#15199 https://github.com/vim/vim/commit/2e7d89b39883b0cfd3e615b02bd55186e00fb7ce
* refactor: remove CH_FOLD macrodundargoc2024-07-10
| | | | It should not be needed as utf_fold should already work on its own.
* vim-patch:9.1.{0503,0549} (#29643)zeertzjq2024-07-10
| | | | | | | | | | | | | | | | | | | | | | | | vim-patch:9.1.0503: cannot use fuzzy keyword completion Problem: cannot use fuzzy keyword completion (Maxim Kim) Solution: add the "fuzzycollect" value for the 'completeopt' setting, to gather matches using fuzzy logic (glepnir) fixes: vim/vim#14912 closes: vim/vim#14976 https://github.com/vim/vim/commit/43eef882ff42e673af1e753892801ba20c5d002a vim-patch:9.1.0549: fuzzycollect regex based completion not working as expected Problem: fuzzycollect regex based completion not working as expected Solution: Revert Patch v9.1.0503 (glepnir) closes: vim/vim#15192 https://github.com/vim/vim/commit/600a12d08e7aeb95a6b02382bfee310aef9801dd Co-authored-by: glepnir <glephunter@gmail.com>
* vim-patch:9.1.0553: filetype: *.mcmeta files are not recognizedChristian Clason2024-07-10
| | | | | | | | | | | | | | | | | | | | | | | | | Problem: filetype: *.mcmeta files are not recognized Solution: Detect '*.mcmeta' files as json filetype (Tomodachi94) "pack.mcmeta" was added to the JSON tests because that is the most common filename with that extension. There are currently 34,000 instances of this file extension on GitHub: https://github.com/search?q=path%3A*.mcmeta&type=code&p=2 .zip files with this extension have downloads in the millions on sites like CurseForge: https://www.curseforge.com/minecraft/search?page=1&pageSize=20&sortBy=relevancy&class=texture-packs Further reading about the file extension: https://minecraft.wiki/w/Tutorials/Creating_a_resource_pack#Creating_a_.MCMETA_file closes: vim/vim#15189 https://github.com/vim/vim/commit/d33a518025765c4a3530ad6cfb6cab83a30c8f55 Co-authored-by: Tomodachi94 <tomodachi94@protonmail.com>
* vim-patch:9.1.0551: filetype: htmlangular files are not properly detectedChristian Clason2024-07-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: filetype: htmlangular files are not properly detected Solution: Use the new htmlangular filetype for angular files, because since angular v17, those are no longer valid HTML files. (Dennis van den Berg) Since Angular 17, the new Control Flow Syntax is not valid HTML. This PR adds a new filetype detection for the HTML templates of Angular. It first checks the filename. The Angular convention is to use *.component.html for the template. However, this is not mandatory. If the filename does not match, it will check the contents of the file if it contains: - One of the Control-Flow blocks: @if, @for, @switch, @defer - A structural directive: *ngIf, *ngFor, *ngSwitch, *ngTemplateOutlet - Builtin Angular elements: ng-template or ng-content - String interpolation: {{ something }} This enables the Angular LSP to attach only to htmlangular filetypes, as well as language parsers, such as tree-sitter. closes: vim/vim#15190 https://github.com/vim/vim/commit/1ad194c0dfd82ca1e7a1b6f2fca89a487794158d Co-authored-by: Dennis van den Berg <dennis.vandenberg@nedap.com>
* vim-patch:9.1.0552: No test for antlr4 filetypeChristian Clason2024-07-10
| | | | | | | | | | | | Problem: No test for antlr4 filetype (after 9.1.0550) Solution: Add a simple filename test related: vim/vim#15191 https://github.com/vim/vim/commit/8fc23bb8a433a28ccf1a60a48ad91bd7226c3d73 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:9.1.0550: filetype: antlr4 files are not recognizedChristian Clason2024-07-10
| | | | | | | | | | | | Problem: filetype: antlr4 files are not recognized Solution: Detect '*.g4' as antlr4 filetype, include a simple antlr4 syntax and filetype plugin (Yinzuo Jiang) closes: vim/vim#15191 https://github.com/vim/vim/commit/4a7a4a3675b6ad90a525524ba4684925df212325 Co-authored-by: Yinzuo Jiang <jiangyinzuo@foxmail.com>
* vim-patch:9.1.0554: :bw leaves jumplist and tagstack data around (#29639)zeertzjq2024-07-10
| | | | | | | | | | | | | | | | | Problem: :bw leaves jumplist and tagstack data around (Paul "Joey" Clark) Solution: Wipe jumplist and tagstack references to the wiped buffer (LemonBoy) As documented the :bwipeout command brutally deletes all the references to the buffer, so let's make it delete all the entries in the jump list and tag stack referring to the wiped-out buffer. fixes: vim/vim#8201 closes: vim/vim#15185 https://github.com/vim/vim/commit/4ff3a9b1e3ba45f9dbd0ea8c721f27d9315c4d93 Co-authored-by: LemonBoy <thatlemon@gmail.com>
* vim-patch:9.1.0547: No way to get the arity of a Vim function (#29638)zeertzjq2024-07-10
| | | | | | | | | | | | | Problem: No way to get the arity of a Vim function (Austin Ziegler) Solution: Enhance get() Vim script function to return the function argument info using get(func, "arity") (LemonBoy) fixes: vim/vim#15097 closes: vim/vim#15109 https://github.com/vim/vim/commit/48b7d05a4f88c4326bd5d7a73a523f2d953b3e51 Co-authored-by: LemonBoy <thatlemon@gmail.com>
* vim-patch:73a8108: runtime(tmux): Update syntax scriptChristian Clason2024-07-09
| | | | | | | | | | closes: vim/vim#15195 related: vim/vim#15188 https://github.com/vim/vim/commit/73a810817b9bea7ce31e625bf5519b6a02f53d41 Co-authored-by: Eric Pruitt <eric.pruitt@gmail.com> Co-authored-by: Contsantine Bulany <61948252+lostl1ght@users.noreply.github.com>
* fix(diagnostic): fix backwards compatibility for goto_next and goto_prev ↵Max Coplan2024-07-09
| | | | (#29593)