Giter Club home page Giter Club logo

vim-appimage's Introduction

Vim The editor

Github Build status Appveyor Build status Cirrus Build Status Coverage Status Coverity Scan Debian CI Packages Fossies codespell report

If you find a bug or want to discuss the best way to add a new feature, please open an issue. If you have a question or want to discuss the best way to do something with Vim, you can use StackExchange or one of the Maillists.

What is Vim?

Vim is a greatly improved version of the good old UNIX editor Vi. Many new features have been added: multi-level undo, syntax highlighting, command line history, on-line help, spell checking, filename completion, block operations, script language, etc. There is also a Graphical User Interface (GUI) available. Still, Vi compatibility is maintained, those who have Vi "in the fingers" will feel at home. See runtime/doc/vi_diff.txt for differences with Vi.

This editor is very useful for editing programs and other plain text files. All commands are given with normal keyboard characters, so those who can type with ten fingers can work very fast. Additionally, function keys can be mapped to commands by the user, and the mouse can be used.

Vim runs under MS-Windows (7, 8, 10, 11), macOS, Haiku, VMS and almost all flavours of UNIX. Porting to other systems should not be very difficult. Older versions of Vim run on MS-DOS, MS-Windows 95/98/Me/NT/2000/XP/Vista, Amiga DOS, Atari MiNT, BeOS, RISC OS and OS/2. These are no longer maintained.

For Vim9 script see README_VIM9.

Distribution

You can often use your favorite package manager to install Vim. On Mac and Linux a small version of Vim is pre-installed, you still need to install Vim if you want more features.

There are separate distributions for Unix, PC, Amiga and some other systems. This README.md file comes with the runtime archive. It includes the documentation, syntax files and other files that are used at runtime. To run Vim you must get either one of the binary archives or a source archive. Which one you need depends on the system you want to run it on and whether you want or must compile it yourself. Check https://www.vim.org/download.php for an overview of currently available distributions.

Some popular places to get the latest Vim:

Compiling

If you obtained a binary distribution you don't need to compile Vim. If you obtained a source distribution, all the stuff for compiling Vim is in the src directory. See src/INSTALL for instructions.

Installation

See one of these files for system-specific instructions. Either in the READMEdir directory (in the repository) or the top directory (if you unpack an archive):

README_ami.txt		Amiga
README_unix.txt		Unix
README_dos.txt		MS-DOS and MS-Windows
README_mac.txt		Macintosh
README_haiku.txt	Haiku
README_vms.txt		VMS

There are other README_*.txt files, depending on the distribution you used.

Documentation

The Vim tutor is a one hour training course for beginners. Often it can be started as vimtutor. See :help tutor for more information.

The best is to use :help in Vim. If you don't have an executable yet, read runtime/doc/help.txt. It contains pointers to the other documentation files. The User Manual reads like a book and is recommended to learn to use Vim. See :help user-manual.

Copying

Vim is Charityware. You can use and copy it as much as you like, but you are encouraged to make a donation to help orphans in Uganda. Please read the file runtime/doc/uganda.txt for details (do :help uganda inside Vim).

Summary of the license: There are no restrictions on using or distributing an unmodified copy of Vim. Parts of Vim may also be distributed, but the license text must always be included. For modified versions, a few restrictions apply. The license is GPL compatible, you may compile Vim with GPL libraries and distribute it.

Sponsoring

Fixing bugs and adding new features takes a lot of time and effort. To show your appreciation for the work and motivate developers to continue working on Vim please send a donation.

The money you donated will be mainly used to help children in Uganda. See runtime/doc/uganda.txt. But at the same time donations increase the development team motivation to keep working on Vim!

For the most recent information about sponsoring look on the Vim web site: https://www.vim.org/sponsor/

Contributing

If you would like to help make Vim better, see the CONTRIBUTING.md file.

Information

If you are on macOS, you can use MacVim.

The latest news about Vim can be found on the Vim home page: https://www.vim.org/

If you have problems, have a look at the Vim documentation or tips: https://www.vim.org/docs.php https://vim.fandom.com/wiki/Vim_Tips_Wiki

If you still have problems or any other questions, use one of the mailing lists to discuss them with Vim users and developers: https://www.vim.org/maillist.php

If nothing else works, report bugs directly to the vim-dev mailing list: <[email protected]>

Main author

Most of Vim was created by Bram Moolenaar <[email protected]> Bram-Moolenaar

Send any other comments, patches, flowers and suggestions to the vim-dev mailing list: <[email protected]>

This is README.md for version 9.1 of Vim: Vi IMproved.

vim-appimage's People

Contributors

chrisbra avatar dependabot[bot] avatar fusion809 avatar github-actions[bot] avatar ichizok avatar mralusw avatar rakus avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

vim-appimage's Issues

Error libgdk_pixbuf-2.0.so.0

Wonderful effort & had fun with it, Until, I attempted to run it on GUI & internet less server & I get libgdk_pixbuf-2.0.so.0.

So, I followed the instruction &:
Arch$ ln -s GVim-v8.1.1209.glibc2.15-x86_64.AppImage vim.appimage
Arch$ ls -l vim.appimage
lrwxrwxrwx 1 ny11559 domain users 40 May 1 18:22 vim.appimage -> GVim-v8.1.1209.glibc2.15-x86_64.AppImage
Arch$ vim.appimage
vim.appimage: command not found
/Arch$ chmod +x vim.appimage
chmod: cannot operate on dangling symlink 'vim.appimage'

Also, I attempted to copy to name vim.appimage:
but got
vim: error while loading shared libraries: libgdk_pixbuf-2.0.so.0: cannot open shared object file: No such file or directory

What am I doing wrong?
Thank you much,

Create a console only appimage too

Hi!

I try to use the appimage on a Debian 10.8 server without X window, but it is always complaining about missing files libXt.so.6 and libXcomposite.so.1. (the first file is in the libxt6 package, but for the second file it want to install a lot of gtk and X depentent packages).

Can you provide an appimage without the X/gtk depencencies please?

E837: This Vim cannot execute :py3 after using :python

Hi,

I seem to have an issue with compiled python support of the AppImage.
I get the following error (triggered by the ultisnips plugin)

E837: This Vim cannot execute :py3 after using :python

I'm running Debian 10.
Note: I'm assuming it's a problem with the appimage, as the error does not appear with the distro-bundled vim, or an nvim appimage I tried.

Thanks and regards,

Ryan

glib version issues on both images while system has GNU libc 2.17

You have provided two app images, one with glib 2.14 and another with glib 2.29. Both of them fail to run on my Red Hat 7 system with glib 2.17. For 2.14 version, not sure if the errors are coming from the gvim installed on the system. But shouldn't AppImage be running from its own mount?

$ ./GVim-v9.1.0080.glibc2.29-x86_64.AppImage 
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/gvim)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/gvim)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libgtk-3.so.0)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libthai.so.0: version `LIBTHAI_0.1.25' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libpango-1.0.so.0)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libcairo.so.2)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libgio-2.0.so.0)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libglib-2.0.so.0)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.30' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libselinux.so.1)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libsodium.so.23)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/liblua5.3.so.0)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libperl.so.5.30)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libperl.so.5.30)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libpython2.7.so.1.0)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libpython2.7.so.1.0)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libtcl8.6.so)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libruby-2.7.so.2.7)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libruby-2.7.so.2.7)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libruby-2.7.so.2.7)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libruby-2.7.so.2.7)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libwayland-cursor.so.0)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libpixman-1.so.0)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libpng16.so.16)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libz.so.1: version `ZLIB_1.2.9' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libpng16.so.16)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libmount.so.1)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libcrypt.so.1)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libblkid.so.1)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libsystemd.so.0)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libsystemd.so.0)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.26' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libsystemd.so.0)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.30' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libsystemd.so.0)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libsystemd.so.0)
/tmp/.mount_GVim-vlAJbVm/usr/bin/gvim: /lib64/libgpg-error.so.0: no version information available (required by /tmp/.mount_GVim-vlAJbVm/usr/bin/../lib/libgcrypt.so.20)

$ ./GVim-v9.0.1413.glibc2.14-x86_64.AppImage 
gvim: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_GVim-vQqmCx6/usr/lib/x86_64-linux-gnu/libsodium.so.23)
gvim: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_GVim-vQqmCx6/usr/lib/x86_64-linux-gnu/libruby-2.5.so.2.5)
gvim: /lib64/libz.so.1: version `ZLIB_1.2.9' not found (required by /tmp/.mount_GVim-vQqmCx6/usr/lib/x86_64-linux-gnu/libpng16.so.16)
gvim: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_GVim-vQqmCx6/usr/lib/x86_64-linux-gnu/libmount.so.1)
gvim: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_GVim-vQqmCx6/usr/lib/x86_64-linux-gnu/libcrypt.so.1)
gvim: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_GVim-vQqmCx6/usr/lib/x86_64-linux-gnu/libblkid.so.1)
gvim: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_GVim-vQqmCx6/usr/lib/x86_64-linux-gnu/libsystemd.so.0)
gvim: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by /tmp/.mount_GVim-vQqmCx6/usr/lib/x86_64-linux-gnu/libsystemd.so.0)
gvim: /lib64/libgpg-error.so.0: no version information available (required by /tmp/.mount_GVim-vQqmCx6/usr/lib/x86_64-linux-gnu/libgcrypt.so.20)

$ uname -a
Linux host 3.10.0-1160.105.1.el7.x86_64 #1 SMP x86_64 x86_64 x86_64 GNU/Linux

$ gvim --version
VIM - Vi IMproved 7.4 (2013 Aug 10)
Included patches: 1-207, 209-629
Modified by <[email protected]>
Compiled by <[email protected]>
Huge version with GTK2 GUI.  Features included (+) or not (-):
+acl             +farsi           +mouse_netterm   +syntax
+arabic          +file_in_path    +mouse_sgr       +tag_binary
+autocmd         +find_in_path    -mouse_sysmouse  +tag_old_static
+balloon_eval    +float           +mouse_urxvt     -tag_any_white
+browse          +folding         +mouse_xterm     -tcl
++builtin_terms  -footer          +multi_byte      +terminfo
+byte_offset     +fork()          +multi_lang      +termresponse
+cindent         +gettext         -mzscheme        +textobjects
+clientserver    -hangul_input    +netbeans_intg   +title
+clipboard       +iconv           +path_extra      +toolbar
+cmdline_compl   +insert_expand   +perl            +user_commands
+cmdline_hist    +jumplist        +persistent_undo +vertsplit
+cmdline_info    +keymap          +postscript      +virtualedit
+comments        +langmap         +printer         +visual
+conceal         +libcall         +profile         +visualextra
+cryptv          +linebreak       +python/dyn      +viminfo
+cscope          +lispindent      -python3         +vreplace
+cursorbind      +listcmds        +quickfix        +wildignore
+cursorshape     +localmap        +reltime         +wildmenu
+dialog_con_gui  -lua             +rightleft       +windows
+diff            +menu            +ruby/dyn        +writebackup
+digraphs        +mksession       +scrollbind      +X11
+dnd             +modify_fname    +signs           -xfontset
-ebcdic          +mouse           +smartindent     +xim
+emacs_tags      +mouseshape      -sniff           +xsmp_interact
+eval            +mouse_dec       +startuptime     +xterm_clipboard
+ex_extra        +mouse_gpm       +statusline      -xterm_save
+extra_search    -mouse_jsbterm   -sun_workshop    +xpm
   system vimrc file: "/etc/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "/etc/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/etc"
 f-b for $VIMRUNTIME: "/usr/share/vim/vim74"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng15 -I/usr/include/uuid -I/usr/include/pixman-1 -I/usr/include/libdrm     -O2 -g -pipe -Wall -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -mtune=generic -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D__linux__ -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -L. -Wl,-z,relro -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,--enable-new-dtags -Wl,-rpath,/usr/lib64/perl5/CORE  -Wl,-z,relro  -L/usr/local/lib -Wl,--as-needed -o vim   -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfontconfig -lgobject-2.0 -lglib-2.0 -lfreetype   -lSM -lICE -lXpm -lXt -lX11 -lSM -lICE  -lm -lnsl  -lselinux  -lncurses -lacl -lattr -lgpm -ldl   -Wl,--enable-new-dtags -Wl,-rpath,/usr/lib64/perl5/CORE  -fstack-protector  -L/usr/lib64/perl5/CORE -lperl -lresolv -lnsl -ldl -lm -lcrypt -lutil -lpthread -lc

Runtime path doesn't include help tags.

As of the AppImage for version v9.1.0610, the tags file in vim91/doc is missing, which means most help commands will fail.

The command works in the AppImages for versions v9.1.0608 and below. The issue appears to be caused by v9.1.0609, though I am not totally how.

gvim appimage: run vim if called as vim; work with extracted appimage

The GVim appimage always tries to run as gvim (even if called through a symlink named vim, and even if no X11 $DISPLAY is set). This is because AppRun.wrapped tries first

test -L "${HERE}/usr/bin/gvim" && exec "${HERE}/usr/bin/gvim" "${@+"$@"}"

Cutting through all the cruft probably generated by linuxdeploy (two bash exec's even though no bash features are needed, the "${@+"$@"}" workaround for 1990's Bash), here's a simpler AppRun that works as vim when the appimage is called as vim. As a bonus this AppRun works when symlinked from an extracted appimage (hidden option gvim.appimage --appimage-extract available with all appimages)

#!/bin/sh
set -ue
: "${ARGV0:=$0}"  # run without AppImage too
this_dir=$(readlink -f "$0")
this_dir=${this_dir%/*}  # empty for '/'
[ -r "$this_dir"/apprun-hooks/linuxdeploy-plugin-gtk.sh ] &&
  .  "$this_dir"/apprun-hooks/linuxdeploy-plugin-gtk.sh
VIMRUNTIME=${this_dir}/usr/share/vim/vim91; export VIMRUNTIME
test -x "${this_dir}/usr/bin/gvim" || ARGV0=/vim
case "${ARGV0##*/}" in
  (vim*) set -- "${this_dir}/usr/bin/vim"  "$@" ;;
  (*)    set -- "${this_dir}/usr/bin/gvim" "$@" ;;
esac
unset ARGV0
exec "$@"

(note: updated after further investigation & #68)

libcrypt.so.1: version `XCRYPT_2.0' not found (on debian bullseye, ubuntu 22.10, mageia 9)

When using vim appimage (or gvim with a link named vim) I have problem with perlcritic, perltidy and PLS.
these programs seems to crash when launched by vim-ale or coc.nvim
when launching one of these program from the terminal:

:terminal
shad@abbadon:~$ perltidy --version

I've got an error about `XCRYPT_2.0' not found

The problem does not occur with the system installed vim.
The problem occurs on several distribs:

Mageia :

system installed:

lib64xcrypt1-4.4.33-3.mga9
vim-enhanced-9.0.1314-1.mga9

Error message in vim:

/usr/bin/perl: /tmp/.mount_Vim-v9w1hgcd/usr/lib/x86_64-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /lib64/libperl.so.5.36

Ubuntu kinetic (22.10):

system installed lib:

ii libcrypt1:amd64 1:4.4.28-2 amd64 libcrypt shared library
ii vim 2:9.0.0242-1ubuntu1 amd64 Vi IMproved - enhanced vi editor

Error message in vim:

/usr/bin/perl: /tmp/.mount_vimwpVdR9/usr/lib/x86_64-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /usr/bin/perl)

debian bullseye

system installed lib:

ii libcrypt1:amd64 1:4.4.18-4 amd64 libcrypt shared library
ii vim 2:8.2.2434-3+deb11u1 amd64 Vi IMproved - enhanced vi editor

Error message in vim:

/usr/bin/perl: /tmp/.mount_vim.apwcbqgJ/usr/lib/x86_64-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /usr/bin/perl)

appimage tested:

  • GVim-v9.0.1314.glibc2.15-x86_64.AppImage
  • Vim-v9.0.1403.glibc2.14-x86_64.AppImage
  • GVim-v9.0.1403.glibc2.14-x86_64.AppImage

the workaround I found is to preload the libcrypt of the system in my ~/.vimrc for exemple, for debian and ubuntu, I've added the line

let $LD_PRELOAD="/lib/x86_64-linux-gnu/libcrypt.so.1.1.0"

It allowed perltidy, perlcritic and PLS to work without visible problems (from terminal or vim-ale/coc.nvim) but I don't know if this preloading will have negative side effect of some sort.

Current working directory not correctly set when running inside Docker Container/FUSEless system

Dear maintainer(s),

When running the Vm AppImage inside a Docker container, the current working directory is replaced with AppImages internal path.
Breaking relative file paths when used as arguments with Vim.

Docker supports no Fuse so the AppImage must be run with --appimage-extract-and-run which extracts the AppImage and runs it.
This works fine so far except that the CWD where Vim was called from is not kept and is changed to the extracted AppImage dir.

Having this setup:

root@763fe0d67d0c:~# ls
Vim-v9.0.1833.glibc2.29-x86_64.AppImage  file.txt

root@763fe0d67d0c:~# pwd
/root

# Now running Vim AppImage
root@763fe0d67d0c:~# ./Vim-v9.0.1833.glibc2.29-x86_64.AppImage --appimage-extract-and-run ./file.txt

Now when executing Vim :pwd returns /tmp/appimage_extracted_0d7da17d27cad8d507bf02564b76c922/usr and not the expected /root
This leads to the file ./file.txt not being found, making editing with Vim inside a container hard to use as all relative paths are non working.

Looking into vim.start.sh it seems that the cd'ing back into $OWD is trying to fix that, but in my testing it was always unset.

Strangely with nvim and tmux AppImages it worked fine without any issues, they both seem to have completely different startup procedure.

For reference:

Vim AppImage is extremely useful for debugging (inside) Docker containers, so this would be very nice if it could be fixed.

Thank you for your effort :)

Vim failes to find runtime files

While the new AppImage version v9.0.1876 fixes #51, I encountered a new issue, it probably is related to the switch to the linuxdeploy built.

Fuse:

$ ./Vim.AppImage 
Error detected while processing /usr/share/vim/vimrc:
line   25:
E484: Can't open file /usr/share/vim/syntax/syntax.vim
failed to load colors/lists/default.vim
failed to load colors/lists/default.vim
Press ENTER or type command to continue
$ ./Vim.AppImage --clean
E1187: Failed to source defaults.vim
Press ENTER or type command to continue

Docker:

root@8fc912ed7e38:/# ./Vim.AppImage --appimage-extract-and-run
E1187: Failed to source defaults.vim
Press ENTER or type command to continue

Looks like Vim uses absolute path for some runtime files, which are not available.
The issue happens on both Fuse system as well as Fuse'less systems.

:set runtimepath?
runtimepath=/usr/share/vim/vimfiles,/usr/share/vim,/usr/share/vim/vimfiles/after

GVim lacks all GUI elements?

When launching GVim-v9.0.1885.glibc2.29-x86_64.AppImage, it lacks all GUI elements, such as: the toolbar, menu, and other components.

GVim

Upgrade to Python 3.8

Hi, thanks for this appimage.

Correct me if I'm wrong. Currently, this package is buildt with Python 3.4, which means we will unable to get python3 support if our python version is more than 3.4.

According to the release schedule

Python 3.4 has now reached its end-of-life and has been retired. No more releases will be made.

Would it be possible to upgrade to latest Python 3.8?

incorrect vim 9 runtime path

When launching the v9.0.0049 appimage,

Error detected while processing /homes/arigathub/.vimrc:
line   48:
E484: Can't open file /tmp/.mount_vimt91IGY/usr/share/vim/vim82/syntax/syntax.vim

The runtime path needs to be updated to vim90

What python version does this appimage link to ?

I downloaded this appimage in Ubuntu 22.04 and found that only python2 was available, while has('python3') returned 0.

Is this a version mismatch problem ?

The python3 package version in ubuntu 22.04 is 3.8.10

Unable to open files on command line

Thanks for providing the appimage of Vim. This is very helpful to work with a recent Vim version on my very old Ubuntu at work.
I'm having some trouble starting Vim on command line with a file as argument. For example $PWD is $HOME and I issue ~/bin/GVim-v8.1.0139-gita8a60d0c6-glibc2.15.glibc2.15-x86_64.AppImage .bashrc Vim will open a file in /tmp/.mount_qMpnvg/usr/.bashrc instead of $HOME/.bashrc. I tried to add -c "cd $PWD" which has no effect as it is executed after reading the file. Adding --cmd "cd $PWD" does not work because in this case the runtimepath variable contains wrong directories (not absolute paths) and the distributed configuration is not found.

Any ideas how to get this running?

Provide update information

The AppImage format support delta updates using zsync files. For this to work an update information string must be passed when the AppImage is being built, like this:

appimagetool AppDir -u "gh-releases-zsync|vim|vim-appimage|latest|GVim-*x86_64.AppImage.zsync"

A zsync file will be generated next to the AppImage file, both file must be published as release artifacts.

Please check:

Link to latest stable

Is there a way to have a link to download the latest stable release?
I want to have a script installing the latest version.
Thanks!

Doesn't find correct terminfo entry

When starting vim from this appimage (version 8.1.2135) I get the following error:

E558: Terminal entry not found in terminfo
'tmux-256color' not known. Available builtin terminals are:
    builtin_gui
    builtin_amiga
    builtin_beos-ansi
    builtin_ansi
    builtin_pcansi
    builtin_win32
    builtin_vt320
    builtin_vt52
    builtin_xterm
    builtin_iris-ansi
    builtin_debug
    builtin_dumb
defaulting to 'ansi'

This doesn't happen with the vim distributed in Debian and it also doesn't happen with a a self-compiled vim (version 8.1.2136).

Bad runtimepath on session loading

Because the appimage uses different path for the vim runtime on every start the runtimepath that saved in the Session.vim is wrong. Because of that the scripts from the default vim runtime path not loaded.

Error:

Error detected while processing command line..script <cut-out>/Session.vim[19]..BufRead Autocommands for "*.sh":
E117: Unknown function: dist#ft#SetFileTypeSH

Steps to reproduce:

$ wget https://github.com/vim/vim-appimage/releases/download/v8.2.2771/GVim-v8.2.2771.glibc2.15-x86_64.AppImage
$ ln -s GVim-v8.2.2771.glibc2.15-x86_64.AppImage vim
$ chmod u+x vim

$ ./vim -u NONE +"filetype plugin on" +"set rtp+=." test.sh
# insert something eg.: test-message
:w
:mks
:q

# now the runtime path in the Session.vim contains:
# runtimepath=~/.vim,/tmp/.mount_vimoFbdm6/usr/share/vim/vimfiles,/tmp/.mount_vimoFbdm6/usr/share/vim/vim82,/tmp/.mount_vimoFbdm6/usr/share/vim/vimfiles/after,~/.vim/after,.

./vim -u NONE +"filetype plugin on" +"set rtp+=." -S
> "test.sh" 1L, 18B
> Error detected while processing command line..script Session.vim[19]..BufRead Autocommands for "*.sh":
> E117: Unknown function: dist#ft#SetFileTypeSH
> Press ENTER or type command to continue

:set rtp?
> runtimepath=~/.vim,/tmp/.mount_vimoFbdm6/usr/share/vim/vimfiles,/tmp/.mount_vimoFbdm6/usr/share/vim/vim82,/tmp/.mount_vimoFbdm6/usr/share/vim/vimfiles/after,~/.vim/after,.

:echo $VIMRUNTIME
> /tmp/.mount_vimh7YdOt/usr/share/vim/vim82

Expected result:
On session loading vim use the new runtime path.

I found a dirty workaround.
Always have to create a Sessionx.vim file with every session but the file reload can be problematic.

set rtp+=$VIMRUNTIME
windo e!

GTK Gui

Thanks for providing these vim appimages; they are really helpful. However, I was wondering if it would be easy to provide appimages based to gtk gui instead of x11-athena; I have been using an old appimage from the older repo chrisbra/vim-appimage which is compiled with gtk gui.

Vim AppImage configuration not persisting across sessions

I have encountered an issue with the Vim AppImage where the configuration settings are not persisting across sessions. Each time I close Vim and reopen it, I have to specify the vimrc file again, and plugins need to be reinstalled using pluginstall.

Expected Behavior:
I expect Vim AppImage to retain the configuration settings and installed plugins between sessions, allowing for a seamless and persistent user experience.

Steps to Reproduce:

Download Vim AppImage.
Open Vim using the AppImage.
Specify a vimrc file and install plugins.
Close Vim.
Reopen Vim using the AppImage.

Actual Result:
The configuration settings and installed plugins are not retained, and Vim starts with default settings.

You might think it's just a :source /path/to/folder/.vimrc but it's really annoying, for example for the codeium plugin (an alternative to copilot) where you have to enter your token each time, via the browser.

Environment:

Operating System: MXlinux 21.3 (Wildflower)
Vim Version: Vim: v9.1.0029 (https://github.com/vim/vim-appimage/releases/tag/v9.1.0029)

Thank you

Releases for 9.1.x can't find files in /usr/share/vim/vim90

Release: Vim-v9.1.0027.glibc2.29-x86_64.AppImage

AppImages for all 9.1 releases of Vim produce the following errors:

Error detected while processing /usr/share/vim/vimrc:
line   25:
E484: Cannot open file /tmp/.mount_Vim-v9vBqJ5u/usr/share/vim/vim90/syntax/syntax.vim
failed to load colors/lists/default.vim
Error detected while processing /home/paul/.vim/vimrc:
line   61:
E185: Cannot find colour scheme 'koehler'
line   98:
E484: Cannot open file /tmp/.mount_Vim-v9vBqJ5u/usr/share/vim/vim90/menu.vim
line  142:
E484: Cannot open file /tmp/.mount_Vim-v9vBqJ5u/usr/share/vim/vim90/syntax/syntax.vim

Similar errors are seen when starting the GVim AppImage.
Last successful launch of either AppImage was with release 9.0.2190
Operating system: Ubuntu 22.04 and Kubuntu 24.04 (dev)

Build another AppImage with all popular dependencies

Issue Description

Currently, the Vim AppImage distributed by the vim/vim-appimage repository does not include some popular dynamic libraries, such as libperlX, libpython2.7, libpython3X, liblua5X, and librubyX. While the current approach of not including these libraries keeps the size of the AppImage small, it also makes it difficult to use some Vim plugins and scripts that require these dependencies.

Therefore, we would like to request a new Vim AppImage that includes all popular dependencies by default. This would allow users to have a more seamless experience when using Vim with plugins and scripts that require these dependencies.

Feature Request Details

  • Include libperlX, libpython2.7, libpython3X, liblua5X, and librubyX in the Vim AppImage (in the tremendous build).
  • Ensure that the AppImage works on various Linux distributions and architectures.
  • Update the documentation to reflect the changes made.

Proposed Solution

We propose creating a new Vim AppImage that includes all popular dependencies (in the tremendous build). This can be achieved by modifying the current recipe file and build scripts to include these dependencies during the build process. We also suggest performing thorough testing on various Linux distributions and architectures to ensure that the AppImage works as expected.

Additional Context

The current Vim AppImage is a great tool for providing a portable version of Vim without the need for installation or dependencies. However, having another version that includes all popular dependencies by default would provide an even better user experience and make it easier to use Vim with a wider range of plugins and scripts.

Thank you for considering our feature request.

No v9.0 appimage

I would like to try the new release. Can we have a build of version 9, please?

included libraries; recent xz-utils / liblzma compromise

I ran

$ GVim-v9.1.0228.glibc2.29-x86_64.AppImage &
$ ls -d /tmp/.mount*  # get auto-mounted AppDir
# /tmp/.mount_GVim-vRwbSEr

$ ldd /tmp/.mount_GVim-vRwbSEr/usr/bin/vim | grep -E 'lzma|systemd|perl|ruby|python|lua'
	liblua5.3.so.0 => /tmp/.mount_GVim-vRwbSEr/usr/bin/../lib/liblua5.3.so.0 (0x00007efc1b9f4000)
	libperl.so.5.30 => /tmp/.mount_GVim-vRwbSEr/usr/bin/../lib/libperl.so.5.30 (0x00007efc1b600000)
	libpython2.7.so.1.0 => /tmp/.mount_GVim-vRwbSEr/usr/bin/../lib/libpython2.7.so.1.0 (0x00007efc1b200000)
	libruby-2.7.so.2.7 => /tmp/.mount_GVim-vRwbSEr/usr/bin/../lib/libruby-2.7.so.2.7 (0x00007efc1ac00000)
	libsystemd.so.0 => /tmp/.mount_GVim-vRwbSEr/usr/bin/../lib/libsystemd.so.0 (0x00007efc19cc2000)
	liblzma.so.5 => /tmp/.mount_GVim-vRwbSEr/usr/bin/../lib/liblzma.so.5 (0x00007efc19c74000)

Two things to note here:

  • The appimages do include libruby, llibperl, liblua and (interestingly) libpython2 (but not 3) which is different from what the release notes / documentation state. I had some release note PR's coming up in any case for unrelated stuff (AppRun.extracted), so I ended up verifying and rewriting the docs.
  • by now I suppose everyone has heard of the xz / liblzma5 / sshd backdoor (e.g. see the Debian fallout).
    • in short, Debian stable doesn't seem to be affected, and the vulnerability only seems to target Debian/Redhat-patched sshd anyway
    • because the vim-appimage's are currently built with Ubuntu 20.04, we probably link to (and "ship") even older versions. I think vim can access compression algorithms (e.g. via its embedded languages) so this might still be a relevant point
    • the appimage compression algorithm (for the embedded squashfs) is gzip, not xz (see below)
$ GVim-v9.1.0228.glibc2.29-x86_64.AppImage --appimage-offset
193728
$ dd if=GVim-v9.1.0228.glibc2.29-x86_64.AppImage of=/tmp/x.squashfs bs=193728 skip=1
# ...
$ file /tmp/x.squashfs
/tmp/x.squashfs: Squashfs filesystem, little endian, version 4.0, zlib compressed  # ...

GVim - 'xapp and canberra' Modules failed

os: Arch
kernel: 6.2.8-arch1-1

Current package versions on system:

  • xapp: 2.4.2-2
  • libcanberra: 1:0.30+r2+gc0620e4-3
  • gdk-pixbuf2: 2.42.10-2

Gvim appimage does not want to open due to modules not loading.

Gtk-Message: 10:26:20.940: Failed to load module "xapp-gtk3-module"
Gtk-Message: 10:26:20.941: Failed to load module "canberra-gtk-module"

(gvim:76276): Gtk-WARNING **: 10:26:21.376: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Bail out! Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Vim: Caught deadly signal ABRT
Vim: Finished.

Aborted (core dumped)

I did see there was gdk-pixbuf-xlib as a deprecated xlib integration package for GdkPixbuf in my Distro. I did installed that package as well and still gave the same error.
Currently gdk-pixbuf-xlib is on version 2.40.2-2

Also installed gvim locally from my Distros repo, and that one works fine. Thought it would change something with current packages but the appimage still errors out.

Release stopped

It seems that the releases are stopped because no credits left for Travis CI.
It might be better to switch to GitHub Actions.

Gvim (vim) cannot find file

Hi, this is the output of latest appimage GVim-v8.2.0011.glibc2.15-x86_64.AppImage.

Gvim/vim is trying to open syntax file in:
/tmp/.mount_gvimpH5q6T/usr/share/vim/vim81/syntax/syntax.vim

but it cannot find it, as the unsquashed image in /tmp is:
tmp/.mount_gvimpH5q6T/usr/share/vim/vim82/syntax/syntax.vim

Here is the output of vim messages:

Messages maintainer: Bram Moolenaar [email protected]
Error detected while processing /home/bozidar/.local/share/nvim/site/vim-sensible/plugin/sensible.vim:
line 15:
E484: Can't open file /tmp/.mount_gvimpH5q6T/usr/share/vim/vim81/syntax/syntax.vim
wombat256mod
No Syntax items defined for this buffer
E484: Can't open file /tmp/.mount_gvimpH5q6T/usr/share/vim/vim81/syntax/syntax.vim

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.