Package Details: gvim-gtk2 9.1.0366-1

Git Clone URL: https://aur.archlinux.org/gvim-gtk2.git (read-only, click to copy)
Package Base: gvim-gtk2
Description: Vim, the text editor. CLI version and GTK2 GUI providing majority of features.
Upstream URL: http://www.vim.org
Keywords: gvim vim
Licenses: custom:vim
Conflicts: gvim, gvim-git, gvim-gtk3, gvim-python3, vim, vim-git, vim-minimal, vim-minimal-git, vim-python3, vim-runtime, vim-runtime-git
Provides: gvim, vim, vim-runtime, xxd
Submitter: fusion809
Maintainer: fusion809
Last Packager: fusion809
Votes: 8
Popularity: 0.000000
First Submitted: 2016-10-01 13:11 (UTC)
Last Updated: 2024-04-23 03:52 (UTC)

Dependencies (14)

Required by (495)

Sources (4)

Latest Comments

1 2 3 4 Next › Last »

replabrobin commented on 2024-04-21 12:53 (UTC)

gdk-pixbuf2-2.42.11-1 fixes this issue; sorry for the noise :(

replabrobin commented on 2024-04-20 10:29 (UTC) (edited on 2024-04-20 11:29 (UTC) by replabrobin)

I started to get errors recently when running gvim from a terminal, not sure what has changed to cause this. If I downgrade back to where I was on April 12 using the arch archive then the same gvim-gtk2 does not have these errors. I see one of the changes was gdk-pixbuf2-2.42.10-2 --> gdk-pixbuf2-2.42.11-1. If using the April 12 installs I just upgrade gdk-pixbuf2-2.42.11-1 I see the errors below. It seems that the error concerns the icons which gvim uses and those cannot be displayed with gdk-pixbuf2-2.4211-1.

$ gvim

(gvim:45602): GdkPixbuf-WARNING **: 11:27:27.381: Error loading XPM image loader: Image type “xpm” is not supported

....

(gvim:45602): GLib-GObject-CRITICAL **: 11:27:27.381: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

.....

bidulock commented on 2023-08-09 05:35 (UTC)

Won't build for me since perl 5.38 update, neither inside nor outside a clean chroot. Get lots of errors in linking stage like:

/usr/bin/ld: objects/if_perl.o: in function PerlIOVim_pushed': /u2/custompkgs/ubs/gvim-gtk2/src/vim-9.0.1679/src/if_perl.xs:1490:(.text+0x770): undefined reference toPerl_SvPV_helper' /usr/bin/ld: objects/if_perl.o: in function XS_VIBUF_Count': /u2/custompkgs/ubs/gvim-gtk2/src/vim-9.0.1679/src/if_perl.c:2229:(.text+0x81c): undefined reference toPerl_SvIV' /usr/bin/ld: objects/if_perl.o: in function XS_VIBUF_Number': /u2/custompkgs/ubs/gvim-gtk2/src/vim-9.0.1679/src/if_perl.c:2198:(.text+0x94c): undefined reference toPerl_SvIV' /usr/bin/ld: objects/if_perl.o: in function XS_VIBUF_Name': /u2/custompkgs/ubs/gvim-gtk2/src/vim-9.0.1679/src/if_perl.c:2163:(.text+0xa8e): undefined reference toPerl_SvIV' /usr/bin/ld: objects/if_perl.o: in function XS_VIBUF_DESTROY': /u2/custompkgs/ubs/gvim-gtk2/src/vim-9.0.1679/src/if_perl.c:2134:(.text+0xc14): undefined reference toPerl_SvIV' /usr/bin/ld: objects/if_perl.o: in function XS_VIBUF_Append': /u2/custompkgs/ubs/gvim-gtk2/src/vim-9.0.1679/src/if_perl.c:2455:(.text+0xd1a): undefined reference toPerl_SvIV'

Veemo commented on 2020-10-25 21:03 (UTC)

@fusion809 Thanks a lot!

fusion809 commented on 2020-10-25 16:43 (UTC)

@Veemo Done.

Veemo commented on 2020-10-25 16:16 (UTC)

Thank you for your work! I noticed that vim built from this PKGBUILD doesn't read /etc/vimrc, it only attempts to find a global vimrc in /ush/share/vim. Could you please change lines 36-37 to:

sed -E -i 's|^.*(#define SYS_.*VIMRC_FILE.*").*$|\1|g' src/feature.h
sed -E -i 's|^.*(#define VIMRC_FILE.*").*$|\1|g' src/feature.h

to make it work correctly? Like here: https://github.com/archlinux/svntogit-packages/blob/packages/vim/trunk/PKGBUILD#L37-L38.

Also, would it be possible to include the CVE-2017-1000382 fix from the official package into archlinux.vim here (see https://github.com/archlinux/svntogit-packages/blob/packages/vim/trunk/archlinux.vim#L22-L40)? I tested it on my system and it seems like Vim still doesn't respect umask when creating swap files (and in my opinion, having all swap files stored in one place is simply more convenient).

replabrobin commented on 2020-08-01 12:22 (UTC)

I have a strangeness with regard to CTRL-V behaviour compared with the standard gvim package. In gvim I find that the visual mode ctrl-v+ctrl-m creates the expected ^M in the text. However, in gvim command line (after the ':') ctrl-v+ctrl-m becomes <C-M> and that doesn't match any real ^M chars in the text making edits of script output etc etc much harder. I tried removing all my customization and it makes no difference. in vim in a terminal the command line behaviour is 'correct' in that ctrl-v+ctrl-m produces ^M as I expect. I don't believe this is caused /usr/share/vim as when I substitute the gvim version of /usr/share/vim for gvim-gtk's version the 'wrong' behaviour is still present in gvim-gtk2. I prefer the speed of this version, but would like it to match gvim.

fusion809 commented on 2019-01-30 20:18 (UTC)

@dgq: thanks mate for reporting these issues. I use a shell script to keep this package up-to-date and, suffice it to say, it is not perfect. Should be fixed in the latest commit.

dgq commented on 2019-01-30 20:02 (UTC) (edited on 2019-01-30 22:08 (UTC) by dgq)

There's something funky going on ever since https://aur.archlinux.org/cgit/aur.git/commit/?h=gvim-gtk2&id=63213601c375 . Notice how the hashes change even though the files in question haven't. Compare to its parent: https://aur.archlinux.org/cgit/aur.git/commit/?h=gvim-gtk2&id=f779d330cd9e

There's another seemingly spurious change in the Maintainer comment line as well.

Every new commit since repeats this weird set of changes, with only a few numbers changing in the hashes (something virtually impossible to happen even if the file were changing, which they aren't).

bidulock commented on 2018-07-28 19:43 (UTC)

I suppose acl is in core so it is not needed.

1 2 3 4 Next › Last »