vim-appimage: v9.1.0271-kstr0k-appimage
vim-appimage release v9.1.0271-kstr0k-appimage
Version Information:
GVim: v9.1.0271 - Vim git commit: 3c4d2e7 - glibc: 2.34
GitHub Actions Logfile
Downloads
This release provides the following Artifacts:
Changelog
- 9.1.0271: CI sound test aborts with undefined variable
- NSIS: Correctly distribute libsodium with the installer (#14422)
- 9.1.0270: a few minor issues to fix
- 9.1.0269: Test for TextChanged is still flaky with ASAN
- 9.1.0268: Two tests in test_filechanged.vim are slow
- 9.1.0267: File name entered in GUI dialog is ignored
- runtime: fix :compiler leaving behind a g:makeprg variable (#14414)
- runtime: Remove more fallback :CompilerSet definitions from compiler plugins (#14413)
- 9.1.0266: filetype: earthfile files are not recognized
- 9.1.0265: console dialog cannot save unnamed buffers
- runtime(doc): Fill in a few details regarding :enums (#14349)
- runtime: Remove fallback :CompilerSet definition from compiler plugins
- 9.1.0264: libgpm may delete some signal handlers
- runtime(java): Improve the matching of contextual keywords
- 9.1.0263: Vim9: Problem with lambda blocks in enums and classes
- 9.1.0262: Test for TextChanged is flaky with ASAN
- 9.1.0261: Vim9: protected class and funcrefs accessible outside the class
What's the difference between the GVim and the Vim AppImage?
- The GVim version includes Vim's GTK3 graphical user interface and other X11 features (including clipboard support). For a desktop system, you'll want the GVim AppImage.
- The GVim appimage only runs on systems with the X11 libraries installed (even if you try to run it outside X11, e.g. from
ssh
); for a server / headless environment, you're better off with the Vim AppImage.
Note: The images are based on Ubuntu 22.04 LTS ("jammy") and most likely won't work on older distributions.
Run it
Download the AppImage, make it executable, then run it as you would run Vim (including any optional CLI arguments):
URL='https://github.com/kstr0k/vim-appimage/releases/download/v9.1.0271/'
wget -O /tmp/gvim.appimage "$URL"/GVim-v9.1.0271.glibc2.34-x86_64.AppImage
chmod +x /tmp/gvim.appimage
/tmp/gvim.appimage
# alternatively, download the Vim AppImage
wget -O /tmp/vim.appimage "$URL"/Vim-v9.1.0271.glibc2.34-x86_64.AppImage
chmod +x /tmp/vim.appimage
/tmp/vim.appimage
You should now have a graphical vim running (if you have a graphical system and chose the GVim appimage) 😄
If you want "terminal" Vim (but with X11 and clipboard support), download the GVim appimage, create a symbolic link with any name starting with "vim..." (or even simply vim
), then run it through this symlink:
ln -s /tmp/gvim.appimage /tmp/vim.appimage
/tmp/vim.appimage
Finally, it's possible to extract the AppImage to a folder ("AppDir") and run vim / gvim directly from there, using the AppRun.extracted
script included in the AppImage. For frequent usage, this incurs less overhead and brings up vim faster than the AppImage (which internally auto-mounts its own "AppDir" on every run). Plus (compared to using distro packages) you still get the latest Vim. For example, for the GVim appimage:
cd /tmp; ./gvim.appimage --appimage-extract
mv squashfs-root ~/gvim.AppDir
ln -s ~/gvim.AppDir/AppRun.extracted ~/bin/gvim
ln -s ~/gvim.AppDir/AppRun.extracted ~/bin/vim
Interpreter interfaces
The Vim / GVim AppImage's are compiled with Vim interfaces for Perl 5.34, Python 3.8+, Ruby 3, and Lua 5.4 and built on Ubuntu 22.04 LTS (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.11.so
or similar (use the shell commandsudo 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.