It's on purpose, see commit 1f87b1510f610361d8e382c7a8c0b6a44fcb183a.
You now need to do a git clone, it's anyway more convenient that way to receive updates (with git pull).

(In reply to Sébastien Wilmet from comment #1)
> It's on purpose, see commit 1f87b1510f610361d8e382c7a8c0b6a44fcb183a.
> You now need to do a git clone, it's anyway more convenient that way to
> receive updates (with git pull).

on purpose does not mean 'it can't be rediscussed' I hope.

Sure, one can argue that users should git clone. But what about users that get it from a package provided rpm? Why make it extra hard for distro packagers to provide usable packages to their users?

The files have not been auto-installed before, which was fine; but at least we distro packagers had them available in the release tarballs to either install or ignore them, as we pleased to do (openSUSE for one install them as addong packages)

Please consider this use-case of the tarballs too

I didn't know that the Vim or Emacs plugin was packaged by Linux distros. I thought that everybody needed to copy the files manually, install them at the right places and do the configuration (adapt the vimrc etc).

I'll revert the change and distribute again those files in tarballs, sorry for the inconvenience (but it's great to see that the unstable releases are actually tested).

Fixed: commit dfc88c06e1b38ae49f3387798858d34a698a0662

The plugins are now in the plugins/ directory instead of misc/.

Thank you Wilmet. We apreciate yout reconsideration.