Vim: v9.0.1811
Vim AppImage Release v9.0.1811
Version Information:
GVim: v9.0.1811 - Vim git commit: 85c3a5bc2 - glibc: 2.29
GitHub Actions Logfile
Downloads
This release provides the following Artifacts:
Changelog
- 9.0.1811: still some issues with term_debug test
- 9.0.1810: camel-case spelling has issues with digits
- 9.0.1809: termdebug test flayk
- 9.0.1808: termdebug: Typo in termdebug test
- 9.0.1807: runtime: crystal scripts not recognised
- runtime: Remove outdated scripts.vim comment (#12934)
- translation(it): updated Italian manpage
- 9.0.1806: Vim9: bogus error on export
- 9.0.1805: Vim9: problem compiling object method as function call arg
- 9.0.1804: Vim9: no support for private object methods
- 9.0.1803: runtime(filetype): Add norg language detection
- 9.0.1802: Multiline regex with Visual selection fails with virtual text
- 9.0.1801: Vim9 instanceof() fails in a def func
- 9.0.1800: Cursor position still wrong with 'showbreak' and virtual text
- 9.0.1799: Russian menu translation can be improved
- runtime: Distribute the editorconfig with vim (#12902)
- 9.0.1798: The 'syntax' option has no completion.
- 9.0.1797: Vimball/Visual Basic filetype detection conflict
- 9.0.1796: Vim9 problems with null_objects
- 9.0.1795: Indentation issues
- 9.0.1794: autoconf: not correctly detecing include dirs
- 9.0.1793: obsolete macros in configure script
- 9.0.1792: problem with gj/gk/gM and virtual text
- 9.0.1791: No tests for the termdebug plugin
- 9.0.1790: Redundant LSP Content-Type header
- translation(ua): Refine (synchronize with Neovim) (#12928)
- 9.0.1789: too early declaration of variable in pum_set_selected()
- 9.0.1788: C4090 warnings in strings.c
- runtime(typescript): Fix highlighting symbols after number literal (#12911)
- translation(ua): Update Ukrainian translation (#12916)
- translation(ir): Updated irish translation (#12918)
- runtime(todo): Update todo.txt to remove recently addressed issues (#12910)
- 9.0.1787: Cannot build with latest luajit
- runtime: configure keywordpg for some file types (#5566)
- runtime: Remove Brams name from a few more runtime files (#12780)
- runtime: Fix typos in various files
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.1811/GVim-v9.0.1811.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.1811/Vim-v9.0.1811.glibc2.29-x86_64.AppImage
chmod +x /tmp/vim.appimage
/tmp/vim.appimageThat'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.appimageThen 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.