On Thu, May 24, 2012 at 3:52 PM, Ted Pavlic <t...@tedpavlic.com> wrote:
> > let g:Tex_ViewRuleComplete_pdf = 'evince /tmp/$*'
> >
> > and I tried hardcoding path of produced pdf file like this:
> > let g:Tex_ViewRuleComplete_pdf = 'evince /tmp/seminar.pdf'
>
> The hard-coded line works fine for me. Otherwise,
>
> let g:Tex_ViewRuleComplete_pdf = 'evince /tmp/$*.pdf'
>
> works fine for me.
>
> If things aren't working fine for you, then while evince is running
> and telling you that the path is bad, can you jump into the terminal
> and do:
>
> ps auxww|grep evince
>
> and see what evince command is being called? That should give a hint
> as to what the unique problem is on your system.
>
> --Ted
>
>
So here is the output when i use:
let g:Tex_ViewRuleComplete_pdf = 'zathura /tmp/$*.pdf'
zathura /tmp/ /home/mesx/temp/2012_05_pero_PaaS/seminar.pdf
and here is the output afrer hardcoding
let g:Tex_ViewRuleComplete_pdf = 'zathura /tmp/seminar.pdf'
zathura /tmp/ /home/mesx/temp/2012_05_pero_PaaS/seminar.pdf
Dont know is it relevant or not, but I use Vundle for managing vim plugins.
and I installed vim-latex using this line in my .vimrc:
Bundle 'LaTeX-Suite-aka-Vim-LaTeX'
> --
> Ted Pavlic <t...@tedpavlic.com>
>
--
http://www.google.com/profiles/marijan.svalina
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
