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

[Vim-latex-devel] vim latex on windows 7 64 bit

[Yue-Jun Y. <yj...@gm...>]

Hi all,
I installed vim-latex on a windows 7 (64) laptop. When use \ll to 
compile a tex file, I got these error.
Error detected while processing function 
Tex_RunLatex..Tex_CompileMultipleTimes..Tex_CatFiles:
line 2:
Traceback (most recent call):
File "<string>", line 1, in ?
NameError: name 'catFile' is not defined
line 4
E121: Undefined variable retval
E15: detected while processing function 
Tex_RunLatex..Tex_CompileMultiTimes..Tex_IsPresentInFile:
line 1:
Traceback (most recent call last):
File "<string>", line 1, in ?
... ...

The second problem is F9 doesn't work. The outline splitting window 
shows up but without any content.

MikTex is installed in the laptop. The tex file can be compiled in 
command line without any problem. I am confident that the
problem lie in vim-latex package. It is fresh installation. The file 
_vimrc has been added to /vim/. The following lines are added to tex.vim 
(/vim/vim72/ftplugin/tex.vim)
set sw=2
set iskeyword+=:


I have used vim latex in windows 7 32 bit, fedora, and snow leopard. 
Have never got such problems.

-- 
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/

Re: [Vim-latex-devel] need help for customizing compiling settings

[LAG G. <l.g...@sc...>]

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... <mailto: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...>
>     <mailto: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&#174; 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...>
>     <mailto: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...>
>     <mailto: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 

Re: [Vim-latex-devel] need help for customizing compiling settings

[Jin C. <che...@gm...>]

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&#174; 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
> >
> >
>

Re: [Vim-latex-devel] need help for customizing compiling settings

[Dennis G. <l.g...@sc...>]

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&#174; 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 
>
>

[Vim-latex-devel] need help for customizing compiling settings

[Jin C. <che...@gm...>]

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

Re: [Vim-latex-devel] Issue with Taglist and suggested patch

[Dan M. O. H. <dm...@st...>]

Hi,

I didn't get any response to the mail below. I would love to hear whether other people are experiencing the same problem with double section headings in Taglist when Vim-Latex is used -- and if my patch is helpful.

-- Dan Michael


Den 16. feb. 2010 kl. 16.16 skrev Dan Michael Olsen Heggø:

> Hi,
> 
> I had issues with some section headings showing up twice in Taglist. I
> use exuberant ctags 5.8, which have some limited native tex support
> (see output from --list-kinds=tex below). Therefore, the tex language
> is already defined, and when Vim-Latex tries to define it again on
> line 899 in main.vim, it results in "ctags: Warning: Language "tex"
> already defined". 
> 
> Regexps for e.g sections are thus defined twice (both natively by
> ctags and by Vim-Latex). As far as I can see, the regexps of Vim-Latex
> appear to be more robust than the native implementation, so I simply 
> modified main.vim to use an unused character ("d") instead of "s" for the 
> all the section-related regexps and modified tlist_tex_settings to just
> ignore the native implementation. My patch against trunk can be found here:
> 
> http://heggoe.net/various/taglist.patch
> 
> I kept "--langdef=tex" in the patch for users of ctags versions without native
> tex-support. While this will trigger an error (in the background), it seems
> like it doesn't do any harm. My patch is just a quick fix, but it seems to work
> fine. Any comments or suggestions are welcome.
> 
> -- Dan Michael
> 
> 
> ctags --list-kinds=tex
> c  chapters
> s  sections
> u  subsections
> b  subsubsections
> p  parts
> P  paragraphs
> G  subparagraphs

Re: [Vim-latex-devel] Eliminating error message for \ll and REVTeX 4-1

[Aditya M. <ad...@um...>]

On Sat, 13 Mar 2010, Nicholas Laszlo Frazer wrote:

> I did not get any responses.  Is there somewhere else I should ask?  Is
> there more information I should provide?

Your minimal example works fine here. \ll compiles the document without 
any errors. But I am using texlive 2009 on arch linux (and not debian).

Aditya

Re: [Vim-latex-devel] Eliminating error message for \ll and REVTeX 4-1

[Nicholas L. F. <per...@ce...>]

Hi,
I did not get any responses.  Is there somewhere else I should ask?  Is  
there more information I should provide?
Thanks!

On Tue, 23 Feb 2010 21:59:21 -0600, Nicholas Laszlo Frazer  
<per...@ce...> wrote:

> Hi, I'm new to this list.
>
> Debian Testing has moved to REVTeX 4-1, removing REVTeX 4.  Needless to
> say, this is causing problems for many scientists who have documents
> written for REVTeX 4.
> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561836)
>
> My issue regards the use of \ll with REVTeX 4-1.  My workaround has been
> to use :!pdflatex %, which does not cause the problem but is less
> convenient than \ll.  \ll seems to create a compiled document just fine.
> However, afterwards vim displays
>
>
> Ran latex 1 time(s)
> Error detected while processing function
> Tex_RunLaTeX..Tex_SetupErrorWindow..Tex_GetMainFileName:
> line   18:
> E344: Cannot find directory "Document Class: revtex4-1 2009/10" in cdpath
> E472: Command failed
> line   31:
> E344: Cannot find directory "Document Class: revtex4-1 2009" in cdpath
> E472: Command failed
> Press ENTER or type command to continue
>
>
> I press enter.  Vim displays the same thing in a buffer at the bottom of
> the screen and an empty buffer at the top of the screen.  How can I make
> the error message go away and have vim return me back to the document I
> was working on after \ll?  Here is an example of a document that causes
> the problem:
>
>
> \documentclass{revtex4-1}
> \begin{document}
> Text
> \end{document}
>
> The problem does not occur with the letter documentclass.
>
> I have vim 7.2.  dpkg says my latexsuite 20100129-1.  Here is my vimrc
>
>
> " Configuration file for vim
> set
> runtimepath=~/.vim,/usr/share/vim/addons,/usr/share/vim/vimfiles,/usr/share/vim/vimcurrent,/usr/share/vim/vimfiles/after,/usr/share/vim/addons/after,~/.vim/after
>
> " Normally we use vim-extensions. If you want true vi-compatibility
> " remove change the following statements
> set nocompatible	" Use Vim defaults instead of 100% vi compatibility
> set backspace=indent,eol,start	" more powerful backspacing
>
> " Now we set some defaults for the editor
> set autoindent		" always set autoindenting on
> " set linebreak		" Don't wrap words by default
> set textwidth=0		" Don't wrap lines by default
> set viminfo='20,\"50	" read/write a .viminfo file, don't store more than
> 			" 50 lines of registers
> set history=50		" keep 50 lines of command line history
> set ruler		" show the cursor position all the time
>
> " Suffixes that get lower priority when doing tab completion for  
> filenames.
> " These are files we are not likely to want to edit or read.
> set
> suffixes=.bak,~,.swp,.o,.info,.aux,.log,.dvi,.bbl,.blg,.brf,.cb,.ind,.idx,.ilg,.inx,.out,.toc,.pdf
>
> " We know xterm-debian is a color terminal
> if &term =~ "xterm-debian" || &term =~ "xterm-xfree86"
>    set t_Co=16
>    set t_Sf=%1B[3%dm
>    set t_Sb=%1B[4%dm
> endif
>
> " Vim5 and later versions support syntax highlighting. Uncommenting the
> next
> " line enables syntax highlighting by default.
> syntax on
>
> " If using a dark background within the editing area and syntax
> highlighting
> " turn on this option as well
> " set background=dark
>
> if has("autocmd")
>   " Enabled file type detection
>   " Use the default filetype settings. If you also want to load indent  
> files
>   " to automatically do language-dependent indenting add 'indent' as  
> well.
>   filetype plugin on
>
> endif " has ("autocmd")
>
> " Some Debian-specific things
> if has("autocmd")
>    augroup filetype
>      au BufRead reportbug.*		set ft=mail
>      au BufRead reportbug-*		set ft=mail
>    augroup END
> endif
>
> " Uncomment the following to have Vim jump to the last position when
> " reopening a file
> " if has("autocmd")
> "   au BufReadPost * if line("'\"") > 0 && line("'\"") <= line("$")
> "                    \| exe normal g'\"" | endif
> " endif
>
> " Set paper size from /etc/papersize if available (Debian-specific)
> if filereadable("/etc/papersize")
>    try
>      let s:shellbak = &shell
>      let &shell="/bin/sh"
>      let s:papersize = matchstr(system("cat /etc/papersize"), "\\p*")
>      let &shell=s:shellbak
>      if strlen(s:papersize)
>        let &printoptions = "paper:" . s:papersize
>      endif
>    catch /^Vim\%((\a\+)\)\=:E145/
>    endtry
> endif
>
> " The following are commented out as they cause vim to behave a lot
> " different from regular vi. They are highly recommended though.
> "set showcmd		" Show (partial) command in status line.
> "set showmatch		" Show matching brackets.
> "set ignorecase		" Do case insensitive matching
> "set incsearch		" Incremental search
> "set autowrite		" Automatically save before commands like :next and :make
>
> " Source a global configuration file if available
> if filereadable("/etc/vim/vimrc.local")
>    source /etc/vim/vimrc.local
> endif
>
> "folding
> set foldmethod=syntax
>
>
> " OPTIONAL: Starting with Vim 7, the filetype of empty .tex files  
> defaults
> to
> " " 'plaintex' instead of 'tex', which results in vim-latex not being
> loaded.
> " " The following changes the default filetype back to 'tex':
>   let g:tex_flavor='latex'
>
>
>
>


-- 
Nicholas Laszlo Frazer
per...@ce...
nlf@u.northwestern.edu
nl...@uc...
nfr...@si...

1516 Hinman Ave #510
Evanston, IL 60201
(773)634-9638

[Vim-latex-devel] patch for ref completion

[Andreas W. <awi...@ze...>]

This is a patch for the 'Error List/cwindow' ref completion mode.
When a label was found in an \include'd file, the completion was made there (in the included file) and not in the buffer, that was edited when <F9> was pressed. This can be fixed by adding the 'j' flag to the search pattern of vimgrep and vimgrepadd.

A.

[Vim-latex-devel] Bug: vanishing backslash

[Tim v. E. <Tim...@cw...>]

Dear list,

Recently I've been running into the strange problem that sometimes all 
of the standard vim-latex keybindings lose their backslash. This is (the 
first part of) the output of typing ":map" in Vim when this happens:

n  ls           @<Plug>Tex_ForwardSearch
n  lv           @<Plug>Tex_View
v  ll           @<Plug>Tex_Compile
n  ll           @<Plug>Tex_Compile
n  rf           @<Plug>Tex_RefreshFolds

normally it looks like this:

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

I can now consistently reproduce the problem on the attached files by 
taking the following steps:

- start Vim in "test" dir.
- \ll
- :e subdir/test2
- :map

The problem goes away if I change the use of "\include" in test.tex to 
"\input". Strangely enough, "\include" generates a test2.aux file in 
subdir, while "\input" does not. I don't know if that's relevant.

I'm using Vim-latex 1.8.23-20100129-r1104 with Vim 7.2 on Fedora 12.

Btw, I've also noticed that compiling (\ll) while in a subdirectory 
changes the Vim path to the directory of the main latex file. That also 
seems a bug to me, and might be related.

Best regards,
   Tim

-- 
Tim van Erven <Tim...@cw...>

[Vim-latex-devel] trigger ref completion mode

[Andreas W. <awi...@ze...>]

Hi list,

there are two \ref completion modes mentioned in the documentation of vim-latex found on http://vim-latex.sourceforge.net/:
The first one is the ErrorList/cwindow mode, the second one the __OUTLINE__ mode.
It is not clear to me, how I can trigger which mode is used when I press <F9> or what setting determines which completion mode is to be used.
In my case I always get the __OUTLINE__ window, where everything is folded up and I have to cycle manually through all the folds to find the right label, which is very inconvenient. Also the documentation says that the <Tab> key is mapped to allow one to navigate the hierarchy faster. This is neither working for me.
Does anybody know what is going wrong here or how I can force vim-latex to use the ErrorList/cwindow completion mode?

I use vim-latex together with MacVim 7.2 on a MB Pro runnning OS X.6.2.

Regards, Andreas

[Vim-latex-devel] Eliminating error message for \ll and REVTeX 4-1

[Nicholas L. F. <per...@ce...>]

Hi, I'm new to this list.

Debian Testing has moved to REVTeX 4-1, removing REVTeX 4.  Needless to  
say, this is causing problems for many scientists who have documents  
written for REVTeX 4.   
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561836)

My issue regards the use of \ll with REVTeX 4-1.  My workaround has been  
to use :!pdflatex %, which does not cause the problem but is less  
convenient than \ll.  \ll seems to create a compiled document just fine.   
However, afterwards vim displays


Ran latex 1 time(s)
Error detected while processing function  
Tex_RunLaTeX..Tex_SetupErrorWindow..Tex_GetMainFileName:
line   18:
E344: Cannot find directory "Document Class: revtex4-1 2009/10" in cdpath
E472: Command failed
line   31:
E344: Cannot find directory "Document Class: revtex4-1 2009" in cdpath
E472: Command failed
Press ENTER or type command to continue


I press enter.  Vim displays the same thing in a buffer at the bottom of  
the screen and an empty buffer at the top of the screen.  How can I make  
the error message go away and have vim return me back to the document I  
was working on after \ll?  Here is an example of a document that causes  
the problem:


\documentclass{revtex4-1}
\begin{document}
Text
\end{document}

The problem does not occur with the letter documentclass.

I have vim 7.2.  dpkg says my latexsuite 20100129-1.  Here is my vimrc


" Configuration file for vim
set  
runtimepath=~/.vim,/usr/share/vim/addons,/usr/share/vim/vimfiles,/usr/share/vim/vimcurrent,/usr/share/vim/vimfiles/after,/usr/share/vim/addons/after,~/.vim/after

" Normally we use vim-extensions. If you want true vi-compatibility
" remove change the following statements
set nocompatible	" Use Vim defaults instead of 100% vi compatibility
set backspace=indent,eol,start	" more powerful backspacing

" Now we set some defaults for the editor
set autoindent		" always set autoindenting on
" set linebreak		" Don't wrap words by default
set textwidth=0		" Don't wrap lines by default
set viminfo='20,\"50	" read/write a .viminfo file, don't store more than
			" 50 lines of registers
set history=50		" keep 50 lines of command line history
set ruler		" show the cursor position all the time

" Suffixes that get lower priority when doing tab completion for filenames.
" These are files we are not likely to want to edit or read.
set  
suffixes=.bak,~,.swp,.o,.info,.aux,.log,.dvi,.bbl,.blg,.brf,.cb,.ind,.idx,.ilg,.inx,.out,.toc,.pdf

" We know xterm-debian is a color terminal
if &term =~ "xterm-debian" || &term =~ "xterm-xfree86"
   set t_Co=16
   set t_Sf=[3%dm
   set t_Sb=[4%dm
endif

" Vim5 and later versions support syntax highlighting. Uncommenting the  
next
" line enables syntax highlighting by default.
syntax on

" If using a dark background within the editing area and syntax  
highlighting
" turn on this option as well
" set background=dark

if has("autocmd")
  " Enabled file type detection
  " Use the default filetype settings. If you also want to load indent files
  " to automatically do language-dependent indenting add 'indent' as well.
  filetype plugin on

endif " has ("autocmd")

" Some Debian-specific things
if has("autocmd")
   augroup filetype
     au BufRead reportbug.*		set ft=mail
     au BufRead reportbug-*		set ft=mail
   augroup END
endif

" Uncomment the following to have Vim jump to the last position when
" reopening a file
" if has("autocmd")
"   au BufReadPost * if line("'\"") > 0 && line("'\"") <= line("$")
"                    \| exe normal g'\"" | endif
" endif

" Set paper size from /etc/papersize if available (Debian-specific)
if filereadable("/etc/papersize")
   try
     let s:shellbak = &shell
     let &shell="/bin/sh"
     let s:papersize = matchstr(system("cat /etc/papersize"), "\\p*")
     let &shell=s:shellbak
     if strlen(s:papersize)
       let &printoptions = "paper:" . s:papersize
     endif
   catch /^Vim\%((\a\+)\)\=:E145/
   endtry
endif

" The following are commented out as they cause vim to behave a lot
" different from regular vi. They are highly recommended though.
"set showcmd		" Show (partial) command in status line.
"set showmatch		" Show matching brackets.
"set ignorecase		" Do case insensitive matching
"set incsearch		" Incremental search
"set autowrite		" Automatically save before commands like :next and :make

" Source a global configuration file if available
if filereadable("/etc/vim/vimrc.local")
   source /etc/vim/vimrc.local
endif

"folding
set foldmethod=syntax


" OPTIONAL: Starting with Vim 7, the filetype of empty .tex files defaults  
to
" " 'plaintex' instead of 'tex', which results in vim-latex not being  
loaded.
" " The following changes the default filetype back to 'tex':
  let g:tex_flavor='latex'




-- 
Nicholas Laszlo Frazer
per...@ce...
nlf@u.northwestern.edu
nl...@uc...
nfr...@si...

1516 Hinman Ave #510
Evanston, IL 60201
(773)634-9638

Re: [Vim-latex-devel] beginner question - textidy [Feature Request?]

[Javier R. <jer...@de...>]

On Mon, Feb 22, 2010 at 10:11:33PM +0100, par...@tl... wrote:
> I'm a bit spoiled by vim-perl plugin which is has a very useful capability of \ry (run perltidy on a source file written in perl).
> (perltidy makes source code beautiful, by i.e. taking care of proper indentation)
> 
> So the big question is:
> Is there a equivalent tool to be run on tex/latex source code?

you can try selecting the tex code, and then pressing g= in normal mode.

-- 
Javier Rojas

GPG Key ID: 0x24E00D68

[Vim-latex-devel] beginner question - textidy [Feature Request?]

[<par...@tl...>]

Hello!
I'm very new to latex world, so first thing I would like to do is to than you all for vim/latex marriage.
Great job!

I would like to ask if there exists some kind of tool to tidy tex/latex source code?
Is someone aware of it?

I'm a bit spoiled by vim-perl plugin which is has a very useful capability of \ry (run perltidy on a source file written in perl).
(perltidy makes source code beautiful, by i.e. taking care of proper indentation)

So the big question is:
Is there a equivalent tool to be run on tex/latex source code?



Sorry if this is lame question.

Anyway thanks for any reply. 

Luke

[Vim-latex-devel] ref completion with \input statements

[LAG G. <l.g...@sc...>]

Dear all,

I am using gvim 7.2 and latex-suite  that I installed via yast in
opensuse and should be up-to-date. I have the same problem as reported here

Hugo Gagnon
Thu, 11 Jun 2009 02:07:41 -0700
http://www.mail-archive.com/vim...@li.../msg00551.html

So it appears that the ref completion does not work with input statements.

My error messages are (look especially at the last line for the *.tex.tex !)

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/share/vim/site/ftplugin/latex-suite/outline.py", line 170,
in main
    contents = getFileContents(root, ext)
  File "/usr/share/vim/site/ftplugin/latex-suite/outline.py", line 27,
in getFileContents
    contents = re.sub(pat, lambda input: getFileContents(input, ext),
contents)
  File "/usr/lib/python2.6/re.py", line 150, in sub
    return _compile(pattern, 0).sub(repl, string, count)
  File "/usr/share/vim/site/ftplugin/latex-suite/outline.py", line 27,
in <lambda>
    contents = re.sub(pat, lambda input: getFileContents(input, ext),
contents)
  File "/usr/share/vim/site/ftplugin/latex-suite/outline.py", line 23,
in getFileContents
    contents = '\n'.join(open(fname).read().splitlines())
IOError: [Errno 2] No such file or directory: 'beginDocument.tex.tex'

is there anyone who has already solved this problem? Or is able to at
least help me?

cheers,

Dennis

[Vim-latex-devel] answer to: cite completion fails after more than three inputarguments for \bibliography

[LAG G. <l.g...@sc...>]

Dear all,

It seems that the answer to my previous question is relatively simple.
Bibtex does allow the use of parentheses in @article() while in order
for the cite completion to work it should be @article{} with the curly
brackets! It took me some time to figure it out since it was a quite
subtle thing in a huge database.

cheers,

Dennis

[Vim-latex-devel] cite completion fails after more than three inputarguments for \bibliography

[LAG G. <l.g...@sc...>]

Hello (every/any)body,

I am using vim-latex to write a large manual and after configuring it to
the best of my ability I am very satisfied with the result!
Unfortunately, I have a lot of bibtex entries and I need to distribute
them over a few bib-files in order to have a bit of an overview. It now
turns out that my cite completion only works for the first three
bibfilenames in my  \bibliography{} and after that it seems that the
completion is not able to find any entries in the other files. This is
weird, since compilation of my document gives me the desired result of
all references to the bibliography being correct.

Is there any real hard limit to the amount of bibtexentries or the
amount of bibtex files?

cheers,

Dennis

Re: [Vim-latex-devel] Package support files

[Till M. <ope...@ti...>]

On Wed, Feb 17, 2010 at 02:58:53PM +0100, Andreas Wagner wrote:

> Sure. Find them attached again. Thanks a lot for maintaining this package!

I added them in changeset 1106.

Regards
Till

Re: [Vim-latex-devel] Package support files

[Andreas W. <And...@em...>]

Hello List,

* Till Maas dixit [170210 12:33]:
>> I have put together four package support files and would like to ask you to have a look at them and if 
>> they are okay by you, to add them to the list of distributed package support files.
>
> Thank you. I only have two formal requests. Do you mind adding a line to the source stating that you are 
> the author and another that says that the file can be distributed using the vim license?

Sure. Find them attached again. Thanks a lot for maintaining this package!

Cheers,
Andreas



-- 
Dr. des. Andreas Wagner
Goethe-Universität Frankfurt
http://tinyurl.com/awagner
Tel. +49 (0)69/798-22765

Exzellenz-Cluster "The Formation of Normative Orders"
http://www.normativeorders.net/
Senckenberganlage 31, R. 517
60325 Frankfurt am Main

Institut für Philosophie
Grüneburgplatz 1, R. 2.456
60629 Frankfurt am Main

Re: [Vim-latex-devel] inputgraphics completion not working

[Till M. <ope...@ti...>]

On Wed, Feb 03, 2010 at 12:23:40PM +0100, Simon Quittek wrote:

> there were some changes on the completion algorithms recently.
> For me, now \inputgraphics[]{} is not working.
> Completion in \include{} is still OK.
> There is a minimal working example in the attachment.

It does not work for me, too. I hope I find the time to debug it soon,
but there are also some other projects I have to spend some time with.
If you can maybe search for the commit that broke it, it would already
help a lot. The easiest way is probably to create a new user, run "svn
co
https://vim-latex.svn.sourceforge.net/svnroot/vim-latex/trunk/vimfiles
~/.vim" and edit the .vimrc as it is explained in the docs. Then inside
the ~/.vim directory, you can switch revisions with "svn up -r 12345"
where 12345 is the revision you want to test.

Regards
Till

Re: [Vim-latex-devel] Package support files

[Till M. <ope...@ti...>]

On Wed, Feb 17, 2010 at 12:33:36AM +0100, Andreas Wagner wrote:

> I have put together four package support files and would like to ask
> you to have a look at them and if they are okay by you, to add them
> to the list of distributed package support files.

Thank you. I only have two formal requests. Do you mind adding a line to
the source stating that you are the author and another that says that
the file can be distributed using the vim license?

Regards
Till

[Vim-latex-devel] Package support files

[Andreas W. <And...@em...>]

Hi list,

I have put together four package support files and would like to ask you to have a look at them and if they 
are okay by you, to add them to the list of distributed package support files.

They are for the biblatex, csquotes, pagenote and fixme packages.

Cheers,
Andreas


-- 
Dr. des. Andreas Wagner
Goethe-Universität Frankfurt
http://tinyurl.com/awagner
Tel. +49 (0)69/798-22765

Exzellenz-Cluster "The Formation of Normative Orders"
http://www.normativeorders.net/
Senckenberganlage 31, R. 517
60325 Frankfurt am Main

Institut für Philosophie
Grüneburgplatz 1, R. 2.456
60629 Frankfurt am Main

[Vim-latex-devel] Issue with Taglist and suggested patch

[Dan M. O. H. <dm...@st...>]

Hi,

I had issues with some section headings showing up twice in Taglist. I
use exuberant ctags 5.8, which have some limited native tex support
(see output from --list-kinds=tex below). Therefore, the tex language
is already defined, and when Vim-Latex tries to define it again on
line 899 in main.vim, it results in "ctags: Warning: Language "tex"
already defined". 

Regexps for e.g sections are thus defined twice (both natively by
ctags and by Vim-Latex). As far as I can see, the regexps of Vim-Latex
appear to be more robust than the native implementation, so I simply 
modified main.vim to use an unused character ("d") instead of "s" for the 
all the section-related regexps and modified tlist_tex_settings to just
ignore the native implementation. My patch against trunk can be found here:

http://heggoe.net/various/taglist.patch

I kept "--langdef=tex" in the patch for users of ctags versions without native
 tex-support. While this will trigger an error (in the background), it seems
like it doesn't do any harm. My patch is just a quick fix, but it seems to work
fine. Any comments or suggestions are welcome.

-- Dan Michael


ctags --list-kinds=tex
c  chapters
s  sections
u  subsections
b  subsubsections
p  parts
P  paragraphs
G  subparagraphs

[Vim-latex-devel] Problem with envmacros.vim macro expansion

[Gary J. <gar...@sp...>]

I just encountered a problem with the macros defined in
ftplugin/latex-suite/envmacros.  A macro defined there is expanded
even if I type it in the middle of a word.  For example, if I try to
type the word DELETED, the letters ETE trigger a macro and the
result looks like this:

    type the word DEL\begin{table}
        \centering
        \begin{tabular}{<+dimensions+>}
            <++>
        \end{tabular}
        \caption{<+Caption text+>}
        \label{tab:<+label+>}
    \end{table}<++>

I can work around the problem by preceding the last letter of such
macro names with Ctrl-V, or I can disable all those macros by
setting g:Tex_EnvironmentMaps to 0 in my ftplugin/tex.vim file, but
the former is awkward and the latter removes the functionality of
those macros.

It seems to me that those macros would be more useful if they were
not expanded in the middle of words but were expanded only in a more
distinguishing context such as at the beginning of a line or when
preceded or followed by some unusual character.  Is there some way
to configure this that I missed or would this require a change to
the macro package?

Regards,
Gary

[Vim-latex-devel] inputgraphics completion not working

[Simon Q. <sim...@gm...>]

Hi folks,

there were some changes on the completion algorithms recently.
For me, now \inputgraphics[]{} is not working.
Completion in \include{} is still OK.
There is a minimal working example in the attachment.

Regards,
Simon