vim-appimage: v9.1.0296-kstr0k-appimage

vim-appimage release v9.1.0296-kstr0k-appimage

Version Information:
GVim: v9.1.0296 - Vim git commit: 7a27c10 - glibc: 2.34

GitHub Actions Logfile

---

Downloads

This release provides the following Artifacts:

• 
• 

Changelog

• 9.1.0296: regexp: engines do not handle case-folding well
• 9.1.0295: filetype: pip config files are not recognized
• 9.1.0294: Text height function does not respect it's argument
• 9.1.0293: filetype: lxqt config files are not recognized
• 9.1.0292: filetype: XDG mimeapps.list file is not recognized
• 9.1.0291: filetype: libreoffice config files are not recognized
• 9.1.0290: filetype: xilinx files are not recognized
• 9.1.0289: filetype: some TeX files are not recognized
• 9.1.0288: MS-Windows: compiler warning for size_t to int conversion
• 9.1.0287: Vim9: comment may be treated as heredoc start
• 9.1.0286: Vim9: E1027 with defcompile for abstract methods
• 9.1.0285: Still problems with cursor position for CTRL-D/U
• runtime(compiler): fix inaccuracies in pandoc compiler (#14467)
• 9.1.0284: make testclean is not able to delete failed screendumps
• runtime(vim): Update base-syntax, no curly-brace names in Vim9 script (#14466)
• 9.1.0282: Several small issues in doc and tests

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.0296/'
wget -O /tmp/gvim.appimage "$URL"/GVim-v9.1.0296.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.0296.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 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.

vim-appimage: v9.1.0282-kstr0k-appimage

vim-appimage release v9.1.0282-kstr0k-appimage

Version Information:
GVim: v9.1.0282 - Vim git commit: 34f00dd - glibc: 2.34

GitHub Actions Logfile

---

Downloads

This release provides the following Artifacts:

• 
• 

Changelog

• 9.1.0282: Finding highlighting attributes is inefficient
• 9.1.0281: CI: fails Test_compiler_completion
• runtime(cuda): Update cuda keywords, remove uncommonly used enumeration constants
• 9.1.0280: several issues with 'smoothscroll' support
• 9.1.0279: filetype: roc files are not recognized
• 9.1.0278: filetype: zathurarc files not recognized
• 9.1.0277: Cannot highlight the Command-line
• 9.1.0276: No pandoc syntax support
• 9.1.0275: filetype: R history files are not recognized

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.0282/'
wget -O /tmp/gvim.appimage "$URL"/GVim-v9.1.0282.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.0282.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 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.

vim-appimage: v9.1.0274-kstr0k-appimage

vim-appimage release v9.1.0274-kstr0k-appimage

Version Information:
GVim: v9.1.0274 - Vim git commit: aca8f55 - glibc: 2.34

GitHub Actions Logfile

---

Downloads

This release provides the following Artifacts:

• 
• 

Changelog

• 9.1.0274: MS-Windows: a few compiler warnings
• 9.1.0273: filetype: keymap files are not recognized
• 9.1.0272: autocmd may change cwd after :tcd and :lcd
• runtime(vim): Update syntax generator, autocmd event list parsing
• runtime(doc): Normalise builtin-function optional parameter formatting

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.0274/'
wget -O /tmp/gvim.appimage "$URL"/GVim-v9.1.0274.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.0274.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 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.

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 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.

vim-appimage: v9.1.0260-kstr0k-appimage

vim-appimage release v9.1.0260-kstr0k-appimage

Version Information:
GVim: v9.1.0260 - Vim git commit: bd28cae - glibc: 2.34

GitHub Actions Logfile

---

Downloads

This release provides the following Artifacts:

• 
• 

Changelog

• 9.1.0260: Problems with "zb" and scrolling to new topline with 'smoothscroll'
• runtime(netrw): filetype not detected when editing remote files
• runtime(doc): sort filetype.txt in the alphabetical order (#14395)
• 9.1.0259: Normal mode TextChanged isn't tested properly

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.0260/'
wget -O /tmp/gvim.appimage "$URL"/GVim-v9.1.0260.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.0260.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 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.

vim-appimage: v9.1.0258-kstr0k-appimage

vim-appimage release v9.1.0258-kstr0k-appimage

Version Information:
GVim: v9.1.0258 - Vim git commit: cb204e688 - glibc: 2.34

GitHub Actions Logfile

---

Downloads

This release provides the following Artifacts:

• 
• 

Changelog

• 9.1.0258: half-page scrolling broke backward compatibility
• 9.1.0257: Vim9: :call may not find imported class members
• 9.1.0256: Finding autocmd events is inefficient
• 9.1.0255: Vim9: no indication of script nr in stack trace of classes
• 9.1.0254: [security]: Heap buffer overflow when calling complete_add() in 'cfu'
• 9.1.0253: filetype: typespec files are not recognized
• runtime(yaml): improve syntax highlighting for YAML

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.0258/'
wget -O /tmp/gvim.appimage "$URL"/GVim-v9.1.0258.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.0258.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 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.

vim-appimage: v9.1.0252-kstr0k-appimage

vim-appimage release v9.1.0252-kstr0k-appimage

Version Information:
GVim: v9.1.0252 - Vim git commit: 2ed5a11b1 - glibc: 2.34

GitHub Actions Logfile

---

Downloads

This release provides the following Artifacts:

• 
• 

Changelog

• 9.1.0252: Vim9: segfault with static in super class
• 9.1.0251: Filetype test fails
• runtime(sshconfig,sshdconfig): update syntax (#14351)
• 9.1.0250: filetype: ldscripts cannot be recognized
• 9.1.0249: filetype: rock_manifest and config.ld files are not recognized
• 9.1.0248: filetype: yarn lock files are not recognized
• 9.1.0247: filetype: bundle config files are not recognized
• 9.1.0246: filetype: fontconfig files are not recognized
• 9.1.0245: filetype: zsh theme, history and zunit files are not recognized
• 9.1.0244: filetype: bash history files are not recognized
• 9.1.0243: filetype: netrw history file is not recognized
• 9.1.0242: filetype: octave history files are not recognized
• 9.1.0241: filetype: mysql history files are not recognized
• 9.1.0240: filetype: some python tools config files are not recognized
• 9.1.0239: filetype: gnuplot history files are not recognised
• 9.1.0238: filetype: jupyterlab and sublime config are not recognized
• 9.1.0237: filetype: mplstyle files are not recognized
• 9.1.0236: filetype: texlua files are not recognized
• 9.1.0235: filetype: supertux files are not recognized
• 9.1.0234: filetype: support for Intel HEX files is lacking
• 9.1.0233: Vim9: string() output of enum is problematic
• 9.1.0232: Conceal test fails when rightleft feature is disabled
• 9.1.0231: Filetype may be undetected when SwapExists sets ft in other buf
• 9.1.0230: TextChanged autocommand not triggered under some circumstances
• runtime(compilers): ensure compiler! sets global options (#14336)
• runtime(vim): Distinguish Vim9 builtin object methods from namesake builtin functions (#14348)
• runtime(pamconf): add support for Debian specific @includes
• 9.1.0229: Error E877 is not translated
• NSIS: fix path of uganda.nsis.txt in german.nsi file (#14331)

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.0252/'
wget -O /tmp/gvim.appimage "$URL"/GVim-v9.1.0252.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.0252.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 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.

vim-appimage: v9.1.0228-kstr0k-appimage

Custom vim-appimage release v9.1.0228

Version Information:
GVim: v9.1.0228 - Vim git commit: ad493ef3e - glibc: 2.34

GitHub Actions Logfile

---

Downloads

This release provides the following Artifacts:

• 
• 

Changelog

• 9.1.0228: Two unrelated things are tested by a single test
• runtime(doc): Improve docs for empty(), len(), and string() on objects
• 9.1.0227: Recording may still be wrong in Select mode
• 9.1.0226: Not able to assign enum values to an enum static variable

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.0228/'
wget -O /tmp/gvim.appimage "$URL"/GVim-v9.1.0228.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.0228.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

Optional libraries

This Vim build was configured with Perl 5.34, Python 3.8+, Ruby 3, and Lua 5.4 interfaces and was compiled on Ubuntu 22.04. If your system runs this exact version of Ubuntu (or some compatible flavor), and has the corresponding interpreter packages installed, they will work like with a native Vim distro package. Otherwise,

• for Python 3, set pythonthreedll=libpython3.11.so or similar (use the shell command locate '*libpython3*.so')
• the other interpreter interfaces will work (see e.g. :help perl), because the appimage embeds their runtime libraries (unlike for Python); however they will not be able to access their default / base modules (which may or may not matter).

vim-appimage: v9.1.0225

Initial release after fork from https://github.com/vim/vim-appimage