vim-latex-devel Mailing List for Vim-Latex (Page 37)
Brought to you by:
srinathava,
tmaas
Menu
▾
▴
vim-latex-devel — Mailing list for developers/maintainers of the vim-latex project
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(120) |
Dec
(118) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(145) |
Feb
(23) |
Mar
(30) |
Apr
(50) |
May
(88) |
Jun
(49) |
Jul
(41) |
Aug
(13) |
Sep
(51) |
Oct
(30) |
Nov
(80) |
Dec
(43) |
| 2004 |
Jan
(15) |
Feb
(25) |
Mar
(48) |
Apr
(12) |
May
(37) |
Jun
(52) |
Jul
(16) |
Aug
(10) |
Sep
(7) |
Oct
(19) |
Nov
(17) |
Dec
(19) |
| 2005 |
Jan
(15) |
Feb
(5) |
Mar
(7) |
Apr
(3) |
May
(2) |
Jun
(4) |
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
(16) |
Dec
(16) |
| 2006 |
Jan
(15) |
Feb
(27) |
Mar
(49) |
Apr
(31) |
May
(24) |
Jun
(12) |
Jul
(23) |
Aug
(13) |
Sep
(22) |
Oct
(6) |
Nov
(8) |
Dec
(10) |
| 2007 |
Jan
(3) |
Feb
(13) |
Mar
(19) |
Apr
(1) |
May
(5) |
Jun
(10) |
Jul
(2) |
Aug
(13) |
Sep
(10) |
Oct
(2) |
Nov
(30) |
Dec
(15) |
| 2008 |
Jan
(11) |
Feb
(9) |
Mar
(27) |
Apr
(27) |
May
(22) |
Jun
(29) |
Jul
|
Aug
(21) |
Sep
(6) |
Oct
(4) |
Nov
(9) |
Dec
(2) |
| 2009 |
Jan
(52) |
Feb
(21) |
Mar
(9) |
Apr
(41) |
May
(13) |
Jun
(8) |
Jul
(5) |
Aug
(31) |
Sep
(14) |
Oct
(10) |
Nov
(17) |
Dec
(17) |
| 2010 |
Jan
(25) |
Feb
(22) |
Mar
(22) |
Apr
(24) |
May
(35) |
Jun
(23) |
Jul
(22) |
Aug
(10) |
Sep
(6) |
Oct
(29) |
Nov
(8) |
Dec
(6) |
| 2011 |
Jan
(12) |
Feb
(89) |
Mar
(41) |
Apr
(8) |
May
(17) |
Jun
(11) |
Jul
(3) |
Aug
(13) |
Sep
(14) |
Oct
(23) |
Nov
(8) |
Dec
(9) |
| 2012 |
Jan
(15) |
Feb
(27) |
Mar
(6) |
Apr
(17) |
May
(29) |
Jun
(9) |
Jul
(50) |
Aug
(15) |
Sep
(11) |
Oct
(12) |
Nov
(22) |
Dec
(7) |
| 2013 |
Jan
(24) |
Feb
(32) |
Mar
(6) |
Apr
(5) |
May
(2) |
Jun
(15) |
Jul
(20) |
Aug
(1) |
Sep
(3) |
Oct
(2) |
Nov
(7) |
Dec
(4) |
| 2014 |
Jan
(3) |
Feb
(7) |
Mar
(4) |
Apr
|
May
(4) |
Jun
(5) |
Jul
(4) |
Aug
(3) |
Sep
(9) |
Oct
|
Nov
(2) |
Dec
(3) |
| 2015 |
Jan
|
Feb
(4) |
Mar
(9) |
Apr
|
May
(1) |
Jun
|
Jul
(5) |
Aug
(6) |
Sep
(2) |
Oct
|
Nov
(6) |
Dec
|
| 2016 |
Jan
(1) |
Feb
(11) |
Mar
(4) |
Apr
(2) |
May
(8) |
Jun
(9) |
Jul
|
Aug
(9) |
Sep
(2) |
Oct
(7) |
Nov
|
Dec
|
| 2017 |
Jan
(7) |
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
| 2018 |
Jan
(1) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(1) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: LAG G. <l.g...@sc...> - 2010-04-13 15:23:47
|
Sorry, I meant the vim manual. getcwd () is the function that determines the current directory and my guess is also what directory the Makefile should be in. What is the 'after directory'? On 04/13/2010 02:26 PM, Yan Zhou wrote: > They are not documented in the manual. The manual is rather incomplete, it's a user manual and one has to check the source code to find the problem. > > However, I have used the after directory to overrule the vim-latex suite behaviour. > > On 13 Apr 2010, at 08:47, LAG Grimminck wrote: > > >> Dear Yan, >> >> .. put your TESTED Makefile in the directory where you let your >> vim-latex compile? Otherwise maybe you should check what vim-latex uses >> as current working directory internally, check the manual for that I think. >> >> cheers, >> >> Dennis >> >> On 04/12/2010 08:06 PM, Yan Zhou wrote: >> >>> Dear all, >>> >>> I have a question about the Tex_UseMakefile. Whatever value I set it, either 1 or 0. The latex suite always define makeprg to whatever is defined by the g:Tex_CompileRule_target setting. How can I disable this behaviour and forbid latex suite to set the makeprg option? >>> >>> Many thanks in advance. >>> >>> Yan, >>> ------------------------------------------------------------------------------ >>> 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 >>> >>> >> >> >> ------------------------------------------------------------------------------ >> 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 >> > |
|
From: Yan Z. <zho...@gm...> - 2010-04-13 12:28:36
|
They are not documented in the manual. The manual is rather incomplete, it's a user manual and one has to check the source code to find the problem. However, I have used the after directory to overrule the vim-latex suite behaviour. On 13 Apr 2010, at 08:47, LAG Grimminck wrote: > Dear Yan, > > .. put your TESTED Makefile in the directory where you let your > vim-latex compile? Otherwise maybe you should check what vim-latex uses > as current working directory internally, check the manual for that I think. > > cheers, > > Dennis > > On 04/12/2010 08:06 PM, Yan Zhou wrote: >> Dear all, >> >> I have a question about the Tex_UseMakefile. Whatever value I set it, either 1 or 0. The latex suite always define makeprg to whatever is defined by the g:Tex_CompileRule_target setting. How can I disable this behaviour and forbid latex suite to set the makeprg option? >> >> Many thanks in advance. >> >> Yan, >> ------------------------------------------------------------------------------ >> 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 >> > > -- > 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 |
|
From: Gastón A. <gar...@ie...> - 2010-04-13 12:21:28
|
Dear Dennis, now I got your point, surely i have explained me very bad, sorry. Application's messages doesn't appears in a quick-fix windows, but in the X. I don't know how to explain it better, here is a snapshot window [0], and here is another moving the cursor half window down [1] Thank you again, Gastón [0] http://imagebin.ca/view/Q46pt5x.html [1] http://imagebin.ca/view/WhL_r6.html 2010/4/13 LAG Grimminck <l.g...@sc...>: > Dear Gaston, > > As you wish... My suggestion would be to remap \lv to \lv :cclose in > your .vimrc file. I did not have time to test it. But It should do the > \lv and then close the quickfix-window immediately that shows your > warning messages. > > cheers, > > Dennis > > On 04/12/2010 08:30 PM, Gastón Araguás wrote: >> Dear Dennis, >> >> thank you for your hints, like you say it is not very elegant to >> trough out messages instead off solving the problem, but if you want >> to do that you can run the application in a terminal and solve each >> error or warning you get. >> Wen i run a viewer from vim I don't want to see application's messages. >> >> still looking for a solution... >> Gastón >> >> 2010/4/12 LAG Grimminck <l.g...@sc...>: >> >>> Dear Simon, >>> >>> Okular probably has some 'watch file' option running. Till now I have >>> not found any viewer that did not have some problem with keeping the >>> document up-to-date, for example gv performs well but if the document is >>> long it cannot update the page you are looking at and it will display a >>> page further back in the document. I finally settled on using acroread >>> with ctrl+r to update my document this works nicely. So my guess would >>> be that to solve your problem you could search for this 'watch file' >>> option, disable it and find a set of keys to update the viewer manually. >>> >>> hope this helps, >>> >>> Dennis >>> >>> On 04/12/2010 09:57 AM, Simon Quittek wrote: >>> >>>> Hi, >>>> >>>> well, that is not always the case. >>>> If I type \lv and open okular to view the pdf, everything is allright. Then >>>> I hit \ll to compile and while compiling, okular looks for the nonexistent >>>> pdf and produces error messages, which remain in vim. >>>> I just start okular seperately and browse through the latest files to >>>> circumvent the problem. It's not the best tough... >>>> >>>> Cheers, >>>> Simon >>>> >>>> On 2010/04/12 8:34,LAG Grimminck <l.g...@sc...> wrote: >>>> >>>> >>>>> Dear Gaston, >>>>> >>>>> You may want to try to solve the problems the viewer apparently has, >>>>> before trying to fix things further down the stream. My viewer always >>>>> starts without any messages. >>>>> >>>>> cheers, >>>>> >>>>> Dennis >>>>> >>>>> On 04/09/2010 09:06 PM, Gastón Araguás wrote: >>>>> >>>>> >>>>>> hi all, >>>>>> >>>>>> first at all i want to say that vim-latexsuite is a wonderful plugin >>>>>> to me. Just a little problem with the pdf viewer, wen i run the >>>>>> viewer with <Leader>lv all warnings and errors from viewers (xpdf or >>>>>> evince) are printed in the screen where vim is running. Wen I swap to >>>>>> vim I have to repaint the window (with CTRL-F plus CTRL-B for example) >>>>>> to see the tex code again. >>>>>> Running the viewer directly from vim ( :!evince file.pdf) got the same >>>>>> behavior, it is only avoided with :!evince file.pdf &>/dev/nul & >>>>>> >>>>>> Is there any way to avoid this, for example introducing this command >>>>>> in tex.vim? >>>>>> >>>>>> I've try with let g:Tex_ViewRule_pdf = 'evince $ &>/dev/null&' without luck. >>>>>> >>>>>> Thank in advanced >>>>>> >>>>>> >>>>>> >>>>>> >>>>> ------------------------------------------------------------------------------ >>>>> 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 >>>>> >>>>> >>>> ------------------------------------------------------------------------------ >>>> 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 >>>> >>>> >>> -- >>> 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 >>> >>> >> >> >> > > -- > 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 > -- Gastón Araguás ______________________________________________________ CIII - Centro de Investigación en Informática para la Ingeniería Univ. Tecnológica Nacional Facultad Regional Córdoba. Argentina |
|
From: LAG G. <l.g...@sc...> - 2010-04-13 07:56:27
|
Dear Gaston, As you wish... My suggestion would be to remap \lv to \lv :cclose in your .vimrc file. I did not have time to test it. But It should do the \lv and then close the quickfix-window immediately that shows your warning messages. cheers, Dennis On 04/12/2010 08:30 PM, Gastón Araguás wrote: > Dear Dennis, > > thank you for your hints, like you say it is not very elegant to > trough out messages instead off solving the problem, but if you want > to do that you can run the application in a terminal and solve each > error or warning you get. > Wen i run a viewer from vim I don't want to see application's messages. > > still looking for a solution... > Gastón > > 2010/4/12 LAG Grimminck <l.g...@sc...>: > >> Dear Simon, >> >> Okular probably has some 'watch file' option running. Till now I have >> not found any viewer that did not have some problem with keeping the >> document up-to-date, for example gv performs well but if the document is >> long it cannot update the page you are looking at and it will display a >> page further back in the document. I finally settled on using acroread >> with ctrl+r to update my document this works nicely. So my guess would >> be that to solve your problem you could search for this 'watch file' >> option, disable it and find a set of keys to update the viewer manually. >> >> hope this helps, >> >> Dennis >> >> On 04/12/2010 09:57 AM, Simon Quittek wrote: >> >>> Hi, >>> >>> well, that is not always the case. >>> If I type \lv and open okular to view the pdf, everything is allright. Then >>> I hit \ll to compile and while compiling, okular looks for the nonexistent >>> pdf and produces error messages, which remain in vim. >>> I just start okular seperately and browse through the latest files to >>> circumvent the problem. It's not the best tough... >>> >>> Cheers, >>> Simon >>> >>> On 2010/04/12 8:34,LAG Grimminck <l.g...@sc...> wrote: >>> >>> >>>> Dear Gaston, >>>> >>>> You may want to try to solve the problems the viewer apparently has, >>>> before trying to fix things further down the stream. My viewer always >>>> starts without any messages. >>>> >>>> cheers, >>>> >>>> Dennis >>>> >>>> On 04/09/2010 09:06 PM, Gastón Araguás wrote: >>>> >>>> >>>>> hi all, >>>>> >>>>> first at all i want to say that vim-latexsuite is a wonderful plugin >>>>> to me. Just a little problem with the pdf viewer, wen i run the >>>>> viewer with <Leader>lv all warnings and errors from viewers (xpdf or >>>>> evince) are printed in the screen where vim is running. Wen I swap to >>>>> vim I have to repaint the window (with CTRL-F plus CTRL-B for example) >>>>> to see the tex code again. >>>>> Running the viewer directly from vim ( :!evince file.pdf) got the same >>>>> behavior, it is only avoided with :!evince file.pdf &>/dev/nul & >>>>> >>>>> Is there any way to avoid this, for example introducing this command >>>>> in tex.vim? >>>>> >>>>> I've try with let g:Tex_ViewRule_pdf = 'evince $ &>/dev/null&' without luck. >>>>> >>>>> Thank in advanced >>>>> >>>>> >>>>> >>>>> >>>> ------------------------------------------------------------------------------ >>>> 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 >>>> >>>> >>> ------------------------------------------------------------------------------ >>> 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 >>> >>> >> -- >> 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 >> >> > > > -- 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 |
|
From: LAG G. <l.g...@sc...> - 2010-04-13 07:48:16
|
Dear Yan, .. put your TESTED Makefile in the directory where you let your vim-latex compile? Otherwise maybe you should check what vim-latex uses as current working directory internally, check the manual for that I think. cheers, Dennis On 04/12/2010 08:06 PM, Yan Zhou wrote: > Dear all, > > I have a question about the Tex_UseMakefile. Whatever value I set it, either 1 or 0. The latex suite always define makeprg to whatever is defined by the g:Tex_CompileRule_target setting. How can I disable this behaviour and forbid latex suite to set the makeprg option? > > Many thanks in advance. > > Yan, > ------------------------------------------------------------------------------ > 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 > -- 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 |
|
From: Gastón A. <gar...@ie...> - 2010-04-12 18:30:37
|
Dear Dennis, thank you for your hints, like you say it is not very elegant to trough out messages instead off solving the problem, but if you want to do that you can run the application in a terminal and solve each error or warning you get. Wen i run a viewer from vim I don't want to see application's messages. still looking for a solution... Gastón 2010/4/12 LAG Grimminck <l.g...@sc...>: > Dear Simon, > > Okular probably has some 'watch file' option running. Till now I have > not found any viewer that did not have some problem with keeping the > document up-to-date, for example gv performs well but if the document is > long it cannot update the page you are looking at and it will display a > page further back in the document. I finally settled on using acroread > with ctrl+r to update my document this works nicely. So my guess would > be that to solve your problem you could search for this 'watch file' > option, disable it and find a set of keys to update the viewer manually. > > hope this helps, > > Dennis > > On 04/12/2010 09:57 AM, Simon Quittek wrote: >> Hi, >> >> well, that is not always the case. >> If I type \lv and open okular to view the pdf, everything is allright. Then >> I hit \ll to compile and while compiling, okular looks for the nonexistent >> pdf and produces error messages, which remain in vim. >> I just start okular seperately and browse through the latest files to >> circumvent the problem. It's not the best tough... >> >> Cheers, >> Simon >> >> On 2010/04/12 8:34,LAG Grimminck <l.g...@sc...> wrote: >> >>> Dear Gaston, >>> >>> You may want to try to solve the problems the viewer apparently has, >>> before trying to fix things further down the stream. My viewer always >>> starts without any messages. >>> >>> cheers, >>> >>> Dennis >>> >>> On 04/09/2010 09:06 PM, Gastón Araguás wrote: >>> >>>> hi all, >>>> >>>> first at all i want to say that vim-latexsuite is a wonderful plugin >>>> to me. Just a little problem with the pdf viewer, wen i run the >>>> viewer with <Leader>lv all warnings and errors from viewers (xpdf or >>>> evince) are printed in the screen where vim is running. Wen I swap to >>>> vim I have to repaint the window (with CTRL-F plus CTRL-B for example) >>>> to see the tex code again. >>>> Running the viewer directly from vim ( :!evince file.pdf) got the same >>>> behavior, it is only avoided with :!evince file.pdf &>/dev/nul & >>>> >>>> Is there any way to avoid this, for example introducing this command >>>> in tex.vim? >>>> >>>> I've try with let g:Tex_ViewRule_pdf = 'evince $ &>/dev/null&' without luck. >>>> >>>> Thank in advanced >>>> >>>> >>>> >>> >>> ------------------------------------------------------------------------------ >>> 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 >>> >> ------------------------------------------------------------------------------ >> 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 >> > > -- > 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 > -- Gastón Araguás ______________________________________________________ CIII - Centro de Investigación en Informática para la Ingeniería Univ. Tecnológica Nacional Facultad Regional Córdoba. Argentina |
|
From: Yan Z. <zho...@gm...> - 2010-04-12 18:06:21
|
Dear all, I have a question about the Tex_UseMakefile. Whatever value I set it, either 1 or 0. The latex suite always define makeprg to whatever is defined by the g:Tex_CompileRule_target setting. How can I disable this behaviour and forbid latex suite to set the makeprg option? Many thanks in advance. Yan, |
|
From: LAG G. <l.g...@sc...> - 2010-04-12 08:05:58
|
Dear Simon, Okular probably has some 'watch file' option running. Till now I have not found any viewer that did not have some problem with keeping the document up-to-date, for example gv performs well but if the document is long it cannot update the page you are looking at and it will display a page further back in the document. I finally settled on using acroread with ctrl+r to update my document this works nicely. So my guess would be that to solve your problem you could search for this 'watch file' option, disable it and find a set of keys to update the viewer manually. hope this helps, Dennis On 04/12/2010 09:57 AM, Simon Quittek wrote: > Hi, > > well, that is not always the case. > If I type \lv and open okular to view the pdf, everything is allright. Then > I hit \ll to compile and while compiling, okular looks for the nonexistent > pdf and produces error messages, which remain in vim. > I just start okular seperately and browse through the latest files to > circumvent the problem. It's not the best tough... > > Cheers, > Simon > > On 2010/04/12 8:34,LAG Grimminck <l.g...@sc...> wrote: > >> Dear Gaston, >> >> You may want to try to solve the problems the viewer apparently has, >> before trying to fix things further down the stream. My viewer always >> starts without any messages. >> >> cheers, >> >> Dennis >> >> On 04/09/2010 09:06 PM, Gastón Araguás wrote: >> >>> hi all, >>> >>> first at all i want to say that vim-latexsuite is a wonderful plugin >>> to me. Just a little problem with the pdf viewer, wen i run the >>> viewer with <Leader>lv all warnings and errors from viewers (xpdf or >>> evince) are printed in the screen where vim is running. Wen I swap to >>> vim I have to repaint the window (with CTRL-F plus CTRL-B for example) >>> to see the tex code again. >>> Running the viewer directly from vim ( :!evince file.pdf) got the same >>> behavior, it is only avoided with :!evince file.pdf &>/dev/nul & >>> >>> Is there any way to avoid this, for example introducing this command >>> in tex.vim? >>> >>> I've try with let g:Tex_ViewRule_pdf = 'evince $ &>/dev/null&' without luck. >>> >>> Thank in advanced >>> >>> >>> >> >> ------------------------------------------------------------------------------ >> 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 >> > ------------------------------------------------------------------------------ > 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 > -- 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 |
|
From: Simon Q. <sim...@gm...> - 2010-04-12 07:58:05
|
Hi, well, that is not always the case. If I type \lv and open okular to view the pdf, everything is allright. Then I hit \ll to compile and while compiling, okular looks for the nonexistent pdf and produces error messages, which remain in vim. I just start okular seperately and browse through the latest files to circumvent the problem. It's not the best tough... Cheers, Simon On 2010/04/12 8:34,LAG Grimminck <l.g...@sc...> wrote: > Dear Gaston, > > You may want to try to solve the problems the viewer apparently has, > before trying to fix things further down the stream. My viewer always > starts without any messages. > > cheers, > > Dennis > > On 04/09/2010 09:06 PM, Gastón Araguás wrote: >> hi all, >> >> first at all i want to say that vim-latexsuite is a wonderful plugin >> to me. Just a little problem with the pdf viewer, wen i run the >> viewer with <Leader>lv all warnings and errors from viewers (xpdf or >> evince) are printed in the screen where vim is running. Wen I swap to >> vim I have to repaint the window (with CTRL-F plus CTRL-B for example) >> to see the tex code again. >> Running the viewer directly from vim ( :!evince file.pdf) got the same >> behavior, it is only avoided with :!evince file.pdf &>/dev/nul & >> >> Is there any way to avoid this, for example introducing this command >> in tex.vim? >> >> I've try with let g:Tex_ViewRule_pdf = 'evince $ &>/dev/null&' without luck. >> >> Thank in advanced >> >> > > > ------------------------------------------------------------------------------ > 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 |
|
From: LAG G. <l.g...@sc...> - 2010-04-12 06:34:44
|
Dear Gaston, You may want to try to solve the problems the viewer apparently has, before trying to fix things further down the stream. My viewer always starts without any messages. cheers, Dennis On 04/09/2010 09:06 PM, Gastón Araguás wrote: > hi all, > > first at all i want to say that vim-latexsuite is a wonderful plugin > to me. Just a little problem with the pdf viewer, wen i run the > viewer with <Leader>lv all warnings and errors from viewers (xpdf or > evince) are printed in the screen where vim is running. Wen I swap to > vim I have to repaint the window (with CTRL-F plus CTRL-B for example) > to see the tex code again. > Running the viewer directly from vim ( :!evince file.pdf) got the same > behavior, it is only avoided with :!evince file.pdf &>/dev/nul & > > Is there any way to avoid this, for example introducing this command > in tex.vim? > > I've try with let g:Tex_ViewRule_pdf = 'evince $ &>/dev/null&' without luck. > > Thank in advanced > > |
|
From: DI <dae...@gm...> - 2010-04-11 21:53:50
|
I recently installed vim-latex on my computer, and I've come across a
conflict with using langmap and Cyrillic characters. I have the following
line in my vimrc:
set
langmap=й',ц\,,у.,кp,еy,нf,гg,шc,щr,зl,х/,ъ=,фa,ыo,вe,аu,пi,рd,оh,лt,дn,жs,э-,я\\;,чq,сj,мk,иx,тb,ьm,бw,юv,.z,ё`,Й\",Ц<,У>,КP,ЕY,НF,ГG,ШC,ЩR,ЗL,Х?,Ъ+,ФA,ЫO,ВE,АU,ПI,РD,ОH,ЛT,ДN,ЖS,Э_,Я:,ЧQ,СJ,МK,ИX,ТB,ЬM,БW,ЮV,\,Z,\\;$,-[,=],Ё~
It converts commands in normal mode from the Russian keyboard to the Dvorak
keyboard. However, if this line is included with vim-latex, insert mode
becomes impossible to use. Whenever I type in a character, the following
output appears in the file:
<SNR>12_LookupCharacter("a")
<SNR>12_LookupCharacter("o")
<SNR>12_LookupCharacter("e")
<SNR>12_LookupCharacter("u")
Where "a", "o", "e", "u", are characters that I typed in.
I have tested this with the Debian and Ubuntu repository versions of
vim-latexsuite, as well as the with latest snapshot on Sourceforge.
Thanks for maintaining vim-latex!
Siyang Chen
|
|
From: Gastón A. <gar...@ie...> - 2010-04-09 19:06:46
|
hi all, first at all i want to say that vim-latexsuite is a wonderful plugin to me. Just a little problem with the pdf viewer, wen i run the viewer with <Leader>lv all warnings and errors from viewers (xpdf or evince) are printed in the screen where vim is running. Wen I swap to vim I have to repaint the window (with CTRL-F plus CTRL-B for example) to see the tex code again. Running the viewer directly from vim ( :!evince file.pdf) got the same behavior, it is only avoided with :!evince file.pdf &>/dev/nul & Is there any way to avoid this, for example introducing this command in tex.vim? I've try with let g:Tex_ViewRule_pdf = 'evince $ &>/dev/null&' without luck. Thank in advanced -- Gastón Araguás ______________________________________________________ CIII - Centro de Investigación en Informática para la Ingeniería Univ. Tecnológica Nacional Facultad Regional Córdoba. Argentina |
|
From: fain182 <fa...@gm...> - 2010-04-04 09:11:18
|
Hello, i don't know how to indent my latex code.. if i go to the first line with gg, and indent all with =G, the rules for indentation are wrong..(for example, indent if at the end of line there is a "\\" or a ",") Vim-latexsuite includes latex indentation rules? How can i set them in my .vimrc? thank you -- pietro |
|
From: Ted P. <te...@te...> - 2010-03-24 17:53:53
|
vim-latex documents the use of %%fakesection to create new folds at the
same level as \section folds. To organize my preamble and backmatter, I
use similar sections like %%fakepart, %%fakechapter, %%fakesubsection, etc.
The attached one-line patch modifies the section of folding.vim so that
it looks for %%fake and not just %%fakesection. That lets me update
g:Tex_FoldedSections to include all of my other %%fake... sections.
--Ted
--
Ted Pavlic <te...@te...>
Please visit my 2009 d'Feet ALS walk page:
http://web.alsa.org/goto/tedp
My family appreciates your support in the fight to defeat ALS.
|
|
From: Ted P. <te...@te...> - 2010-03-24 17:20:03
|
> You might be able to add something for this in a .latexmain file, but
> then you would need to have two files. The docs should give some more
> information about the .latexmain file.
Another option is to create a Makefile that responds in your desired way
regardless of which target is called. Again, you would have two files,
but this way you could still execute easily execute your custom build
commands from the CLI as well as from within vim.
--Ted
--
Ted Pavlic <te...@te...>
Please visit my 2009 d'Feet ALS walk page:
http://web.alsa.org/goto/tedp
My family appreciates your support in the fight to defeat ALS.
|
|
From: Till M. <ope...@ti...> - 2010-03-23 22:17:22
|
On Tue, Mar 23, 2010 at 10:23:04AM +0100, Udo Hortian wrote: > I would like to set TTarget this way, but this seems not to be possible. > Or am I missing some possibility here? You might be able to add something for this in a .latexmain file, but then you would need to have two files. The docs should give some more information about the .latexmain file. Regards Till |
|
From: Gary J. <gar...@sp...> - 2010-03-23 20:43:20
|
On 2010-03-23, Udo Hortian <udo...@we...> wrote:
> Hello,
>
> Normally I compile my LaTeX documents with latex, but some I need to
> compile with pdflatex. I would like to store this setting in the .tex
> file like one can store other vim specific settings like the following:
>
> /* ex: set tabstop=8 expandtab: */
>
> I would like to set TTarget this way, but this seems not to be possible.
> Or am I missing some possibility here?
According to
:help modeline
Vim allows only certain options to be set in a modeline, for
security reasons.
Here's something you might try.
Put one of the following lines at the bottom of each of your .tex
files:
% TTarget latex
or
% TTarget pdflatex
Put the following in your ~/.vim/after/ftplugin/tex.vim file.
let compiler = matchstr(getline("$"), '^% TTarget \zs.*')
if compiler != ''
" Execute whatever command will set TTarget according to the
" value of compiler. I don't understand vim-latex-suite
" well enough to know what goes here.
endif
HTH,
Gary
|
|
From: ZyX <zy...@np...> - 2010-03-23 14:54:38
|
Ответ на сообщение «[Vim-latex-devel] After error during compilation cannot return to .tex document», присланное в 13:57:01 23 марта 2010, Вторник, отправитель Udo Hortian: Try <C-o> in normal mode. Текст сообщения: > Hello, > > I am not sure what is happening exactly, but I often encounter the > following situation using (g)vim with latex-suite: > > I am compiling a LaTeX document from within vim (via ll) and errors > occur during the compilation (I think this mostly happened with > undefined references). After the compilation I find myself with the .bbl > file opened and the error log below. It seems that my usual .tex file is > closed. At least I cannot find it. How can I easily return to my .tex > document? > > Best, > Udo > > --------------------------------------------------------------------------- > --- 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 > |
|
From: Udo H. <udo...@we...> - 2010-03-23 11:02:04
|
Hello, I am not sure what is happening exactly, but I often encounter the following situation using (g)vim with latex-suite: I am compiling a LaTeX document from within vim (via ll) and errors occur during the compilation (I think this mostly happened with undefined references). After the compilation I find myself with the .bbl file opened and the error log below. It seems that my usual .tex file is closed. At least I cannot find it. How can I easily return to my .tex document? Best, Udo |
|
From: Udo H. <udo...@we...> - 2010-03-23 09:23:48
|
Hello, Normally I compile my LaTeX documents with latex, but some I need to compile with pdflatex. I would like to store this setting in the .tex file like one can store other vim specific settings like the following: /* ex: set tabstop=8 expandtab: */ I would like to set TTarget this way, but this seems not to be possible. Or am I missing some possibility here? Best, Udo |
|
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
>> >
>> >
>>
>
>
|
|
From: Jin C. <che...@gm...> - 2010-03-18 01:24:45
|
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
> >
> >
>
|
|
From: Jin C. <che...@gm...> - 2010-03-17 16:48:21
|
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
>
>
|
|
From: Gary J. <gar...@sp...> - 2010-03-17 15:17:05
|
On 2010-03-17, Yue-Jun Yin <yj...@gm...> wrote:
> Any one is using gvim-latex in windows 7 (64bit)? I could not get it
> work properly. \ll,\lv commands work in vim (NOT gvim). However it dose
> not work in gvim (i.e., GUI of vim). When I use \ll under gvim, many red
> lines pop up and disappear. I don't even have a chance to read what it
> is complaining. More information about the configuration.
To find out what those red lines were, execute
:messages
Regards,
Gary
|
|
From: Yue-Jun Y. <yj...@gm...> - 2010-03-17 14:50:51
|
Any one is using gvim-latex in windows 7 (64bit)? I could not get it work properly. \ll,\lv commands work in vim (NOT gvim). However it dose not work in gvim (i.e., GUI of vim). When I use \ll under gvim, many red lines pop up and disappear. I don't even have a chance to read what it is complaining. More information about the configuration. windows 7 home edition, 64 bit vim 7.2 (latest version) MikTex2.8 (latest version) I appreciate your comments and help. -- Yue-Jun Yin (Eugene) PhD Candidate Civil& Environmental Engineering Dept. Michigan Tech University 1400 Townsend Dr. Houghton, MI 49931 USA http://www.cee.mtu.edu/~yuejuny/ |
34 messages has been excluded from this view by a project administrator.
