aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
* vim-patch:3698fbb: runtime(tsv): include simple syntax pluginChristian Clason2024-07-17
| | | | | | | | fixes: vim/vim#15271 https://github.com/vim/vim/commit/3698fbbd7c35590dcc4708677d6c38f9009cf9a3 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:9.1.0593: filetype: Asymptote files are not recognizedChristian Clason2024-07-17
| | | | | | | | | | | | | | Problem: filetype: Asymptote files are not recognized Solution: detect '*.asy' files as asy filetype, include ftplugin and syntax plugin (AvidSeeker). Reference: https://asymptote.sourceforge.io/ closes: vim/vim#15252 https://github.com/vim/vim/commit/3088ef094da721dac8c0363a6c9e14eaf9313929 Co-authored-by: AvidSeeker <avidseeker7@protonmail.com>
* vim-patch:babea52: runtime(gomod): add recommended indent options to ftpluginChristian Clason2024-07-17
| | | | | | | | closes: vim/vim#15264 https://github.com/vim/vim/commit/babea52f4d2d7cf466c5b383a067078392b153dc Co-authored-by: markmacode <code@mamo.aleeas.com>
* vim-patch:3e07d5a: runtime(go): add recommended indent options to ftpluginChristian Clason2024-07-17
| | | | | | | | related: vim/vim#15264 https://github.com/vim/vim/commit/3e07d5aef19ac34a61b9d58c2e0698351d392f52 Co-authored-by: markmacode <code@mamo.aleeas.com>
* vim-patch:6a54dcb: runtime(gdscript): add recommended indent options to ftpluginChristian Clason2024-07-17
| | | | | | | | related: vim/vim#15264 https://github.com/vim/vim/commit/6a54dcbbd68e70ee067348d1d9c1898befc56972 Co-authored-by: markmacode <code@mamo.aleeas.com>
* vim-patch:9.1.0592: runtime: filetype: Mediawiki files are not recognizedChristian Clason2024-07-17
| | | | | | | | | | | | | Problem: filetype: Mediawiki files are not recognized Solution: detect "*.mw" and "*.wiki" as mediawiki filetype, include basic syntax and filetype plugins. (AvidSeeker) closes: vim/vim#15266 https://github.com/vim/vim/commit/b5844104ab1259e061e023ea6259e4eb002e7170 Co-authored-by: AvidSeeker <avidseeker7@protonmail.com>
* vim-patch:9.1.0591: filetype: *.wl files are not recognizedChristian Clason2024-07-17
| | | | | | | | | | | | Problem: filetype: *.wl files are not recognized Solution: Detect '*.wl' files as Mathematica package files (Jonas Dujava) closes: vim/vim#15269 https://github.com/vim/vim/commit/c6d7dc039342fbe1cf432c7f8e7e391063de210b Co-authored-by: Jonas Dujava <jonas.dujava@gmail.com>
* fix(lsp): don't show codelens for buffers that don't support it (#29690)Riley Bruins2024-07-16
|
* fix(snippet): modify base indentation when there's actually whitespace (#29670)Maria José Solano2024-07-16
|
* fix(tohtml): support ranges againaltermo2024-07-16
|
* vim-patch:1cc4cae: runtime(typst): Add typst runtime filesChristian Clason2024-07-16
| | | | | | | | closes: vim/vim#15234 https://github.com/vim/vim/commit/1cc4cae961a7b49608ef7bd56837cc723d49db4d Co-authored-by: Gregory Anders <greg@gpanders.com>
* fix(tohtml): extmark text may be out of boundsaltermo2024-07-16
|
* vim-patch:df62c62: runtime(doc): grammar fixes in options.txt (#29729)zeertzjq2024-07-15
| | | | | | | closes: vim/vim#15265 https://github.com/vim/vim/commit/df62c62177bd4dffce880b7a5711594865090953 Co-authored-by: Dominique Pellé <dominique.pelle@gmail.com>
* docs(lpeg): merge upstream changesMaria José Solano2024-07-15
|
* docs: misc (#29622)dundargoc2024-07-15
| | | | Co-authored-by: Christian Clason <c.clason@uni-graz.at> Co-authored-by: zeertzjq <zeertzjq@outlook.com>
* vim-patch:9.1.0586: ocaml runtime files are outdatedChristian Clason2024-07-14
| | | | | | | | | | | | | Problem: ocaml runtime files are outdated Solution: sync those files with the upstream repo, detect a few more ocaml files (Yinzuo Jiang) closes: vim/vim#15260 https://github.com/vim/vim/commit/700cf8cfa1e926e2ba676203b3ad90c2c2083f1d Co-authored-by: Yinzuo Jiang <jiangyinzuo@foxmail.com>
* vim-patch:9.1.0583: filetype: *.pdf_tex files are not recognizedChristian Clason2024-07-14
| | | | | | | | | | | | | | | Problem: filetype: *.pdf_tex files are not recognized Solution: Detect '*.pdf_tex' files as tex filetype (Jonas Dujava) Those files are generated by inkscape, when exporting, see e.g. https://inkscape.org/doc/inkscape-man.html closes: vim/vim#15250 https://github.com/vim/vim/commit/28145e005d646cb0477aa26ef69d0f651a9f9d27 Co-authored-by: Jonas Dujava <jonas.dujava@gmail.com>
* vim-patch:27c5598: runtime(doc): Add hint how to load termdebug from vimrc ↵zeertzjq2024-07-14
| | | | | | | | | (#29704) fixes: vim/vim#15256 https://github.com/vim/vim/commit/27c55984def4c6ff7afc89958c90f6018c474b2c Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:9.1.0574: ex: wrong handling of commands after barzeertzjq2024-07-14
| | | | | | | | | | | | | | | | | Problem: ex: wrong handling of commands after bar Solution: for :append, :insert and :change use the text after the bar as input for those commands. This is what POSIX requests. (Mohamed Akram) See the POSIX Spec: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/ex.html#tag_20_40_13_03 Section 12.c closes: vim/vim#15229 https://github.com/vim/vim/commit/8c446da34998f6350911e07fbfd7932412c83185 Co-authored-by: Mohamed Akram <mohd.akram@outlook.com>
* 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>
* 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>
* 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.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: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.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.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)
* build(deps): drop unused bundled bash, python parsers and queriesChristian Clason2024-07-09
| | | | | | | | | | Problem: Neovim bundles treesitter parsers for bash and python but does not use them by default. This dilutes the messaging about the bundled parsers being required for functionality or reasonable out-of-the-box experience. It also increases the risk of query incompatibilities for no gain. Solution: Stop bundling bash and python parser and queries.
* fix(lua): change some vim.fn.expand() to vim.fs.normalize() (#29583)zeertzjq2024-07-09
| | | Unlike vim.fn.expand(), vim.fs.normalize() doesn't expand wildcards.
* vim-patch:d1c3698: runtime(doc): fix typo in :h ft-csv-syntax (#29619)zeertzjq2024-07-09
| | | | | closes: vim/vim#15179 https://github.com/vim/vim/commit/d1c369892d49775e3da502981d0d896c98592528
* vim-patch:ab03dd2: runtime(hlsplaylist): include hlsplaylist ftplugin fileChristian Clason2024-07-09
| | | | | | | | | | fixes: vim/vim#15156 closes: vim/vim#15162 https://github.com/vim/vim/commit/ab03dd2085a37a62864cbf8616ebd52b8bbc3f6b Co-authored-by: AvidSeeker <avidseeker7@protonmail.com> Co-authored-by: zeertzjq <zeertzjq@outlook.com>
* perf(filetype): skip contents check in `match()` if there is no contents ↵Evgeni Chasnovski2024-07-08
| | | | | | | | | | | | | | | | | | (#29596) Problem: `vim.filetype.match()` tries to match on contents even if there is no contents (empty buffer or `{''}` explicit contents). This results in extra avoidable execution duration for cases. It matters, for example, when trying to match filetype based solely on file name (which still needs `contents` or `buf` to properly match earlier in the code path). Solution: skip matching based solely on contents if it is `{''}`. This works because: - Matching solely on content is done after any user-configured `vim.filetype.add()` hooks. - All default matching on content might depend on supplied path *only* if there is non-empty content (like in `require('vim.filetype.detect').match_from_hashbang()`).
* vim-patch:f77a0e9: runtime(cmakecache): include cmakecache ftplugin fileChristian Clason2024-07-08
| | | | | | | | closes: vim/vim#15175 https://github.com/vim/vim/commit/f77a0e9f417d41a3c35de86a42a75d10b633f19a Co-authored-by: Riley Bruins <ribru17@hotmail.com>
generated by cgit (git 2.34.1) at 2025-06-26 02:18:38 +0000