Hi Jin,

I think you have forgotten to define the ps dependency, texrc:
" Uncomment this line if you compile ps files via dvi files.
" TexLet g:Tex_FormatDependency_ps = 'dvi,ps'

so add

let g:Tex_FormatDependency_ps='dvi,ps'

to your vimrc. Than the program can complete the chain dvi,ps,pdf

cheers,

Dennis



Jin Chen wrote:
> Dear Dennis, 
>
> I appreciate your responsive reply! As you suggested, I added the
> following lines into my .vimrc and
> tried it our again, but still no luck. I also attached the .vimrc and
> texrc files for your reference. 
>
> It also did not make any difference whether I added the following
> lines into tex.vim or not:
> " customized compiling settings
>  let g:Tex_MultipleCompileFormats = 'dvi,ps'
>  let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
>  let g:Tex_DefaultTargetFormat = 'pdf'
>
> " compiling rules
>  let g:Tex_CompileRule_dvi = 'latex --interaction=nonstopmode $*'
>  let g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi'
>  let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps $*.pdf'
>
> " other settings
>  let g:Tex_IgnoreLevel = 7
>
>
> It would be really great if you could take a look into them. There
> must be something I still missed. 
> Thank you once again in advance!
>
>
> Sincerely,
> Jin Chen
>
>
>
> On Tue, Mar 16, 2010 at 4:21 AM, LAG Grimminck
> <l.grimmi...@science.ru.nl <mailto:l.grimmi...@science.ru.nl>> wrote:
>
>     Dear Jim,
>
>     My suggestion is to read the texrc file, that you already found,
>     thouroughly(!), and make any changes in your .vimrc file or maybe
>     the vim.tex (I only made them in my vimrc).
>
>     You will need:
>     let g:Tex_MultipleCompileFormats = 'dvi,ps'              (pdf will
>     not need multiple compile steps since it will depend on ps2pdf)
>     let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
>     let g:Tex_DefaultTargetFormat = 'pdf'
>     let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'              (this is
>     what you most probably forgot)
>
>     and for your viewer you may want to use
>     let g:Tex_ViewRule_pdf = 'gv'  (has a watchfile option, but I will
>     start to fail for large files.. you will not be able to keep the
>     same page at the end of your document updated)
>     let g:Tex_ViewRule_pdf = 'acroread' (does not have a watchfile,
>     ctrl+r will update your current page, always!)
>
>     I hope this will work out for you!
>
>     cheers,
>
>     Dennis
>
>
>
>
>     On 03/16/2010 04:00 AM, Jin Chen wrote:
>>     Hi All,
>>
>>     I'm very new to this package but eager to get comfortable with
>>     it. I haven't figured out how to set up the configuration files
>>     so that I can run customized compiling/viewing command when I
>>     issue "\ll". I read through the on-line manual and tried to
>>     put the following lines into the "~/.vim/ftplugin/tex.vim" file
>>     (it's a ubuntu machine). 
>>
>>     I hope to get pdf files via "dvi -> ps -> pdf." 
>>
>>     " this is mostly a matter of taste. but LaTeX looks good with
>>     just a bit
>>     " of indentation.
>>      set sw=2
>>     " " TIP: if you write your \label's as \label{fig:something},
>>     then if you
>>     " " type in \ref{fig: and press <C-n> you will automatically
>>     cycle through
>>     " " all the figure labels. Very useful!
>>     set iskeyword+=:
>>
>>     " customized compiling settings
>>     let g:Tex_MultipleCompileFormats = 'dvi,ps,pdf'
>>     let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
>>     let g:Tex_DefaultTargetFormat = 'pdf'
>>
>>     " compiling rules
>>     let g:Tex_CompileRule_dvi = 'latex --interaction=nonstopmode $*'
>>     let g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi'
>>     let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps $*.pdf'
>>
>>     " other settings
>>     let g:Tex_IgnoreLevel = 7
>>
>>     I also changed the following line in
>>     ~/.vim/ftplugin/latex-suite/texrc:
>>
>>     if has('macunix')
>>         TexLet g:Tex_DefaultTargetFormat = 'pdf'
>>
>>     originally it's dvi instead of pdf. 
>>
>>
>>     When I issue "\ll" in VIM, what i got is only dvi output. What
>>     else should I change? I read through the manual several times but
>>     still
>>     didn't find a clue. Please advise. 
>>
>>     I appreciate your help!
>>
>>
>>
>>     Sincerely,
>>     Jin Chen
>>
>>
>>     
>> ------------------------------------------------------------------------------
>>     Download Intel&#174; Parallel Studio Eval
>>     Try the new software tools for yourself. Speed compiling, find bugs
>>     proactively, and fine-tune applications for parallel performance.
>>     See why Intel Parallel Studio got high marks during beta.
>>     http://p.sf.net/sfu/intel-sw-dev
>>
>>
>>     _______________________________________________
>>     Vim-latex-devel mailing list
>>     Vim-latex-devel@lists.sourceforge.net 
>> <mailto:Vim-latex-devel@lists.sourceforge.net>
>>     https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>       
>
>     -- 
>     Dennis LAG Grimminck
>     PhD student
>
>     Molecular and Biophysics /
>     Solid State NMR
>     Heyendaalseweg 135
>     Nijmegen
>     Desk: near HG 03.305
>
>     phone: +31 24 3652324 email: l.grimmi...@science.ru.nl 
> <mailto:l.grimmi...@science.ru.nl> http://www.ru.nl/molphys 
>
>

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Reply via email to