Installation problems on Ubuntu via Termux

[rieser]

Description

I get the following error when trying to install vimtex on a Samsung S6 Lite Tablet using Ubuntu under Termux. I get the same error under vim using vim-plug or the native vim package system, and also in neovim. Any help would be much appreciated.

Error detected while processing function vimtex#init[7]..<SNR>26_init_state[1]..
vimtex#state#init[9]..vimtex#state#class#new[32]..vimtex#compiler#init_state[3].
.<SNR>41_init_compiler[5]..vimtex#compiler#latexmk#init[1]..1[5]..20:
line    9:
E121: Undefined variable: l:cmd
E116: Invalid arguments for function vimtex#log#warning
Error detected while processing function vimtex#init[7]..<SNR>26_init_state[1]..
vimtex#state#init[9]..vimtex#state#class#new:
line   32:
E170: Missing :endfor
Error detected while processing function vimtex#init[7]..<SNR>26_init_state[1]..
vimtex#state#init:
line    9:
E171: Missing :endif

Steps to reproduce

vim or nvim. Any .tex file. I used:

\documentclass{article}

\begin{document}
This is a test.
\end{document}

Expected behavior

vim or nvim to open normally

Actual behavior

I get the error described above when opening a .tex file. Also, the \ll and \lv commands don't work.

Do you use a latexmkrc file?

No

VimtexInfo

I get the error: "E492: Not an editor command: VimtexInfo"

[rieser]

I get a similar error in Fedora and Debian (installed via proot-distro). In Termux it works fine.

[lervag]

I get the following error when trying to install vimtex on a Samsung S6 Lite Tablet using Ubuntu under Termux. I get the same error under vim using vim-plug or the native vim package system, and also in neovim. Any help would be much appreciated.

It seems to me that this does not have anything to do with installation. Instead, it looks like a problem during initialization of VimTeX when you open a .tex file.

:VimtexInfo would probably not be available if this initialization is not working. So, in this case: What's the version of Vim and/or neovim?

Please also note that the proper way to write code blocks in Markdown is to use three backtics, i.e.

Markdown stuff

```
code block here
```

You used multiple =s, which makes the preceding text recognized as a header. Feel free to read the guide to github flavored markdown

[lervag]

I've pushed a minor fix that should resolve the error. Please update and let me know what happens now.

[rieser]

It works! Many thanks!

(Sorry about the sloppy formatting. Thanks for the advice as well.)

[lervag]

Glad to hear it! And you're welcome :)

[rieser]

The version of vim was 8.1.2269, and the neovim version was 0.4.3.