Thread: [Vim-latex-devel] [BUGREPORT] -output-directory isn't handled
Brought to you by:
srinathava,
tmaas
From: Christian B. <ex...@gm...> - 2012-11-11 11:33:16
|
I am using vim-latexsuite on Kubuntu 12.10 32bit. This is my compile rule [.vimrc] let g:Tex_CompileRule_pdf='mkdir -p _out && xelatex -output-directory=_out -interaction=nonstopmode $* && mv _out/$*.pdf .' [/.vimrc] You see I am using -output-directory to bundle all output-files in a subdirectorie. It is needed because no human need this files. Only the machine itself (latex compiler, etc) need and use them. So they don't have to appear in my document directory. But as I see the latexsuite is not able to handle this. It didn't show me the error-log inside vim because it didn't find the error log. And maybe it take an negative effect on some other features of vim-latex that I doesn't know currently. |
From: Devendra G. <dev...@gm...> - 2012-11-11 12:37:45
|
Christian, What do you mean by "not handle it"? 1. The output directory being generated? 2. Are the output PDF files being generated by xelatex in the output directory? 3. OR the output files are not being moved to the current folder by mv. Regards, Devendra On 11 November 2012 17:03, Christian Buhtz <ex...@gm...> wrote: > I am using vim-latexsuite on Kubuntu 12.10 32bit. > > This is my compile rule > [.vimrc] > let g:Tex_CompileRule_pdf='mkdir -p _out && xelatex -output-directory=_out > -interaction=nonstopmode $* && mv _out/$*.pdf .' > [/.vimrc] > > You see I am using -output-directory to bundle all output-files in a > subdirectorie. It is needed because no human need this files. Only the > machine itself (latex compiler, etc) need and use them. So they don't > have to appear in my document directory. > > But as I see the latexsuite is not able to handle this. > It didn't show me the error-log inside vim because it didn't find the > error log. > And maybe it take an negative effect on some other features of vim-latex > that I doesn't know currently. > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > -- Cheers, Devendra. |
From: Devendra G. <dev...@gm...> - 2012-11-11 13:45:11
|
Christian, I understand the problem now. If you add an empty 'file.tex.latexmain' (here file.tex is the one we are trying to compile), it should work. If you already have the 'file.tex.latexmain', then there is some other issue. Do let me know if this solves the problem. Devendra On 11 November 2012 17:03, Christian Buhtz <ex...@gm...> wrote: > I am using vim-latexsuite on Kubuntu 12.10 32bit. > > This is my compile rule > [.vimrc] > let g:Tex_CompileRule_pdf='mkdir -p _out && xelatex -output-directory=_out > -interaction=nonstopmode $* && mv _out/$*.pdf .' > [/.vimrc] > > You see I am using -output-directory to bundle all output-files in a > subdirectorie. It is needed because no human need this files. Only the > machine itself (latex compiler, etc) need and use them. So they don't > have to appear in my document directory. > > But as I see the latexsuite is not able to handle this. > It didn't show me the error-log inside vim because it didn't find the > error log. > And maybe it take an negative effect on some other features of vim-latex > that I doesn't know currently. > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > -- Cheers, Devendra. |
From: Christian B. <ex...@gm...> - 2012-11-11 22:17:03
|
Devendra Ghate schrieb am Sonntag, 11. November 2012 um 14:45: > I understand the problem now. If you add an empty 'file.tex.latexmain' > (here file.tex is the one we are trying to compile), it should work. If you > already have the 'file.tex.latexmain', then there is some other issue. Sorry, now I didn't understand you? What is "latexmain"? Where should I put it? Why? xelatex create and use the output directory very well. There is no problem. The problem is that the vim-latexsuite doesn't find the log file because it is in the output-directory, too. The latexsuite doesn't give any shit on the use of -output-directory. |
From: Alessandro P. <ale...@la...> - 2012-11-12 07:13:20
|
2012/11/11 Christian Buhtz <ex...@gm...>: > Devendra Ghate schrieb am Sonntag, 11. November 2012 um 14:45: >> I understand the problem now. If you add an empty 'file.tex.latexmain' >> (here file.tex is the one we are trying to compile), it should work. If you >> already have the 'file.tex.latexmain', then there is some other issue. > > Sorry, now I didn't understand you? What is "latexmain"? Where should I > put it? Why? If you are not compiling a file called "main.tex", e.g. if you are dividing your document in multiple files, then creating a (possibly empty) file with the same name as your main file with a "latexmain" suffix will tell latexsuite to compile that file. You can put settings specific to your project in that file, too. For more info, see the manual [1]. > xelatex create and use the output directory very well. There is no > problem. > The problem is that the vim-latexsuite doesn't find the log file because > it is in the output-directory, too. Probably (I'm not familiar with the code) latexsuite is relying on parsing the output of your compilation command, which gets eaten up by your last pipe. I think that latexsuite is actually relying on vim for this, which is known to be quite flaky at supporting external programs (by design). You can try to see if any of the methods suggested in this [2] blog post let you do what you want in a cleaner way. Note that the "rubber" link is dead, but you can find it on launchpad [3]. I will try to have a closer look at your issue later today, when I'll have more time. > The latexsuite doesn't give any shit on the use of -output-directory. Please, keep in mind that people here are trying to help you (out of their spare time). Alessandro [1] http://vim-latex.sourceforge.net/documentation/latex-suite/latex-project.html [2] http://phaseportrait.blogspot.it/2008/03/fixing-vim-latex-compiler-error.html [3] https://launchpad.net/rubber |
From: Alessandro P. <ale...@la...> - 2012-11-12 10:01:19
|
I'm sorry, you clearly don't have pipes in your 'g:Tex_CompileRule_pdf'. Still, I can confirm that latexsuite relies on vim's ':make' command. In particular, it sets the 'makeprg' and 'errorformat' variables to appropriate values, so that calling ':make' gives: " [...] 4. The program given with the 'makeprg' option is started (default "make") with the optional [arguments] and the output is saved in the errorfile (for Unix it is also echoed on the screen). 5. The errorfile is read using 'errorformat'. [...] " (from vim's "quickfix.txt" help page) If you set 'g:Tex_CompileRule_pdf' to 'xelatex -interaction=nonstopmode $*' does vim behave as you expect? If not, then this is probably an error parsing issue, otherwise this issue is probably related to the output of your command. Please, let me know, as I currently am unable to reproduce a xelatex latexsuite setup. Alessandro |