On Tue, 2011-02-15 at 12:34 -0500, Mike Richman wrote: > On Tue, Feb 15, 2011 at 7:04 AM, Ng Oon-Ee <ngoo...@gmail.com> wrote: > > On Mon, 2011-02-14 at 14:27 +0800, Ng Oon-Ee wrote: > >> Hi, > >> > >> I'm coming from a texlipse (Eclipse plug-in) background. Been through > >> the Latex-Suite Reference, but could not find this particular 'feature'. > >> > >> Would it be possible to do a compile in a specific subdirectory (by > >> default ./tmp in texlipse). This helps prevent clutter in the main > >> directory. > >> > >> I've not checked, but I believe texlipse does this using the > >> --output-directory option of tex/pdflatex. Would changing > >> g:Tex_CompileRule_* allow me to have this behaviour (all the temporary > >> files like aux,bbl,blg,log,out,toc in ./tmp but the final output dvi/pdf > >> in ./)? > >> > > > > I take it this is not possible, then? > > In principle, if you can determine the commands used to make it happen > in the shell, then you can get vim-latex to do it for you as well. > I've never tried compiling in a subdir, though. > > Let us know if you can manage to do it at the command line. > > -Mike Richman
Hmm, from checking more closely, it seems all texlipse does is move the temp files out of the compilation folder after a completed (or partially completed) compile. No point if its done that way then. I was thinking more along the lines of how programs can be compiled in a clean build directory, but perhaps that'd be a bit complicated/unnecessary in this situation. >From a bit of testing its obviously possible to do all output to a tmp directory. pdflatex -output-directory ./tmp foo.tex The output file (foo.pdf) would also appear there, which is where the lack of a -output-filename hampers things (if such would exist, we could just specify the filename to be something like ../foo) ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Vim-latex-devel mailing list Vim-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
