Vim: v9.0.1777

Vim AppImage Release v9.0.1777

Version Information:
GVim: v9.0.1777 - Vim git commit: 75dc1ed1a - glibc: 2.29

GitHub Actions Logfile

---

Downloads

This release provides the following Artifacts:

• 
• 

Changelog

• 9.0.1778: if_py_both: code-style issue
• 9.0.1777: patch 9.0.1771 causes problems
• runtime(sdc): Add underscore to sdc flags in syntax file (#6201)
• Runtime(javascript): add new document properties to completion file
• runtime(haskell): Add single quote to `iskeyword` in ftplugin (#8191)
• runtime(spec): ftplugin: Revert change dropping <SID> from SpecChangelog (#9032)
• runtime(css): Update pseudo-classes in syntax script (#11595)
• runtime(lua): fix lua indentation of non-lowercase "keywords" (#11759)
• runtime(javascript): fix default link of javaScriptNumber in syntax file (#11788)
• 9.0.1776: No support for stable Python 3 ABI
• 9.0.1775: Wrong comparison in vim9type.c
• 9.0.1774: no support for custom cmdline completion
• 9.0.1773: cannot distinguish Forth and Fortran *.f files
• runtime(lua): indent curly bracket followed by line comment (#12306)
• 9.0.1772: Cursor may be adjusted in 'splitkeep'ed windows
• runtime(rust): fix rust indent (#12542)
• runtime(man): remove backslashes in man pages using Vim script (#12557)
• 9.0.1771: regex: combining chars in collections not handled
• 9.0.1770: lines disappear when modifying chars before virt text
• runtime(termdebug): refactor error printing (#12856)
• runtime(termdebug): re-indent lines (#12857)
• 9.0.1769: executable() ignoring symlinks on Windows
• Runtime(termdebug): Add support to view local and argument variables
• Runtime: Add nixInherit matcher in nix.vim syntax
• 9.0.1768: Runtime: no support for bicep files
• 9.0.1767: '.-' no allowed in highlight group names
• 9.0.1766: Runtime: Missing QML support
• 9.0.1765: Error when cross-compiling Vim
• 9.0.1764: CI: label should not be set on all yml files
• Translation: also update ru.cp1251.po file after 6cc8bc836616e9b0
• 9.0.1763: crash when passing invalid buffer to undotree()
• 9.0.1762: Not able to get the virtual text property
• 9.0.1761: g<kEnd> behaves different from g<end>
• 9.0.1760: vim9 class problem with new() constructor
• Translation: Russian PO file updated to Vim version 9.0.1757 (#12864)
• 9.0.1759: Visual highlight not working with cursor at end of screen line
• 9.0.1758: vim9 no class identifiers in stack dumps

What is the Difference between the GVim and the Vim Appimage?

The difference between the GVim and Vim Appimage is, that the GVim version includes a graphical User Interface (GTK3) and other X11 features like clipboard handling. That means, for proper clipboard support, you'll need the GVim Appimage, but you can only run this on a system that has the X11 libraries installed.

For a Server or headless environment, you are probably be better with the Vim version.

Note: The image is based on Ubuntu 20.04 LTS focal. It most likely won't work on older distributions.

Run it

Download the AppImage, make it executable then you can just run it:

wget -O /tmp/gvim.appimage https://github.com/vim/vim-appimage/releases/download/v9.0.1777/GVim-v9.0.1777.glibc2.29-x86_64.AppImage
chmod +x /tmp/gvim.appimage
/tmp/gvim.appimage
# alternatively, download the Vim Appimage
wget -O /tmp/vim.appimage https://github.com/vim/vim-appimage/releases/download/v9.0.1777/Vim-v9.0.1777.glibc2.29-x86_64.AppImage
chmod +x /tmp/vim.appimage
/tmp/vim.appimage

That's all, you should have a graphical vim now running (if you have a graphical system running) 😄

If you want a terminal Vim (with X11 and clipboard feature enabled), just create a symbolic link with a name starting with "vim". Like:

ln -s /tmp/gvim.appimage /tmp/vim.appimage

Then execute vim.appimage to get a terminal Vim.

More Information

If you need a dynamic interface to Perl, Python2, Python3.8, Ruby or Lua make sure your system provides the needed dynamic libraries (e.g. libperlX, libpython2.7 libpython3X liblua5X and librubyX) as those are not distributed together with the image to not make the image too large.

However, Vim will work without those libraries, but some plugins might need those additional dependencies. This means, those interpreters have to be installed in addition to Vim. Without it Vim won't be able to use those dynamic interfaces.