Re: [Vim-latex-devel] need help for customizing compiling settings
Brought to you by:
srinathava,
tmaas
From: Jin C. <che...@gm...> - 2010-03-18 01:47:24
|
Hi All, Thanks for everybody's help! I still have my problem using VIM-latex-suite: .dvi is generated but not for .ps or .pdf files. Does anybody could share your configuration file with me? The files that you make any changes when you configure latex-suite package, .vimrc, texrc, or even tex.vim? I am using an Ubuntu 9.10 box on a 64-bit Intel machine, and VIM version v7.2.245. If you consider your environment is similar to mine, please send me a copy of your configuration files for my reference. I appreciate your help! Sincerely, Jin Chen On Wed, Mar 17, 2010 at 9:24 PM, Jin Chen <che...@gm...> wrote: > Hi Mike, > > Thanks for your suggestions, unfortunately still no luck. I suppose your > suggested adding the rule > into texrc file, right? I actually added it into both texrc and .vimrc, but > still didn't work -- I just can't > generate a .ps file from the .dvi file. Any thoughts on this situation? > > Seems like I'm running into a > stubborn case... > > > Sincerely, > Jin Chen > > > > > On Wed, Mar 17, 2010 at 8:26 PM, Mike Richman <mik...@gm...>wrote: > >> Hi Jin, >> >> I think I had a similar problem at some point. I decided to write a >> rule that goes all the way to PDF. It's a bit of a hack, but it >> works. >> >> " Section: Compiling {{{ >> let g:Tex_DefaultTargetFormat='pdf' >> let g:Tex_MultipleCompileFormats='pdf' >> let g:Tex_CompileRule_pdf='latex -interaction=nonstopmode -shell-escape >> $*.tex' >> \.' && dvips -P pdf -q $*.dvi' >> \.' && rm -f $*.dvi' >> \.' && ps2pdf $*.ps' >> \.' && rm -f $*.ps' >> " }}} >> >> Good luck, >> >> Mike >> >> >> On Wed, Mar 17, 2010 at 11:48 AM, Jin Chen <che...@gm...> wrote: >> > Hi Dennis, >> > I tried dvips, ps2pdf in the terminal, and they worked just fine. In >> > vim-latex-suite, I can get dvi files but no ps or pdf files. >> > I can't get ps files when I changed the compile target to ".ps", so I >> guess >> > it is where the problem happens. >> > Do you have any ideas why this happened and how should I correct it? >> Thanks >> > a lot for your patience and helps! >> > >> > >> > Sincerely, >> > Jin Chen >> > >> > >> > >> > On Wed, Mar 17, 2010 at 4:14 AM, LAG Grimminck < >> l.g...@sc...> >> > wrote: >> >> >> >> Dear Jin, >> >> >> >> I compared what you use against what I use and it is the same. My next >> >> suggestion is that you try your compilation command line first and see >> if >> >> nothing is wrong with either dvips or ps2pdf. If that works you can try >> to >> >> generate a ps file by setting the target to ps. Since you were already >> able >> >> to create your dvi file, at least that should work. If not we should >> >> concentrate on getting your dvi->ps part to work first. >> >> >> >> cheers, >> >> >> >> Dennis >> >> >> >> On 03/17/2010 12:05 AM, Jin Chen wrote: >> >> >> >> Hi Dennis, >> >> Thank you for your further advices. >> >> I tried you suggestions but still no luck. Here is the related part of >> my >> >> latest .vimrc: >> >> " for VIM-latex-suite usage >> >> let g:Tex_MultipleCompileFormats = 'dvi,ps' >> >> let g:Tex_DefaultTargetFormat='pdf' >> >> let g:Tex_FormatDependency_ps='dvi,ps' >> >> let g:Tex_FormatDependency_pdf='dvi,ps,pdf' >> >> let g:Tex_CompileRule_dvi='latex --interaction=nonstopmode $*' >> >> let g:Tex_CompileRule_ps='dvips -o $*.ps $*.dvi' >> >> let g:Tex_CompileRule_pdf='ps2pdf $*.ps' >> >> let g:Tex_ViewRule_pdf='acroread' >> >> Then below are the related parts of my texrc: >> >> if has('macunix') >> >> TexLet g:Tex_DefaultTargetFormat = 'pdf' >> >> else >> >> TexLet g:Tex_DefaultTargetFormat = 'pdf' >> >> endif >> >> ...... >> >> " Compiler rules {{{ >> >> " This is the first thing you should customize. It is set up for most >> >> common >> >> " values, but if use some other compiler, then you will want to change >> >> this. >> >> " As CompileFlags value you'd perhaps like to use, e.g., >> '-src-specials', >> >> " but it is known that it can sometimes give different results in the >> >> output, >> >> " so use it with care. The '-file-line-error' flag helps sanitize LaTeX >> >> error >> >> " messages for processing by Vim. >> >> TexLet g:Tex_CompileRule_dvi = 'latex -interaction=nonstopmode $*' >> >> TexLet g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi' >> >> TexLet g:Tex_CompileRule_pdf = 'ps2pdf $*.ps' >> >> TexLet g:Tex_EscapeChars = '{}\' >> >> >> >> " ways to generate pdf files. there are soo many... >> >> " NOTE: pdflatex generates the same output as latex. therefore quickfix >> is >> >> " possible. >> >> " TexLet g:Tex_CompileRule_pdf = 'pdflatex -interaction=nonstopmode $*' >> >> " TexLet g:Tex_CompileRule_pdf = 'dvipdfm $*.dvi' >> >> " TexLet g:Tex_CompileRule_pdf = 'dvipdf $*.dvi' >> >> TexLet g:Tex_CompileRule_html = 'latex2html $*.tex' >> >> TexLet g:Tex_CompileRule_bib = g:Tex_BibtexFlavor . ' $*' >> >> " Set Tex_UseMakefile to 0 if you want to ignore the presence of a >> >> Makefile >> >> " when deciding how to compile >> >> TexLet g:Tex_UseMakefile = 1 >> >> " }}} >> >> In case you wonder my tex.vim: >> >> " 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+=: >> >> >> >> Could you please check if I missed anything here? I appreciate your >> help! >> >> >> >> >> >> Sincerely, >> >> Jin Chen >> >> >> >> >> >> >> >> On Tue, Mar 16, 2010 at 5:57 PM, Dennis Grimminck >> >> <l.g...@sc...> wrote: >> >>> >> >>> 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.g...@sc... <mailto:l.g...@sc...>> >> 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® 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...@li... >> >>> >> <mailto:Vim...@li...> >> >>> >> 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.g...@sc... >> >>> > <mailto:L.g...@sc...> http://www.ru.nl/molphys >> >>> > >> >>> > >> >> >> >> >> >> -- >> >> 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.g...@sc... >> >> http://www.ru.nl/molphys >> > >> > >> ------------------------------------------------------------------------------ >> > Download Intel® 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...@li... >> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >> > >> > >> > > |