Vim: v9.1.1382

Vim AppImage Release v9.1.1382

Version Information:
GVim: v9.1.1382 - Vim git commit: e62244f22 - glibc: 2.34

GitHub Actions Logfile

---

Downloads

This release provides the following Artifacts:

• 
• 

Changelog

• runtime(getscript): CI: failure on powershell
• 9.1.1382: if_ruby: unused compiler warnings from ruby internals
• runtime(getscript): check for network errors
• 9.1.1381: completion: cannot return to original text
• 9.1.1380: 'eventignorewin' only checked for current buffer
• runtime(java): Search type and method declarations with "&inc" and "&def"
• runtime(html): Optionally fold tags with the "expr" method
• runtime(tutor): improve tutor.vim plugin and filetype plugin
• runtime(sh): Update syntax, improve wildcard character class matching
• 9.1.1379: MS-Windows: error when running evim when space in path
• 9.1.1378: sign without text overwrites number option
• runtime(doc): clarify single/multibyte support for 'fillchars'
• 9.1.1377: patch v9.1.1370 causes some GTK warning messages
• runtime(lf): use syn iskeyword in syntax script
• 9.1.1376: quickfix dummy buffer may remain as dummy buffer
• 9.1.1375: [security]: possible heap UAF with quickfix dummy buffer
• CI: use deb822 style for llvm source
• runtime(doc): remove duplicate sentence in builtin.txt
• typo in comment in gui.c
• runtime(doc): update return types for builtin functions
• 9.1.1374: completion: 'smartcase' not respected when filtering matches
• 9.1.1373: 'completeopt' checking logic can be simplified
• git: ignore more style changes from v9.1.1371 and v9.1.1372
• 9.1.1372: style: braces issues in various files
• 9.1.1371: style: indentation and brace issues in insexpand.c
• 9.1.1370: CI Tests favor GTK2 over GTK3
• 9.1.1369: configure still using autoconf 2.71
• 9.1.1368: GTK3 and GTK4 will drop numeric cursor support.
• 9.1.1367: too many strlen() calls in gui.c

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 22.04 LTS jammy. 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.1.1382/GVim-v9.1.1382.glibc2.34-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.1.1382/Vim-v9.1.1382.glibc2.34-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.

Interpreter interfaces

The Vim / GVim AppImage's are compiled with Vim interfaces for Perl 5.30, Python 3.8+, Ruby 2.7, and Lua 5.3 and built on Ubuntu 22.04 ("jammy"). If your system runs this exact version of Ubuntu (or some compatible flavor), and has the corresponding interpreter packages installed, they will work just as in a native Vim distro package.

Otherwise,

• for Python 3: install it on your system. In Vim, set pythonthreedll=libpython3.10.so or similar (use the shell command sudo ldconfig -p | grep libpython3 to find the library name). See :help +python3/dyn-stable.
• for any interpreter other than Python: the appimage embeds a version of its runtime. The Vim interface will work (see e.g. :help lua, :help perl, :help ruby), however it won't have access to the default / base modules (with various effects for each interpreter). Any interpreter modules (base and add-ons) installed on your system will be ignored and are most likely not compatible with the runtime version embedded in the AppImage.