vim-latex-devel — Mailing list for developers/maintainers of the vim-latex project

Re: [Vim-latex-devel] New line in mapping

[Gerd W. <ger...@ma...>]

Try

call IMAP('DEF', '\begin{definition}\<CR><++>\<CR>\end{definition}<++>',
'tex')

Regards
Gerd

On 01/18/2012 07:58 PM, abstractd wrote:
> How do I change the following
> call IMAP('DEF', '\begin{definition}<++>\end{definition}<++>', 'tex')
> (in my tex.vim) such that it adds an empty line between begin and end. That
> is, I want the result to be:
> \begin{definition}
> <++>
> \end{definition}<++>
> 
> I've tried a bunch of different things but I don't get it to work.
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> 
> 
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

[Vim-latex-devel] New line in mapping

[abstractd <abs...@gm...>]

How do I change the following
call IMAP('DEF', '\begin{definition}<++>\end{definition}<++>', 'tex')
(in my tex.vim) such that it adds an empty line between begin and end. That
is, I want the result to be:
\begin{definition}
<++>
\end{definition}<++>

I've tried a bunch of different things but I don't get it to work.

[Vim-latex-devel] latex suite and R/sweave

[hl <hl....@go...>]

I am using both the latex suite plugin and the vim-r-plugin quite 
regularly.

With Sweave, an R package, it is possible to write documents that 
contain both latex and R code. Sweave is called on the document, 
generates a tex file which is then used to generate a pdf. these files 
typically end with .rnw and are recognized by the vim-r-plugin, and the 
latex suite plugin is also activated (I suspect the author of the R 
plugin is responsible for this).

this is helpful, since most mappings also work now, e.g. F5, F9, 
<leader>ll (although this one doesn't have any effect). However, 
<leader>lv gives the error message "calling Tex_View_LaTeX from a 
non-tex file". Would it be possible to activate this (and other mappings 
that are filetype-dependent) for .rnw files?

regards,

Helge

Re: [Vim-latex-devel] Using Forward Search with xdvi

[David A. <ad...@tc...>]

This is a very similar problem to the one I posted about yap in
windows. Probably makes sense to have a similar approach.

2011/12/13 "Rüdiger Kürsten" <rue...@gm...>:
> hi everybody,
>
> i have problems using forward search, when i use the xdvi viewer with further options.
> i'm using Latex-Suite: version 1.8.23 together with vim version 7.1.314
> the latex part of my vim.rc is:
>
> let g:tex_flavor='latex'
> let g:Tex_ViewRule_dvi = 'xdvi -fullscreen -hush -hushstdout -s 6'
> let g:Tex_MultipleCompileFormats = 'dvi'
> let g:Tex_CompileRule_dvi = 'latex --src-specials -interaction=nonstopmode $*'
>
> the problem appears if xdvi is used as viewer with any option.
> when i edit a latex file and typ \ls nothing happens, one the other hand \lv works as desired.
>
> i figured out that in the file
> .vim/ftplugin/latex-suite/compile.vim
> in the function Tex_ForwardSearchLatex()
> there is defined the variable viewer:
>
>        let viewer = Tex_GetVarValue('Tex_ViewRule_'.s:target)
>
> later on the variable viewer is compared to "xdvi", cleary if viewer has the value "xdvi -option" it is not recognised as "xdvi".
>
> i would suggest to cut the first word out of the variable viewer and use this for the comparisons with "xdvi"
>
> regards,
> ruediger
>
> --
> NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
> Jetzt informieren: http://www.gmx.net/de/go/freephone
>
> ------------------------------------------------------------------------------
> Systems Optimization Self Assessment
> Improve efficiency and utilization of IT resources. Drive out cost and
> improve service delivery. Take 5 minutes to use this Systems Optimization
> Self Assessment. http://www.accelacomm.com/jaw/sdnl/114/51450054/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] Using Forward Search with xdvi

[Ted P. <te...@te...>]

2011/12/13 "Rüdiger Kürsten" <rue...@gm...>:
> i would suggest to cut the first word out of the variable viewer and use this for the comparisons with "xdvi"

Good point. I just committed a change to the git repository that
should do exactly that. I did a quick test with xdvi, but it wasn't
exhaustive.

See if the change works for you.

commit 8b62284128414dc14:

http://vim-latex.git.sourceforge.net/git/gitweb.cgi?p=vim-latex/vim-latex;a=commit;h=8b62284128414dc141f633d70e5972b8028ccaef

diff:

http://vim-latex.git.sourceforge.net/git/gitweb.cgi?p=vim-latex/vim-latex;a=blobdiff;f=ftplugin/latex-suite/compiler.vim;h=4c081fee4833d5baa78c4b4694da5e856b3b3fcb;hp=08b0509dd006af942f524ca260477ce2f00d8fc1;hb=8b62284128414dc141f633d70e5972b8028ccaef;hpb=36d275da3266c1b0cdc8f525f4d977d0154241f1

Best --
Ted

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Using Forward Search with xdvi

[Philipp H. <ph...@ph...>]

Hi,

I also had this problem in the past and I've worked around it by putting the 
xdvi options I want into my .Xdefaults instead of changing Tex_ViewRule_dvi. 
The entries look as follows:

xdvi.Hush:			True
xdvi.shrinkFactor:	5
xdvi.expertMode:	0
[...]

All the options are listed and explained in the man page for xdvi. But I agree 
that fixing this in the source would be desirable.

Regards,
Philipp

[Vim-latex-devel] Using Forward Search with xdvi

[Rüdiger K. <rue...@gm...>]

hi everybody,

i have problems using forward search, when i use the xdvi viewer with further options.
i'm using Latex-Suite: version 1.8.23 together with vim version 7.1.314
the latex part of my vim.rc is:

let g:tex_flavor='latex'
let g:Tex_ViewRule_dvi = 'xdvi -fullscreen -hush -hushstdout -s 6'
let g:Tex_MultipleCompileFormats = 'dvi'
let g:Tex_CompileRule_dvi = 'latex --src-specials -interaction=nonstopmode $*'

the problem appears if xdvi is used as viewer with any option.
when i edit a latex file and typ \ls nothing happens, one the other hand \lv works as desired.

i figured out that in the file
.vim/ftplugin/latex-suite/compile.vim
in the function Tex_ForwardSearchLatex()
there is defined the variable viewer:

        let viewer = Tex_GetVarValue('Tex_ViewRule_'.s:target)

later on the variable viewer is compared to "xdvi", cleary if viewer has the value "xdvi -option" it is not recognised as "xdvi".

i would suggest to cut the first word out of the variable viewer and use this for the comparisons with "xdvi"

regards,
ruediger

-- 
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!		
Jetzt informieren: http://www.gmx.net/de/go/freephone

Re: [Vim-latex-devel] Windows Problems

[Ted P. <te...@te...>]

David --

	Errorformat issues with Vim and LaTeX are well-known, well-documented,
and have several "fixes."

	To start, see the review at:

http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html

To summarize, modern TeX and pdfTeX accept arguments that generate
compiler-like error messages that are compatible with Vim.
Unfortunately, it doesn't help much with warnings. There are then other
ways to sanitize (like using the "vimlatex" script) LaTeX error messages
by ensuring that two closing parentheses don't occur on the same line.
Finally, you can further sanitize TeX error messages by using a more
sophisticated wrapper like rubber which should have the ability to
convert both warnings and error messages into compiler-like strings that
Vim can handle.

	Best --
	Ted

On 12/06/2011 02:45 PM, David Adley wrote:
> The second problem isn't windows specific rather the 'errorformat'
> string is just not sophisticated to deal with my somewhat complicated
> latex output and gets confused. I had a look at the errorformat string
> in the compiler/tex.vim file but I couldn't figure it out. I might have
> another look but for the moment if anyone has quick of debugging the
> problem (something like :cexpr) here is the latex output
> 
> This is pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7)
> entering extended mode
> (intronew.tex
> LaTeX2e <2005/12/01>
> Babel <v3.8h> and hyphenation patterns for english, dumylang,
> nohyphenation, ge
> rman, ngerman, french, loaded.
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\base\article.cls"
> Document Class: article 2005/09/16 v1.4f Standard LaTeX document class
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\base\size10.clo"))
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsmath\amsmath.sty"
> For additional information on amsmath, use the `?' option.
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsmath\amstext.sty"
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsmath\amsgen.sty"))
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsmath\amsbsy.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsmath\amsopn.sty"))
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amscls\amsthm.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsfonts\amssymb.sty"
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsfonts\amsfonts.sty"))
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\setspace\setspace.sty"
> Package: `setspace' 6.7 <2000/12/01>
> ) ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\graphics\graphicx.sty"
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\graphics\keyval.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\graphics\graphics.sty"
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\graphics\trig.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\00miktex\graphics.cfg")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\graphics\dvips.def")))
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\ltxmisc\parskip.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\tools\array.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\caption\caption.sty"
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\caption\caption3.sty"))
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\preprint\authblk.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\subfig\subfig.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\was\upgreek.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\jknappen\mathrsfs.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\float\float.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\ltxmisc\braket.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\ltxmisc\threeparttable.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\was\gensymb.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\tools\showkeys.sty")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\xcolor\xcolor.sty"
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\00miktex\color.cfg")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\colortbl\colortbl.sty"))
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\wrapfig\wrapfig.sty")
> (intronew.aux)
> 
> Package gensymb Warning: Not defining \perthousand.
> 
> 
> Package gensymb Warning: Not defining \micro.
> 
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsfonts\umsa.fd")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsfonts\umsb.fd")
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\jknappen\ursfs.fd") [1]
> ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\base\omscmr.fd") [2] [3] [4]
> [5] [6] [7]
> Overfull \hbox (0.39636pt too wide) in paragraph at lines 504--507
> []\OT1/cmr/m/n/10 The Schrodinger equa-tion is the re-sult of solv-ing
> equa-ti
> ons 26[] and 27[] for $\OML/cmm/m/it/10 E\OT1/cmr/m/n/10
> (\OML/cmm/m/it/10 x; 
> t\OT1/cmr/m/n/10 )$
> [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22]
> [23] [24] [25] [26] [27] [28]
> Overfull \hbox (34.20609pt too wide) in paragraph at lines 1963--1970
>  [][] 
> [29] [30] [31] [32] [33] [34] [35] [36] [37] [38] <figs/Brillouin_Zone.eps>
> [39] [40] [41] [42] [43] [44]
> Overfull \hbox (0.91194pt too wide) in paragraph at lines 3078--3078
> []\OT1/cmr/bx/n/10 Normal modes of three di-men-sional monatomic and
> poly-atomi
> c Bravis
> [45] [46] <figs/si_phonon_curve.eps> [47] [48] [49] [50] [51] [52]
> <figs/Band_structure_Si_schematic.eps> [53] [54] <figs/weber771_Ge.eps>
> [55] [56] [57] [58] [59] [60] [61]
> Overfull \hbox (57.93492pt too wide) in paragraph at lines 4215--4215
> [] 
> [62] <figs/quantum_vertices_descr.eps> [63]
> Overfull \hbox (3.40059pt too wide) in paragraph at lines 4349--4349
> [] 
> [64]
> Overfull \hbox (9.81105pt too wide) in paragraph at lines 4433--4468
>  [][] 
> [65] [66] [67] [68] [69] [70] [71] [72] (intronew.aux) )
> (see the transcript file for additional information)
> Output written on intronew.dvi (72 pages, 309336 bytes).
> Transcript written on intronew.log.
> 
> 
> On 6 December 2011 03:09, David Adley <ad...@tc...
> <mailto:ad...@tc...>> wrote:
> 
>     Hi all,
> 
>     I've encountered a few problems getting vim-latex to run on windows.
> 
>     1) Forward src-specials don't work. This is because the equality in
>     compiler.tex on line 346 (latest snapshot release) is 'yap' while
>     the default setting for 'Tex_ViewRule_Dvi' is 'yap -1' so obviously
>     these will never equate changing the equality on line 346 works
>     (viewer ==? 'yap- 1') changing Tex_ViewRule_Dvi to 'yap' also works
>     but it means that multiple instances open everytime '\ls' is used
>     which is no good.
> 
>     2) The quickfix window doesn't work at all. I've spent a bit of time
>     on this and I narrowed down the problem. In windows the default qf
>     behaviour is 'broken'. Therefore typing ':normal! \<escape>'  when
>     in the qf window doesn't work the cursor just stays where it is. 
> 
>     This is because the 'bufnr' in each item of the quickfix window (see
>     getqflist()) is set to zero. It doesn't know what buffer the error
>     points to. 
>     I've hacked around this by replacing the ':normal! \<escape>' call
>     to 'wincmd k' and it works but I'd be interested if anyone has a
>     solution.
> 
>     David
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Cloud Services Checklist: Pricing and Packaging Optimization
> This white paper is intended to serve as a reference, checklist and point of 
> discussion for anyone considering optimizing the pricing and packaging model 
> of a cloud services business. Read Now!
> http://www.accelacomm.com/jaw/sfnl/114/51491232/
> 
> 
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Windows Problems

[David A. <ad...@tc...>]

The second problem isn't windows specific rather the 'errorformat' string
is just not sophisticated to deal with my somewhat complicated latex output
and gets confused. I had a look at the errorformat string in the
compiler/tex.vim file but I couldn't figure it out. I might have another
look but for the moment if anyone has quick of debugging the problem
(something like :cexpr) here is the latex output

This is pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7)
entering extended mode
(intronew.tex
LaTeX2e <2005/12/01>
Babel <v3.8h> and hyphenation patterns for english, dumylang,
nohyphenation, ge
rman, ngerman, french, loaded.
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\base\article.cls"
Document Class: article 2005/09/16 v1.4f Standard LaTeX document class
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\base\size10.clo"))
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsmath\amsmath.sty"
For additional information on amsmath, use the `?' option.
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsmath\amstext.sty"
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsmath\amsgen.sty"))
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsmath\amsbsy.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsmath\amsopn.sty"))
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amscls\amsthm.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsfonts\amssymb.sty"
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsfonts\amsfonts.sty"))
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\setspace\setspace.sty"
Package: `setspace' 6.7 <2000/12/01>
) ("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\graphics\graphicx.sty"
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\graphics\keyval.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\graphics\graphics.sty"
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\graphics\trig.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\00miktex\graphics.cfg")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\graphics\dvips.def")))
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\ltxmisc\parskip.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\tools\array.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\caption\caption.sty"
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\caption\caption3.sty"))
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\preprint\authblk.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\subfig\subfig.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\was\upgreek.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\jknappen\mathrsfs.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\float\float.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\ltxmisc\braket.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\ltxmisc\threeparttable.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\was\gensymb.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\tools\showkeys.sty")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\xcolor\xcolor.sty"
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\00miktex\color.cfg")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\colortbl\colortbl.sty"))
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\wrapfig\wrapfig.sty")
(intronew.aux)

Package gensymb Warning: Not defining \perthousand.


Package gensymb Warning: Not defining \micro.

("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsfonts\umsa.fd")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\amsfonts\umsb.fd")
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\jknappen\ursfs.fd") [1]
("C:\Program Files (x86)\MiKTeX 2.7\tex\latex\base\omscmr.fd") [2] [3] [4]
[5] [6] [7]
Overfull \hbox (0.39636pt too wide) in paragraph at lines 504--507
[]\OT1/cmr/m/n/10 The Schrodinger equa-tion is the re-sult of solv-ing
equa-ti
ons 26[] and 27[] for $\OML/cmm/m/it/10 E\OT1/cmr/m/n/10 (\OML/cmm/m/it/10
x;
t\OT1/cmr/m/n/10 )$
[8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22]
[23] [24] [25] [26] [27] [28]
Overfull \hbox (34.20609pt too wide) in paragraph at lines 1963--1970
 [][]
[29] [30] [31] [32] [33] [34] [35] [36] [37] [38] <figs/Brillouin_Zone.eps>
[39] [40] [41] [42] [43] [44]
Overfull \hbox (0.91194pt too wide) in paragraph at lines 3078--3078
[]\OT1/cmr/bx/n/10 Normal modes of three di-men-sional monatomic and
poly-atomi
c Bravis
[45] [46] <figs/si_phonon_curve.eps> [47] [48] [49] [50] [51] [52]
<figs/Band_structure_Si_schematic.eps> [53] [54] <figs/weber771_Ge.eps>
[55] [56] [57] [58] [59] [60] [61]
Overfull \hbox (57.93492pt too wide) in paragraph at lines 4215--4215
[]
[62] <figs/quantum_vertices_descr.eps> [63]
Overfull \hbox (3.40059pt too wide) in paragraph at lines 4349--4349
[]
[64]
Overfull \hbox (9.81105pt too wide) in paragraph at lines 4433--4468
 [][]
[65] [66] [67] [68] [69] [70] [71] [72] (intronew.aux) )
(see the transcript file for additional information)
Output written on intronew.dvi (72 pages, 309336 bytes).
Transcript written on intronew.log.


On 6 December 2011 03:09, David Adley <ad...@tc...> wrote:

> Hi all,
>
> I've encountered a few problems getting vim-latex to run on windows.
>
> 1) Forward src-specials don't work. This is because the equality in
> compiler.tex on line 346 (latest snapshot release) is 'yap' while the
> default setting for 'Tex_ViewRule_Dvi' is 'yap -1' so obviously these will
> never equate changing the equality on line 346 works (viewer ==? 'yap- 1')
> changing Tex_ViewRule_Dvi to 'yap' also works but it means that multiple
> instances open everytime '\ls' is used which is no good.
>
> 2) The quickfix window doesn't work at all. I've spent a bit of time on
> this and I narrowed down the problem. In windows the default qf behaviour
> is 'broken'. Therefore typing ':normal! \<escape>'  when in the qf window
> doesn't work the cursor just stays where it is.
>
> This is because the 'bufnr' in each item of the quickfix window (see
> getqflist()) is set to zero. It doesn't know what buffer the error points
> to.
> I've hacked around this by replacing the ':normal! \<escape>' call to
> 'wincmd k' and it works but I'd be interested if anyone has a solution.
>
> David
>

[Vim-latex-devel] Windows Problems

[David A. <ad...@tc...>]

Hi all,

I've encountered a few problems getting vim-latex to run on windows.

1) Forward src-specials don't work. This is because the equality in
compiler.tex on line 346 (latest snapshot release) is 'yap' while the
default setting for 'Tex_ViewRule_Dvi' is 'yap -1' so obviously these will
never equate changing the equality on line 346 works (viewer ==? 'yap- 1')
changing Tex_ViewRule_Dvi to 'yap' also works but it means that multiple
instances open everytime '\ls' is used which is no good.

2) The quickfix window doesn't work at all. I've spent a bit of time on
this and I narrowed down the problem. In windows the default qf behaviour
is 'broken'. Therefore typing ':normal! \<escape>'  when in the qf window
doesn't work the cursor just stays where it is.

This is because the 'bufnr' in each item of the quickfix window (see
getqflist()) is set to zero. It doesn't know what buffer the error points
to.
I've hacked around this by replacing the ':normal! \<escape>' call to
'wincmd k' and it works but I'd be interested if anyone has a solution.

David

[Vim-latex-devel] <tab> doesn't toggle folds in preview window

[David A. <ad...@tc...>]

Hi,

According to the
help<http://vim-latex.sourceforge.net/documentation/latex-suite/ls-completion-ref.html>
the
<tab> key should toggle the folds in the preview window. This doesn't seem
to be working in my implementation. I had a quick look through the source
and couldn't find any mappings so I added one to texviewer.vim

exec 'nnoremap <buffer> <cr> '
\ .':cd '.s:origdir.'<CR>'
\ .':call Tex_FinishOutlineCompletion()<CR>'
exec 'nnoremap <buffer> q '
\ .':cd '.s:origdir.'<CR>'
\ .':close<CR>'
\ .':call Tex_SwitchToInsertMode()<CR>'
"Added by me
exec 'nnoremap <buffer> <tab> za <CR>'

Not sure if there is a better way to do this however.

In case anyone is interested. Here is a substitute command I wrote for
automatically adding a key (aka a label) to any BibTex entries in a bib
file that don't have one, as latex-suite will not work without them. Scopus
doesn't including a key when exporting in BibTex for instance. It just
gives @article{first_author:year,

%s/\(\s*@\a*\s*{\)\(,\)\(\_[^@]*author\s*=\s*{\)\(\a*\)\(\_[^@]*year={\)\(\d*\)\(}\)/\1\4:\6,\3\4\5\6\7/

David

[Vim-latex-devel] Ignore Reference warnings at compilation

[Thomas G. <goe...@gm...>]

Hi everybody,

i want some warnings being ignored while compiling my article. I am
referencing to a chapter which isn`t already written, so it isn`t
included right now too. I split all my chapters into separate files
using \includeonly{chap1,chap2}.

The howto tells me to set variables TeX_IgnoreLevel and
TeX_IgnoredWarnings, which i did. But it still does not work. Here is
the part of my vimrc:

" Ignore some warnings and errors
let g:Tex_IgnoredWarning =
             \"Underfull\n".
             \"Overfull\n".
             \"specifier changed to\n".
             \"You have requested\n".
             \"Missing number, treated as zero.\n".
             \"There were undefined references\n"
             \"Citation %.%# undefined"
             \"LaTeX Warning: Reference"
let g:Tex_IgnoreLevel = "8"
let g:Tex_GotoError = "0"

The warning i get is:
kapitel/teststand.tex|9 warning| LaTeX Warning: Reference `chap:imstart'
on page 8 undefined on input line 9.

Thanks for your help,
Tom

-- 
Answer:   Because we read from top to bottom, left to right!
Question: Why should i start my reply below the quoted text?

Re: [Vim-latex-devel] issue with duplicate labels

[Gerd W. <ger...@ma...>]

I would suggest the following:

- Read the manual, in particular:
http://vim-latex.sourceforge.net/documentation/latex-suite.html#customizing-compiling

- Add something like "LaTeX Warning: Label `%.%#' multiply defined.".

Regards
Gerd


On 11/18/2011 06:38 PM, David Karapetyan wrote:
> Yes, this is precisely what I do, but there must be a way to disable the auto-jumping to the .aux file, as it is really annoying.
> 
> --
> Best,
> David Karapetyan
> 
> 
> 
> On Nov 18, 2011, at 9:41 AM, Mike Richman wrote:
> 
>> Hi David,
>>
>> I don't think I ever found a way to disable this behavior, but you can
>> normally jump quickly back to your previous location with CTRL-o
>> (which is also really useful in lots of other circumstances!).  Hope
>> this helps you get your flow back.
>>
>> Cheers,
>> Mike
>>
>> On Wed, Nov 16, 2011 at 1:22 PM, David Karapetyan
>> <dav...@gm...> wrote:
>>>
>>>>
>>>> Hello everyone,
>>>>
>>>> If I have a duplicate label in a tex file, and compile it in the latest git pull of latex-suite, the corresponding .aux file is opened. I would like to disable this behavior. How can I do this.
>>>>
>>>> --
>>>> Best,
>>>> David Karapetyan
>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> All the data continuously generated in your IT infrastructure
>>> contains a definitive record of customers, application performance,
>>> security threats, fraudulent activity, and more. Splunk takes this
>>> data and makes sense of it. IT sense. And common sense.
>>> http://p.sf.net/sfu/splunk-novd2d
>>> _______________________________________________
>>> Vim-latex-devel mailing list
>>> Vim...@li...
>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>>
> 
> 
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure 
> contains a definitive record of customers, application performance, 
> security threats, fraudulent activity, and more. Splunk takes this 
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

Re: [Vim-latex-devel] issue with duplicate labels

[David K. <dav...@gm...>]

Yes, this is precisely what I do, but there must be a way to disable the auto-jumping to the .aux file, as it is really annoying.

--
Best,
David Karapetyan



On Nov 18, 2011, at 9:41 AM, Mike Richman wrote:

> Hi David,
> 
> I don't think I ever found a way to disable this behavior, but you can
> normally jump quickly back to your previous location with CTRL-o
> (which is also really useful in lots of other circumstances!).  Hope
> this helps you get your flow back.
> 
> Cheers,
> Mike
> 
> On Wed, Nov 16, 2011 at 1:22 PM, David Karapetyan
> <dav...@gm...> wrote:
>> 
>>> 
>>> Hello everyone,
>>> 
>>> If I have a duplicate label in a tex file, and compile it in the latest git pull of latex-suite, the corresponding .aux file is opened. I would like to disable this behavior. How can I do this.
>>> 
>>> --
>>> Best,
>>> David Karapetyan
>>> 
>>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure
>> contains a definitive record of customers, application performance,
>> security threats, fraudulent activity, and more. Splunk takes this
>> data and makes sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-novd2d
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>> 

Re: [Vim-latex-devel] issue with duplicate labels

[Mike R. <ri...@um...>]

Hi David,

I don't think I ever found a way to disable this behavior, but you can
normally jump quickly back to your previous location with CTRL-o
(which is also really useful in lots of other circumstances!).  Hope
this helps you get your flow back.

Cheers,
Mike

On Wed, Nov 16, 2011 at 1:22 PM, David Karapetyan
<dav...@gm...> wrote:
>
>>
>> Hello everyone,
>>
>> If I have a duplicate label in a tex file, and compile it in the latest git pull of latex-suite, the corresponding .aux file is opened. I would like to disable this behavior. How can I do this.
>>
>> --
>> Best,
>> David Karapetyan
>>
>>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] [ vim-latex-Patches-3189887 ] More customizations of envmacros

[Gerd W. <ger...@ma...>]

After mailing the patch two times to the mailing list, which fails,
since nobody administrates the list, I upload the patch to my website.
You can found it on

www.tu-chemnitz.de/~gerw/envmacros_customizations.patch

Regards
Gerd


On Sat, 15 Oct 2011, SourceForge.net wrote:

> ----------------------------------------------------------------------
>
> Comment By: Gerd Wachsmuth (gerw)
> Date: 2011-10-15 12:40
>
> Message:
> I can't upload the patch here. (Why?)
>
> I send it on the mailinglist.
>
> ----------------------------------------------------------------------
>
> Comment By: Gerd Wachsmuth (gerw)
> Date: 2011-10-15 12:38
>
> Message:
> Uploaded new version of the patch, including changes in the documentation.
>
> ----------------------------------------------------------------------

[Vim-latex-devel] issue with duplicate labels

[David K. <dav...@gm...>]

> 
> Hello everyone,
> 
> If I have a duplicate label in a tex file, and compile it in the latest git pull of latex-suite, the corresponding .aux file is opened. I would like to disable this behavior. How can I do this.
> 
> --
> Best,
> David Karapetyan
> 
> 

Re: [Vim-latex-devel] Issue with includegraphics tex-completion and Tex_ImageDir

[Francesco M. <fra...@gm...>]

Kay Smarczewski <kay.smarczewski <at> mailbox.tu-dresden.de> writes:

> 
> Hey,
> 
> I use the latest svn trunk version.
> If I leave the
> > TexLet g:Tex_ImageDir = ''
> in texrc the <F9>-completion of \includegraphics{ aborts without any
> message. Setting it to
> > Tex_ImageDir = '.'
> brings the completion back to life. So this could be a better default
> value.
> 
> But the inserted path way too long, e.g. ..//home/.../tex/file
> Changing the param value for the root dir for Tex_SetupFileCompletion 
> to '' solves this problem for me. I have attached a tiny patch... maybe
> someone can use it sometime.
> 
> Kind regards,
> 
> Kay
> 
> Attachment (texviewer_path.patch): text/x-diff, 403 bytes
> 
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and 
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today. 
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim-latex-devel <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 


I just solved adding g:

here's my patch

--- texviewer.vim	2011-11-10 12:55:48.750162773 +0100
+++ texviewer_new.vim	2011-11-10 12:56:07.656484462 +0100
@@ -148,8 +148,8 @@
 				\ '', 
 				\ '^\.\\|\.tex$\\|\.bib$\\|\.bbl$\\|\.zip$\\|\.gz$', 
 				\ 'noext', 
-				\ Tex_GetVarValue('Tex_ImageDir', '.'), 
-				\ Tex_GetVarValue('Tex_ImageDir', ''))
+				\ Tex_GetVarValue('g:Tex_ImageDir', '.'), 
+				\ Tex_GetVarValue('g:Tex_ImageDir', ''))
 			
 		elseif exists("s:type") && s:type == 'bibliography'
 			call Tex_SetupFileCompletion(

Re: [Vim-latex-devel] vim-latex parsing .log files incorrectly?

[Ted P. <te...@te...>]

William --

Please review this summary of Vim's issues with dealing with LaTeX error
messages and some fixes and workarounds:

http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html

Does that answer your question?

Best --
Ted

On 11/05/2011 02:27 AM, William Pettersson wrote:
> I've attached a short debug.tex file which gives me odd results. When
> compiling, I get overfull hboxes.  This I expect, some of the formula
> are way to long to fit easily, and the resulting output does look
> horrible. That's because half-made this example to cause an issue.
> 
> My issue is that I've got vim-latex set to defaults, so it should be
> ignoring any underfull hbox warnings, however it seems to think that
> there is some sort of issue. The second window (error parsing) in vim
> opens up, displaying the following:
> 
> debug.tex                                                              
>  1 || (./debug.aux)
>  2 debug.tex|| \OML/cmm/m/it/12 m[]; m[]; [] ; m[]; m[]; m[]; [] ; m[];
> \OT1/cmr/m/n/12 (\OM 
>  3 || 
> 
> It seems to me like vim-latex is having some sort of issue with the
> parsing of the log file. I'm really not sure why, I can't quite
> interpret the output to work out exactly why it's throwing this error out.
> 
> What I can do, however, is "fix" my issue. If I change the
> "max_print_line" value in texmf.cnf  to almost any other value (I've
> tested 70,75,80,82) then the debug.log file changes sufficiently such
> that I no longer get the warning printed. So it seems to be something to
> do with parsing lines from the log files. 
> 
> As a side-note, to test this simply running 
> $ max_print_line=79 vim debug.tex
> 
> and then compiling (\ll) is enough to show my issues, while changing the
> 79 seems to resolve it.
> 
> Anyway, I'm "happy" in that I don't really care how long the log file
> lines are, but I wanted to point this out as it may be an issue in the
> log file parsing.
> 
> Thanks,
> Will
> 
> 
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> 
> 
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Folding for latex-beamer

[Germain V. <ger...@un...>]

Hello,

I am a beamer user and I use the following syntax for frames.

\begin{frame}
     \frametitle{Just the title}

     frame contents
\end{frame}

Thus, folding looks like that :
+--- 30 lignes : frame ():    \frametitle{Just the title}

Nevertheless,  I agree with denilson frame environment could be added to 
defaults Tex_FoldedEnvironments variable.


Germain


Le 27/10/2011 18:38, Ted Pavlic a écrit :
> Of course, another option is to include a comment after each
> \begin{frame} that is descriptive:
>
> \begin{frame}{Frame name}
> % Frame name
> \end{frame}
>
> However, at that point you might as well just start using your own
> folding markers (which is another option) instead of Vim-LaTeX's
> tex-based folding.
>
> Again, try the hack I suggest below. See if it works well for you. You
> don't lose a lot when you short circuit \begin and \end and call the
> macros themselves.
>
> --Ted
>
> On 10/27/2011 12:35 PM, Ted Pavlic wrote:
>> Here's a hack that might work for you.
>>
>> Add "frame" to FoldedSections as opposed to FoldedEnvironments. Then,
>> instead of using \begin and \end, use:
>>
>> \frame{Frame name}
>> \endframe
>>
>> and
>>
>> \frame[fragile]{Another frame}
>> \endframe
>>
>> I think you'll get a result closer to what you want.
>>
>> Best --
>> Ted
>>
>> On 10/26/2011 11:01 PM, Denilson Figueiredo de Sá wrote:
>>> It would be nice to add folding for Beamer right out of the box.
>>> Not just that, but the folding should show the frame name.
>>>
>>> I've already added ",frame" to g:Tex_FoldedEnvironments, but the result is
>>> not good. The folding does not show the frame name, which results in a
>>> bunch of foldings that look all alike.
>>>
>>> Beamer frames look like this:
>>>
>>> \begin{frame}{Frame name}
>>> This is a slide in Beamer.
>>> \end{frame}
>>>
>>> \begin{frame}[fragile]{Another frame}
>>> It is great for making presentations.
>>> \end{frame}
>>>
>>> There seems to be other alternate syntaxes (but the above one is enough
>>> for me). Look here for more examples:
>>> http://en.wikibooks.org/wiki/LaTeX/Presentations
>>>
>>>
>>> (BTW, if someone replies to the list, please also add me to CC)
>>>
>>>

-- 
Maître de Conférence
Université de Pau et des pays de l'Adour
Institut Pluridisciplinaire de Recherche sur l'Environnement et les
Matériaux
Équipe de Chimie Physique
email  : ger...@un...
Tel    : 05 59 40 78 51
page   : http://gvallver.perso.univ-pau.fr

[Vim-latex-devel] Folding bug?

[Giovanni L. C. <jun...@gm...>]

Hi all,
I found that folding does not work correctly when you have an equation 
environment in a single line. E.g.:

**************

\section{Ciao, World!}

This is the first section

\begin{equation} e = m\cdot c^{2} \label{eq:energymass} \end{equation}

\section{Hi again, World!}

This is another section

**************

Vim-latex folds everything after the equation in one fold, and does not 
create a fold for the second section. As soon as the \end{equation} is 
moved to a new line, folding works again. Can anybody reproduce this 
problem? I am on Ubuntu 11.10, Vim-latex 20110214.1049-1, Vim 7.3.154.

Best,

-- 
Giovanni Luca Ciampaglia

Ph.D. Candidate
Faculty of Informatics
University of Lugano
Web: http://www.inf.usi.ch/phd/ciampaglia/

Bertastraße 36 ∙ 8003 Zürich ∙ Switzerland

Mobile: +41 79 718 8157

Re: [Vim-latex-devel] Folding for latex-beamer

[Gerd W. <ger...@ma...>]

It's also possible to use

\begin{frame}
  \frametitle{Frame name}
\end{frame}

with LaTeX Beamer.

Regards
Gerd



On 10/27/2011 06:38 PM, Ted Pavlic wrote:
> Of course, another option is to include a comment after each
> \begin{frame} that is descriptive:
> 
> \begin{frame}{Frame name}
> % Frame name
> \end{frame}
> 
> However, at that point you might as well just start using your own
> folding markers (which is another option) instead of Vim-LaTeX's
> tex-based folding.
> 
> Again, try the hack I suggest below. See if it works well for you. You
> don't lose a lot when you short circuit \begin and \end and call the
> macros themselves.
> 
> --Ted
> 
> On 10/27/2011 12:35 PM, Ted Pavlic wrote:
>> Here's a hack that might work for you.
>>
>> Add "frame" to FoldedSections as opposed to FoldedEnvironments. Then,
>> instead of using \begin and \end, use:
>>
>> \frame{Frame name}
>> \endframe
>>
>> and
>>
>> \frame[fragile]{Another frame}
>> \endframe
>>
>> I think you'll get a result closer to what you want.
>>
>> Best --
>> Ted
>>
>> On 10/26/2011 11:01 PM, Denilson Figueiredo de Sá wrote:
>>> It would be nice to add folding for Beamer right out of the box.
>>> Not just that, but the folding should show the frame name.
>>>
>>> I've already added ",frame" to g:Tex_FoldedEnvironments, but the result is  
>>> not good. The folding does not show the frame name, which results in a  
>>> bunch of foldings that look all alike.
>>>
>>> Beamer frames look like this:
>>>
>>> \begin{frame}{Frame name}
>>> This is a slide in Beamer.
>>> \end{frame}
>>>
>>> \begin{frame}[fragile]{Another frame}
>>> It is great for making presentations.
>>> \end{frame}
>>>
>>> There seems to be other alternate syntaxes (but the above one is enough  
>>> for me). Look here for more examples:
>>> http://en.wikibooks.org/wiki/LaTeX/Presentations
>>>
>>>
>>> (BTW, if someone replies to the list, please also add me to CC)
>>>
>>>
>>
> 

Re: [Vim-latex-devel] Folding for latex-beamer

[Ted P. <te...@te...>]

Of course, another option is to include a comment after each
\begin{frame} that is descriptive:

\begin{frame}{Frame name}
% Frame name
\end{frame}

However, at that point you might as well just start using your own
folding markers (which is another option) instead of Vim-LaTeX's
tex-based folding.

Again, try the hack I suggest below. See if it works well for you. You
don't lose a lot when you short circuit \begin and \end and call the
macros themselves.

--Ted

On 10/27/2011 12:35 PM, Ted Pavlic wrote:
> Here's a hack that might work for you.
> 
> Add "frame" to FoldedSections as opposed to FoldedEnvironments. Then,
> instead of using \begin and \end, use:
> 
> \frame{Frame name}
> \endframe
> 
> and
> 
> \frame[fragile]{Another frame}
> \endframe
> 
> I think you'll get a result closer to what you want.
> 
> Best --
> Ted
> 
> On 10/26/2011 11:01 PM, Denilson Figueiredo de Sá wrote:
>> It would be nice to add folding for Beamer right out of the box.
>> Not just that, but the folding should show the frame name.
>>
>> I've already added ",frame" to g:Tex_FoldedEnvironments, but the result is  
>> not good. The folding does not show the frame name, which results in a  
>> bunch of foldings that look all alike.
>>
>> Beamer frames look like this:
>>
>> \begin{frame}{Frame name}
>> This is a slide in Beamer.
>> \end{frame}
>>
>> \begin{frame}[fragile]{Another frame}
>> It is great for making presentations.
>> \end{frame}
>>
>> There seems to be other alternate syntaxes (but the above one is enough  
>> for me). Look here for more examples:
>> http://en.wikibooks.org/wiki/LaTeX/Presentations
>>
>>
>> (BTW, if someone replies to the list, please also add me to CC)
>>
>>
> 

-- 
Ted Pavlic <te...@te...>

[Vim-latex-devel] Folding for latex-beamer

[Denilson F. de Sá <den...@gm...>]

It would be nice to add folding for Beamer right out of the box.
Not just that, but the folding should show the frame name.

I've already added ",frame" to g:Tex_FoldedEnvironments, but the result is  
not good. The folding does not show the frame name, which results in a  
bunch of foldings that look all alike.

Beamer frames look like this:

\begin{frame}{Frame name}
This is a slide in Beamer.
\end{frame}

\begin{frame}[fragile]{Another frame}
It is great for making presentations.
\end{frame}

There seems to be other alternate syntaxes (but the above one is enough  
for me). Look here for more examples:
http://en.wikibooks.org/wiki/LaTeX/Presentations


(BTW, if someone replies to the list, please also add me to CC)


-- 
Denilson Figueiredo de Sá
Rio de Janeiro - Brasil

[Vim-latex-devel] \ll doesn't trigger the compilation

[Qiuye W. <qi...@gm...>]

Hey list,

I've noticed that the \ll shortcut doesn't trigger the compilation, but I can
launch it by mouseclick in the latexsuite menu of gvim. In the normal mode when
I press \ll, the cursor just moves left twice, which is the right behavior
without the mapleader.

by
:map
I got
n  \rf          @<Plug>Tex_RefreshFolds
n  \ls          @<Plug>Tex_ForwardSearch
n  \lv          @<Plug>Tex_View
v  \ll          @<Plug>Tex_Compile
n  \ll          @<Plug>Tex_Compile
...

and BTW, the rest shortcuts of this list don't work either, which also can be
launched through the menu.

I've also changed the mapleader by
g:mapleader="<space>" or "<F11>"
Well, can see this change in the menu, but still nothing happens when
<mapleader>ll is pressed.

Now I have no clue, don't know how to fix it.
Any idea? 

Regards,
QY
-- 
Linux version 3.0.0-2-686-pae
Debian GNU/Linux wheezy/sid