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

[Vim-latex-devel] [Contact] Latency on Cygwin during both startup and writing/rereading a Tex buffer.

[Vincent N. V. <vim...@so...>]

Hello,



I am running the Cygwin version of vim with vim-latex on Windows XP.  I 
notice that when I load a Latex file into a buffer, with vim-latex active, there is a 
very noticeable delay/latency. The a: drive lights up during this wait. This does not 
happen when I edit non-Latex files.



Is there a way to prevent vim-latex from 
\'scanning\' the a: drive here?



Thanks,



Vince Virgilio  

Re: [Vim-latex-devel] First steps with LS (at last)

[Srinath A. <sr...@fa...>]

On Thu, 17 Jun 2004, Luc Hermitte wrote:

> > I remember that sourcing the compiler plugin was always a bit of a
> > problem... I remember that it was some subtle bug in vim itself (or
> > lack of documentation)... I see the following lines in main.vim:
> > =09runtime compiler/tex.vim
>
> OK I see, Thanks.
>
> Why don't you just execute
>     :compiler tex
> (which in turns calls =AB:runtime! compiler/tex.vim=BB) ?
> This modification fixed the problem -- in my configuration at least.
>

Hmm... This does look like it might be a better way of doing things. The
thing which confuses me is why vim is not doing

    :runtime! compiler/tex.vim

automatically when you open a tex file even though we have "filetype
plugin on". Does vim only do:

    :runtime! ftplugin/tex.vim

when you open a tex file?! (I am surprised I didn't know this already if
its true) Its not mentioned anywhere in the docs that you have to
manually source the compiler ftplugin IIRC.

Latex-suite is not always installed in the same place. The debian distro
instals it in /usr/share/vim/ etc. On windows, most people install it in
~/vimfiles... So its not given if latex-suite's compiler/tex.vim or
vim's will get sourced first...

but...

> If t63 is loaded first, then tls will override the definitions that need
> to be overriden, and LaTeXSuite will ignore the other ones I guess. If
> tls is loaded first, then it can set =ABcurrent_compiler=BB which will ab=
ort
> the sourcing of t63.
>

=2E.. I guess that if I have latex-suite's compiler/tex.vim NOT finish
even if 'current_compiler' exists and set it to 'latex' when it does get
sourced, then it will handle both cases. Have to check this a bit
thoroughly. I don't want to make a release where \ll doesn't work! :)

> the log file (which is not automatically reloaded BTW) , how to
> integrate HT4Tex, ...), and you will see me again. :)
>

Cool :)

Srinath

Re: [Vim-latex-devel] First steps with LS (at last)

[Luc H. <her...@fr...>]

* On Wed, Jun 16, 2004 at 07:52:00PM -0700, Srinath Avadhanula <srinath@f=
astmail.fm> wrote:
> > After investigations, it seems that =AB:compiler tex=BB is not execut=
ed
> > -- when I executed this, I only have one complain about a command
> > redefined and then \ll can be used.
> >
> > It that normal ? Or is there a bug in my installation ? (LS beeing
> > installed into ~/vimfiles/latex-suite which is the last directory of =
my
> > 'runtimepath').
>=20
> I remember that sourcing the compiler plugin was always a bit of a
> problem... I remember that it was some subtle bug in vim itself (or
> lack of documentation)... I see the following lines in main.vim:
> 	runtime compiler/tex.vim

OK I see, Thanks.

Why don't you just execute
    :compiler tex
(which in turns calls =AB:runtime! compiler/tex.vim=BB) ?
This modification fixed the problem -- in my configuration at least.

Is there any incompatibilities between $VIMRUNTIME/compiler/tex.vim
(t63) and the one from LaTeXSuite (tls) that you want to load only
LaTeXSuite's one ?

If t63 is loaded first, then tls will override the definitions that need
to be overriden, and LaTeXSuite will ignore the other ones I guess. If
tls is loaded first, then it can set =ABcurrent_compiler=BB which will ab=
ort
the sourcing of t63.


> The standard way of using latex-suite is to unzip it in your
> ~/vimfiles directory which will create ~/vimfiles/compiler/tex.vim
> which will in turn get sourced by the above line when you open a .tex
> file.

That would be too easy. ;)
As LaTeXSuite and my configuration are quite redundant, I wanted to
progressivelly integrate LaTeXSuite. Thus I had to rewrite some plugins
of mine (like my context-dependant bracketing system) in order to fix
the problems I had, and I didn't wanted the plugin of LaTeXSuite (like
imaps.vim) to interact with my plugins the time I was fixing them.

> Don't know exactly what goes wrong in situations like yours... Has to
> do with how vim sources compiler plugins when a .tex file is opened...

It is because you used =AB:runtime=BB and not =AB:runtime!=BB I guess.

> PS: Hope latex-suite is useful :)

It is, it is.
First of all I do not need to maintain things like tex-tools.vim
anymore.  :) I can focus on my set of C&C++ ftplugins.

I will have to search within the archive if haven't missed threads about
little customisations I am interrested in (how to disable the preview of
the log file (which is not automatically reloaded BTW) , how to
integrate HT4Tex, ...), and you will see me again. :)

Thanks!
--=20
Luc Hermitte
http://hermitte.free.fr/vim/

Re: [Vim-latex-devel] First steps with LS (at last)

[Srinath A. <sr...@fa...>]

On Thu, 17 Jun 2004, Luc Hermitte wrote:

> I'm doing my first steps with LaXeX-suite (at last) and I have run into
> a little bug -- if we can call it a bug.
>
> It is easy to reproduce on my box:
>     $> gvim foo.tex
>     \ll
> And then Vim complains about s:target not defined into Tex_RunLaTeX().
>
> Once :TTarget called, and \ll typed again, vim complains about :TCLevel
> beeing undefined.
>
> After investigations, it seems that =AB:compiler tex=BB is not executed -=
-
> when I executed this, I only have one complain about a command redefined
> and then \ll can be used.
>
> It that normal ? Or is there a bug in my installation ? (LS beeing
> installed into ~/vimfiles/latex-suite which is the last directory of my
> 'runtimepath').

I remember that sourcing the compiler plugin was always a bit of
a problem... I remember that it was some subtle bug in vim itself (or
lack of documentation)... I see the following lines in main.vim:

=09" This line seems to be necessary to source our compiler/tex.vim file.
=09" The docs are unclear why this needs to be done even though this file i=
s
=09" the first compiler plugin in 'runtimepath'.
=09runtime compiler/tex.vim

So it looks like there was always a problem with getting latex-suite's
tex/compiler.vim file to get sourced... Now that you put latex-suite at
the end of the 'rtp', then latex-suite's compiler/tex.vim will not be
sourced by the above line (:runtimepath only sources the first
compiler/tex.vim found which will be vim's standard compiler/tex.vim).

Anyway...

The standard way of using latex-suite is to unzip it in your ~/vimfiles
directory which will create ~/vimfiles/compiler/tex.vim which will in
turn get sourced by the above line when you open a .tex file.

Don't know exactly what goes wrong in situations like yours... Has to do
with how vim sources compiler plugins when a .tex file is opened...

Srinath

PS: Hope latex-suite is useful :)

[Vim-latex-devel] First steps with LS (at last)

[Luc H. <her...@fr...>]

Hello,

I'm doing my first steps with LaXeX-suite (at last) and I have run into
a little bug -- if we can call it a bug.

It is easy to reproduce on my box:
    $> gvim foo.tex
    \ll
And then Vim complains about s:target not defined into Tex_RunLaTeX().

Once :TTarget called, and \ll typed again, vim complains about :TCLevel
beeing undefined.

After investigations, it seems that =AB:compiler tex=BB is not executed -=
-
when I executed this, I only have one complain about a command redefined
and then \ll can be used.

It that normal ? Or is there a bug in my installation ? (LS beeing
installed into ~/vimfiles/latex-suite which is the last directory of my
'runtimepath').

Regards.
PS: I am using the version of yesterday I think.
--=20
Luc Hermitte
http://hermitte.free.fr/vim/

Re: [Vim-latex-devel] How to print?

[Srinath A. <sr...@fa...>]

On Wed, 16 Jun 2004, Jan Ulrich Hasecke wrote:

> Srinath Avadhanula wrote:
> > There is no support for printing in latex-suite by default. I personally
> > do not see this happening any time because there is absolutely a HUGE
> > number of ways in which printing happens across platforms and even
> > within a single platform. I would recommend using the print utility of
> > the viewer which comes up by doing \lv.
>
> I'm using xdvi, which AFAIK has no printing support.
>

Well, xdvi doesn't have printing support, but most postscript viewers
do. For example, I beleive the default for latex-suite on linux is
ghostview which does do printing. Do

:TVarget ps

to set the target for viewing to ps, bring up ghostscript by doing \lv
and then print from there. You can then restore the target to dvi... You
could do all this with your own mapping. For instance:

map \lp :TTarget ps<CR>\ll:lpr -P printer_name <C-r>=Tex_GetMainFile()<CR>:TTarget dvi<CR>

Srinath

Re: [Vim-latex-devel] How to print?

[Jan U. H. <jan...@we...>]

Srinath Avadhanula wrote:
> There is no support for printing in latex-suite by default. I personally
> do not see this happening any time because there is absolutely a HUGE
> number of ways in which printing happens across platforms and even
> within a single platform. I would recommend using the print utility of
> the viewer which comes up by doing \lv.

I'm using xdvi, which AFAIK has no printing support. 

So I have to map something on my own?

juh

Re: [Vim-latex-devel] How to print?

[Srinath A. <sr...@fa...>]

On Tue, 15 Jun 2004, Jan Ulrich Hasecke wrote:

> Hi,
>
> I am new to vim and new to latex-suite and tried to find the
> print-command. Is there nothing like "\ll" for compiling or "\lv" for
> viewing?
>
> \lp or so?
>
There is no support for printing in latex-suite by default. I personally
do not see this happening any time because there is absolutely a HUGE
number of ways in which printing happens across platforms and even
within a single platform. I would recommend using the print utility of
the viewer which comes up by doing \lv.

Srinath

[Vim-latex-devel] How to print?

[Jan U. H. <jan...@we...>]

Hi,

I am new to vim and new to latex-suite and tried to find the
print-command. Is there nothing like "\ll" for compiling or "\lv" for
viewing?

\lp or so?

TIA
juh

Re: [Vim-latex-devel] [Contact] Re: Minor problem with Tex_GetVarValue(\\\'Tex_SmartBSPattern\\\')

[Srinath A. <sr...@fa...>]

On Sat, 12 Jun 2004, Srinath Avadhanula wrote:

> On Fri, 11 Jun 2004 23:33:01 -0700, "Alp ATICI"
> > I tried with the newest development version and now a backspace key press
> > in the insert
> > mode always produces the following error:
> >
> > Error detected while processing
> > function <SNR> 25_SmartBS:
> >
> > line 2:
> >
> > E55: Unmatched \\)
> >
>
> I fixed this only 2 days back. If you downloaded before then, please try
> again.

Turns out that I had made a faulty release. I have rechecked the latest
files which should NOT have this error.

Hope things work this time.

Srinath

Re: [Vim-latex-devel] [Contact] Re: Minor problem with Tex_GetVarValue(\\\'Tex_SmartBSPattern\\\')

[Srinath A. <sr...@fa...>]

I fixed this only 2 days back. If you downloaded before then, please try
again.

Srinath

On Fri, 11 Jun 2004 23:33:01 -0700, "Alp ATICI"
<vim...@so...valid> said:
> 
> I tried with the newest development version and now a backspace key press
> in the insert 
> mode always produces the following error:
> 
> Error detected while processing 
> function <SNR> 25_SmartBS:
> 
> line 2:
> 
> E55: Unmatched \\)
> 
>  
> 
> Best,
> 
> Alp  
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> From Windows to Linux, servers to mobile, InstallShield X is the
> one installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
-- 
  Srinath
  sr...@fa...

[Vim-latex-devel] [Contact] Re: Minor problem with Tex_GetVarValue(\\\'Tex_SmartBSPattern\\\')

[Alp A. <vim...@so...>]

I tried with the newest development version and now a backspace key press in the insert 
mode always produces the following error:

Error detected while processing 
function <SNR> 25_SmartBS:

line 2:

E55: Unmatched \\)

 

Best,

Alp  

[Vim-latex-devel] Support for gather in Latex-suite

[Aditya M. <adi...@al...>]

Hi,

  For some reason the gather environment is not fully supported in 
latex-suite. Some suggestions to make it better

1) file: ftplugin/latex-suite/envmacros.vim
function Tex_PutEnvironment(env)
  21st line (~line 580, I have made some changes so not sure of the 
original line number)

elseif a:env ~= 'equation*\|eqnarray*\|.....
   add \|gather\|gather* in the end

I know that this can be done with let g:Tex_Env_gather = 
"\\begin{gather}\<CR><++>\\label{<++>}\<CR>\\end{gather}<++>" but 
gather is a common environment so should be included in the default 
list.

2) In funtion Tex_ChangeEnvironments()

change
   if change_env == 'eqnarray'
   .
   .
   .
   elseif change_env == ''

to

   if change_env == 'eqnarray'
   .
   .
   .
   elseif change_env == 'gather'
 	call <SID>Change('gather',0,'&',0)
   elseif change_env == 'gather*'
 	call <SID>Change('gather*',0',&\|\\nonumber',0)
   elseif change_env == ''

so that change environment <S-F5> works smoothly with gather also.

3) In file texrc
add gather and gather* to the default Tex_PromptedEnvironments


On a different note, the prompted environments take too much space, 
this is especailly true for prompted packages, it covers almost the 
entire screen. Is it possible to have a setting like
g:Tex_ShowPromptedEnviroments, such that if it is 1, you get the 
present behaviour and if it is 0, one gets only a input() prompt,

eg, for <S-F5>
You are in a align enviroment.
What do you want to change it to?

for <F5>
Choose which enviroment to insert:

for <F5> in the preamble
Enter the package to use:

Thanks
aditya

-- 
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008

[Vim-latex-devel] [Contact] <C-j> does not forward to placeholder

[Diwaker G. <vim...@so...>]

I get the following error when I press <C-j> to for advancing to a 
placeholder:



E486: Pattern not found: =IMAP_Jumpfunc(\'\', 0)



The error 
persists even if I remind to something else. Any suggestions?  

[Vim-latex-devel] [Contact] latex suite menus persist even after closing file

[Diwaker G. <vim...@so...>]

Vim Latex is awesome -- just makes using Vim even better.



However, even after 
closing a file, the Latex Suite menus persist, which is quite annoying at times. Is 
this a bug or an intended feature? Either way, is there any way to turn them off on 
leaving a latex buffer and turning them back on entering a Latex buffer?  

[Vim-latex-devel] [Contact] Suggestion to improve help

[Alex J. <vim...@so...>]

In *recommended-settings* it is said to use things like 



set sw=2

set 
iskeyword+=: 



I think it is better to use \"setl\", rather than \"set\" - this will 
change settings to the current (tex) file only, leaving other files and files that are 
to be loaded, intact.  

[Vim-latex-devel] IgnoredWarnings bug

[Ricardo F. <rf...@if...>]

Hi,

I have a problem with the errors displayed in the error
window. A sample tex document is attached.  It consists of the
following files:

main.tex
chap1.tex
chap2.tex
main.tex.latexmain

chap1 and chap2 are input-ed into main.tex

chap1.tex contains command to include a non-existing file called a_figure.eps
Also, it contains a mistake inside a mathematical equation.

While editing any of the .tex, type "\ll".  The errors in the error log
window are:

	chap1.tex|5 warning| LaTeX Warning: File `figs/a_figure.eps' not found
	on input line 5.
	chap1.tex|5 error| File `figs/a_figure.eps' not found.
	chap1.tex|5 error| Cannot determine size of graphic in
	figs/a_figure.eps (no Boundi
	main.tex|10 error| Undefined control sequence.

What does the last line mean?? main.tex has no errors, only chap1.tex.
Strangely, the mistakes that you type *before* the includefigure environment
will be correctly logged.

I tested this with both TexSuite 1.5 and the latest development
version, under Vim 6.2 and Slackware Linux 9.1

best,
Ricardo.

--
  Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil.
  TEL: +55 016 273.9882  CEL: +55 016 9121.9046  ICQ: 208974212

Re: [Vim-latex-devel] [Contact] bibtex search and find

[Srinath A. <sr...@fa...>]

Hi,

On Mon, 7 Jun 2004, Fredrik Karlsson wrote:

> So, what I whant is a macro that asks me for a word to seach for, and
> returns (and displays) a list of references that matches my criterion.
>
> The key of the reference I choose will be inserted in the
> document inside the proper  \\cite-command.

Latex-suite already has significant support for inserting bib-keys fast
as described in:

http://vim-latex.sourceforge.net/documentation/latex-suite/latex-completion-cite.html

If you already know about this and are thinking of something else, then
please elaborate. What exactly are you looking for which is not already
there?

-- 
Srinath

NOTE: If you are not subscribed to vim-latex-devel, then further replies
      to the list will be silently ignored. Please subscribe if you wish to
      continue the thread, or use

        From: vim...@so...valid
        Reply-To: yo...@em...dress, vim...@li...

      in the header.

Re: [Vim-latex-devel] [Contact] Minor problem with Tex_GetVarValue(\'Tex_SmartBSPattern\')

[Srinath A. <sr...@fa...>]

Hi,

On Tue, 8 Jun 2004, Alp ATICI wrote:

> The problem is in file \"C:\\Program
> Files\\vim\\vimfiles\\ftplugin\\latex-suite\\main.vim\" line 266.
>
> I get the
> error:
>
> line 266:
>
> E117: Unknown function:  Tex_GetVarValue
>
> E15: Invalid
> expression: Tex_GetVarValue(\'Tex_SmartBSPattern\')
>
This bug resulted from a hastily executed addition to the code. Its
fixed in the latest release.

-- 
Srinath

NOTE: If you are not subscribed to vim-latex-devel, then further replies
      to the list will be silently ignored. Please subscribe if you wish to
      continue the thread, or use

        From: vim...@so...valid
        Reply-To: yo...@em...dress, vim...@li...

      in the header.

[Vim-latex-devel] [Contact] Minor problem with Tex_GetVarValue(\'Tex_SmartBSPattern\')

[Alp A. <vim...@so...>]

Hi,



I am having a problem with vim 6.3 (just released) and vim-latex development 
version dated 06/06.

The problem is in file \"C:\\Program 
Files\\vim\\vimfiles\\ftplugin\\latex-suite\\main.vim\" line 266.

I get the 
error: 

line 266:

E117: Unknown function:  Tex_GetVarValue

E15: Invalid 
expression: Tex_GetVarValue(\'Tex_SmartBSPattern\')



Any 
quick-fix?



Thanks!  

Re: [Vim-latex-devel] Compiling parts of a doc using \includesonly{...}

[Srinath A. <sr...@fa...>]

On Mon, 7 Jun 2004, Sebastian Menge wrote:

> Would it be possible for latexsuite to place \includesonly{thisfile}
> into the praeamble before compiling when im editing thisfile.tex at the
> moment?

I don't know if this is something which is appropriate for latex-suite
to include by default. However, it should be easy enough to do something
specifically for yourself. Example:

nmap <leader>ll :call InsertIncludesOnly()<CR><Plug>Tex_Compile

where InsertIncludesOnly() is something which you can write yourself to
handle putting an \includesonly{thisfile} into the main file.

<untested code>

function! InsertIncludesOnly()
    let thisfile = expand('%:p:t')
    let mainfname = Tex_GetMainFileName(':p')
    exec 'split '.escape(mainfname, ' ')

    " remove a previous \\includesonly if its already there
    g/^\\includesonly/d _

    " search for preamble
    if search('\\documentclass') == 0
        return
    endif

    let includeline = '\includesonly{'.thisfile.'}'
    put=includeline

    " quit the :split'ted window
    q
endfunction

</untested code>

HTH
Srinath

[Vim-latex-devel] [Contact] bibtex search and find

[Fredrik K. <vim...@so...>]

Dear list,



I would like to have a bibtex seach and inseart featyre in vim-latex. 
Finding the correct key in a large bibtex-file is by no means a trivial task, and  I have 
to say that is is essential to scientific  use of LaTeX.



So, what I whant is a macro 
that asks me for a word to seach for, and returns (and displays) a list of references 
that matches my criterion.

The key of the reference I choose will be inserted in the 
document inside the proper  \\cite-command.



Thank you in advance.  

[Vim-latex-devel] Compiling parts of a doc using \includesonly{...}

[Sebastian M. <seb...@un...>]

Hi!

I have a large document consisting of several files which I \include{}.

Would it be possible for latexsuite to place \includesonly{thisfile}
into the praeamble before compiling when im editing thisfile.tex at the
moment?

That would be really nice.

regards, Sebastian

Re: [Vim-latex-devel] Changing the makeindex program to another

[Srinath A. <sr...@fa...>]

On Sun, 6 Jun 2004, Berta Milan wrote:

> I try it as the first possibility :) But the problem occurs.
> The program 'makeindex' is called (for example on Linux)
>
> $makeindex my-file.ind
>
> latex-suite also calls this program this way.  But the (my)
> program 'csindex' (and script) must be call as follows
>
> $csindex.bat my-file
>
Okay, I just made the makeindex customizable in the latest release. Also
made the smart backspace pattern customizable. You will need to set the
following

Tex_SmartBSPattern
Tex_MakeIndexFlavor

Srinath

Re: [Vim-latex-devel] Changing the makeindex program to another

[Berta M. <ber...@ar...>]

I try it as the first possibility :) But the problem occurs.
The program 'makeindex' is called (for example on Linux)

$makeindex my-file.ind

latex-suite also calls this program this way.  But the (my)
program 'csindex' (and script) must be call as follows

$csindex.bat my-file

(because of additional program which change the encoding of
file before and after running 'csindex')

Note: The program 'csindex' is a Czech version of
'makeindex', and I think that people have several kinds of
"makeindex" program for their native languages and alphabet.

So I must change the ftplugin/latex-suite/compiler.vim.
There is a "Running makeindex..." subsection.

let temp_mp = &mp | let &mp='csindex.bat $*'

instead of

let temp_mp = &mp | let &mp='makeindex $*.idx'

Thank You for Your hint!

Latex-suite helps me very much. I write LaTeX documents
faster then before with other programs (thanks also goes to
vim :)

Milan

On Sat, Jun 05, 2004 at 06:40:48PM +0200, Srinath Avadhanula wrote:
> On Sat, 5 Jun 2004, Berta Milan wrote:
> 
> > Hi! I am going to be short: How can I change the program
> > 'makeindex' to another program (I want to use program
> > 'csindex' instead)?
> 
> As of now, this is unfortunately, not customizable. In the future, this
> will be a settable thing. for now, how about making a copy of csindex
> and call it makeindex?
> 
> Srinath