LLPStartPreview doesn't start

[linuscl]

Error in "function <SNR>34_Compile":
Line   10:

That's the error I received, and evince (pdf viewer) says that it cannot find the pdf file.

[paynito]

starting $vim main.tex after enabling your plugin in .vimrc.
Error detected while processing function <SNR>28_Initialize: line 10: E887: Sorry, this command is disabled, the Python's site module could not be loaded.

[xuhdev]

@paynito This is because your Vim installation does not have Python feature enabled (or the python feature is broken). Please try to reinstall Vim. You can search for E887 online, the solution is the same, regardless of the plugin.

[thebabush]

I just want to add that I have VIM compiled with python3 and it seems that I have to :%s/python/python3/g on my xenial machine.

[luchaoo7]

Hello does anyone know why when I type :LLPStartPreview in VIM it says "Not an editor command"

[xuhdev]

@luchaoo7 You probably didn't have the plugin loaded. You can check by running :script.

[luchaoo7]

@xuhdev thanks for your reply, It is loaded
54: ~/.vim/bundle/vim-latex-suite/plugin/remoteOpen.vim
55: ~/.vim/bundle/vim-latex-live-preview/plugin/latexlivepreview.vim

The only tag I see in ~/.vim/bundle/vim-latex-live-preview/doc/tag is "vim-latex-live-preview.txt"

In the "latexlivepreview.vim" file on line command! 184 is the following:
command! LLPStartPreview call s:StartPreview()

I can't seem to spot why its not working.

[xuhdev]

As long as it's loaded, it should be available. Tags are just indices for quick lookup. Perhaps you wanna check your typing of the command?

[jestin]

I'm seeing the same thing. script says that it is loaded:

~/.config/vim/plugged/vim-latex-live-preview/plugin/latexlivepreview.vim

but vim's command autocomplete doesn't pick it up, and I get Not an editor command: LLPStartPreview.

As you can see, I installed this using the vim-plug plugin manager, but I hope that isn't the issue.

UPDATE: I see that the script looks specifically for 'python' support, and not 'python' and 'python3'. That's why I was never seeing the commands available. Any chance of adding python3 support?

[kunlilin2991]

I have encounter the same problem
I use vundle to manage plugin
in vimrc
Plugin 'xuhdev/vim-latex-live-preview'
the info in vim :script is as following
77: ~/.vim/bundle/vim-latex-live-preview/plugin/latexlivepreview.vim
however when i type LLPStartPreview
this problem appeared as following
E492: not an editor command :LLPStartPreview
this pluginin seems not work.

[badouralix]

@kunlilin2991 thanks for the feedback !
vundle doesn't seem to be the issue (a section to the readme should be added about that actually)

Could you provide some info about your system and your vim ? Also, what does :echo g:loaded_vim_live_preview output ?

Having the same problem here. VIM 8.0 installed on macOS Sierra through Homebrew, relevant features: +python3 -python.
Plugin installed through vundle. Configured the previewer and the updatetime as per the instructions.
Doing :echo g:loaded_vim_live_preview returns 1.

Going through ~/.vim/bundle/vim-latex-live-preview/plugin/latexlivepreview.vim and replacing all "python" calls with "python3" and reloading, everything works perfect.

Looks like the if(!has('python')[...] block should be extended to test for both +python and +python3 features. Also, the python command should be dynamically set as either 'python' or 'python3', depending on the existing feature.

[ranguli]

Also having the same issue as @vicentius, @kunlilin2991, @luchaoo7 and @jestin. :script is saying the plugin is in fact being loaded, but :LLPStartPreview with or without a filename returns the E492: Not an editor command: LLPStartPreview.

I'm running Xubuntu 16.04, with Vim 7.4 compiled with support for +python and +python3

[badouralix]

Thanks @vicentius for the python3 checking! Then this should be easy to fix. Otherwise, maybe we can look for a way to get rid of python and only use vim internal functions...

@ranguli @kunlilin2991 : digging into E492, I found this post VundleVim/Vundle.vim#486 (comment). Could you check whether our issue is somehow related to this one? If so, it can be fixed using a .gitattributes file.