Package Details: neovim-vimtex-opt-git 3719.e5214dd3-1

Git Clone URL: (read-only, click to copy)
Package Base: neovim-vimtex-opt-git
Description: A modern (neo)vim plugin for editing LaTeX files.
Upstream URL:
Licenses: MIT
Submitter: shanewstone
Maintainer: shanewstone
Last Packager: shanewstone
Votes: 4
Popularity: 0.012427
First Submitted: 2019-04-20 04:59 (UTC)
Last Updated: 2021-01-06 00:37 (UTC)

Latest Comments

Segaja commented on 2020-03-23 00:05 (UTC)

@shanewstone: I understand and I believe i will make a vim-vimtex AUR package in the future.

Another reasone why it would be odd for vim users to use your package is that it has a dependency on neovim which doesn't make sense for normal vim users.

As long as you don't mind me creating a vim-vimtex package then all is fine ;)

shanewstone commented on 2020-03-23 00:02 (UTC)

@Segaja I believe you are misunderstanding the situation.

Anyone is free to make a "vim-vimtex" package. I have no desire to do so.

The vim and neovim projects decide on their default directory structure. I have no role in this matter.

This package is usable and useful. I have edited my comment below to better reflect my opinion on this. Anyone who uses neovim can use this package. Technically, anyone who uses vim can use this package as well, but would have to add a neovim directory to their path, which seems an odd choice to me.

Feel free, of course, to make a "vim-vimtex" package and use this PKGBUILD as a guide, copying any portion which you find useful, but understand that I am not available to provide support on the creation of other AUR packages. As a tip, other vim plugin packages will likely have even more useful PKGBUILD files than this package.

Segaja commented on 2020-03-22 23:12 (UTC)

If the path to install it to are so much different between vim and neo-vim wouldn't it make more sense to have one neovim-vimtex and one vim-vimtex?

If you never intended this package to be used by anyone else why did you upload it to the AUR? From my point of view if you uploaded it, it should be usable.

It is actually stated in the Submission Guidelines ( ) that a package should be useful for others. By your own statement this is not really useful for others.

How about we split the package? I would be happy to maintain the vim-vimtex variant if you don't want to take it ;)

shanewstone commented on 2019-05-02 15:56 (UTC) (edited on 2020-03-22 23:55 (UTC) by shanewstone)

It installs to a neovim directory, /usr/local/share/nvim/site/pack/${_pkgname}/opt/${_pkgname}/, which is why I list neovim as a dependency, but of course it will install fine without it - I am just not sure why someone would do that.

That being said, it installs to an opt/ directory, so takes a specific packadd in your init.vim to get working.

You may wish to use a vim plugin manager like vim-plug, pathogen, etc., instead of this package.

Rakete1111 commented on 2019-05-02 10:59 (UTC)

Does this really depend on neovim?