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

Re: [Vim-latex-devel] abbreviations break in vim-latex

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

On Tue, 25 Mar 2003, D. MacAlpine wrote:

> > >
> > Please try the latest version from the web-page. It should contain a bug
> > fix to address this... Please let us know if it works...
> >
>
> Thanks for the fast response!  I tried the March 25th version and things
> are getting closer. I have the following abbreviation set:
>
> iab     mul     $\mu$l
>
[snip]
>

Please try the latest version again...

Also, since you are using latex-suite, take a look at imaps.vim, which
contains an alternate way of creating mappings the way most latex-suite
mappings are created... hopefully, abbreviations will just work though.

Srinath

Re: [Vim-latex-devel] abbreviations break in vim-latex

[D. M. <da...@mi...>]

> >
> Please try the latest version from the web-page. It should contain a bug
> fix to address this... Please let us know if it works...
> 

Thanks for the fast response!  I tried the March 25th version and things
are getting closer. I have the following abbreviation set:

iab     mul     $\mu$l

In vim-latex the '\' is dropped out of the expanded version resulting in
$mu$l  -- If I hit <esc> or <cr> instead of <space> after the
abbreviation it is mapped correctly.

Another abbreviation I routinely use for the date is:

iab     mdyl     <c-r>=strftime("%a %d %b %Y")<cr>

Now in vim-latex this results in:

Error detected while processing function <SNR>10_LookupCharacter:
line   33:
E121: Undefined variable: a
Hit ENTER or type command to continue
Error detected while processing function <SNR>10_LookupCharacter:
line   33:
E15: Invalid expression:  "\<C-R>=strftime("%a %d %b %Y")\<CR>\<Space>"

I hope this information helps,

David
-- 
David MacAlpine				email:da...@mi...
Dept. of Biology RM 68-640		phone:(617)253-1979
Massachusetts Institute of Technology	fax:(617)253-4043
77 Massachusetts Avenue
Cambridge, MA 02139

Re: [Vim-latex-devel] Help with Compile

[Alan S. <ala...@po...>]

* Srinath Avadhanula (sr...@fa...) wrote:
> Doesn't this behavior already exist in the present version of ls?

I don't think so. It seems that if there is a Makefile, it uses it no
matter what.

> Atleast it was designed to... Could you please supply context diffs? My
> patch program seems not to like unified diffs and I am hesitant to apply
> patches manually.

Here you go (attached).

Alan

-- 
The hacker: someone who figured things out and made something cool happen.

Re: [Vim-latex-devel] TL8 and latexSuite

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

Hey Mikolaj,

On Sun, 16 Mar 2003, Mikolaj Machowski wrote:

> It works, and I have nothing against little forking, but what do you
> think about including this in main branch?
>
I think that its fine including these changes in the main branch.
Eventually, all changes have to folded back to the main branch anyway...
The overhead of forking can be left for times when we are doing
something which can potentially break existing usability.

Srinath

Re: [Vim-latex-devel] Help with Compile

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

Hello,

Tom: I think that you have a 'makefile' or 'Makefile' in the directory
     where the file being edited is present. Therefore 'makeprg' simply
     reverts to 'make dvi' when you try to run '\ll' on your latex file.
     And since (I assume) your Makefile doesn't have a 'dvi' target, you
     are getting an error. To get around this:
     1. either create a 'dvi' target in your makefile.
     2. create a .latexmain file. See help for details.

On Mon, 24 Mar 2003, Alan Schmitt wrote:

> I had this problem, so I wrote a small patch for compiler.vim. This
> patch makes the following behavior change:
> - if a something.latexmain file is present, "\ll" calls latex on that
>   file instead of make
> - otherwise, if no something.latexmain exists, it either calls make if
>   there is a Makefile, or it calls latex on the current file.
>

Doesn't this behavior already exist in the present version of ls?
Atleast it was designed to... Could you please supply context diffs? My
patch program seems not to like unified diffs and I am hesitant to apply
patches manually.

Thanks,

Srinath

Re: [Vim-latex-devel] abbreviations break in vim-latex

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

On Mon, 24 Mar 2003, D. MacAlpine wrote:

> Greetings,
>
> I am quite impressed with vim latex, but my abbreviation mappings seem
> to be broken when editing .tex files.  For example I have been using in
>
Please try the latest version from the web-page. It should contain a bug
fix to address this... Please let us know if it works...

Srinath

[Vim-latex-devel] abbreviations break in vim-latex

[D. M. <da...@mi...>]

Greetings,

I am quite impressed with vim latex, but my abbreviation mappings seem
to be broken when editing .tex files.  For example I have been using in
my .vimrc:

iab    mul     $\mu$l
iab    mug     $\mu$g

These work fine while editing non-tex files.  However if I am editing a
tex file 'mug' only works with mug<cr> instead of mug<space> and mul
doesn't work at all!  Am I missing something obvious?  I am using vim
6.1.48 and vim-latex from Feb 05, 2003 (current version on webpage).
Any help would be appreciated.

Thanks in advance,

David
-- 
David MacAlpine				email:da...@mi...
Dept. of Biology RM 68-640		phone:(617)253-1979
Massachusetts Institute of Technology	fax:(617)253-4043
77 Massachusetts Avenue
Cambridge, MA 02139

Re: [Vim-latex-devel] Help with Compile

[Benji F. <be...@me...>]

Tom Newman wrote:
> Hello,
> 
> I'm trying to figure out why I can't get the compiler to work with
> LaTeX-Suite.
> 
> Following the FAQ, the following info provided:
> 
> :echo Tex_CompileRule_dvi
> 
> Returns E121: Undefined variable Tex_CompileRule
> E15: Invalid expression: Tex_CompileRule.dvi
[snip]

      The only explanation I can think of for that error message is that you 
accidentally typed a "." instead of the second "_".  Is that what happened?

HTH					--Benji Fisher

Re: [Vim-latex-devel] Help with Compile

[Alan S. <ala...@po...>]

* Tom Newman (new...@US...) wrote:
> Hello,
> 
> I'm trying to figure out why I can't get the compiler to work with
> LaTeX-Suite.

I had this problem, so I wrote a small patch for compiler.vim. This
patch makes the following behavior change:
- if a something.latexmain file is present, "\ll" calls latex on that
  file instead of make
- otherwise, if no something.latexmain exists, it either calls make if
  there is a Makefile, or it calls latex on the current file.

Here is the patch (to apply on today's cvs)
schmitta@alan-schm1p:/usr/src/latexvim/vimfiles/ftplugin/latex-suite> cvs diff                     
Index: compiler.vim
===================================================================
RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/latex-suite/compiler.vim,v
retrieving revision 1.22
diff -u -p -r1.22 compiler.vim
--- compiler.vim        4 Mar 2003 22:58:13 -0000       1.22
+++ compiler.vim        24 Mar 2003 14:16:29 -0000
@@ -90,17 +90,11 @@ function! RunLaTeX()
        " close any preview windows left open.
        pclose!
 
-       " If a *.latexmain file is found, then use that file to
-       " construct a main file.
-       if Tex_GetMainFileName() != ''
-               let mainfname = Tex_GetMainFileName()
-       else
-               " otherwise just use this file.
+       " if a makefile and no *.latexmain exists, just use the make utility
+       " this also sets mainfname for the rest of the function
+       let mainfname = Tex_GetMainFileName()
+       if (glob('makefile') != '' || glob('Makefile') != '') && mainfname == ''
                let mainfname = expand("%:t:r")
-       endif
-
-       " if a makefile exists, just use the make utility
-       if glob('makefile') != '' || glob('Makefile') != ''
                let _makeprg = &l:makeprg
                let &l:makeprg = 'make $*'
                if exists('s:target')
@@ -110,6 +104,11 @@ function! RunLaTeX()
                endif
                let &l:makeprg = _makeprg
        else
+       " otherwise, if a *.latexmain file is found, then use that file to
+       " construct a main file.
+               if mainfname == ''
+                       let mainfname = expand("%:t:r")
+               endif
                exec 'make '.mainfname
        endif
 

Hope this helps,

Alan


-- 
The hacker: someone who figured things out and made something cool happen.

[Vim-latex-devel] Help with Compile

[Tom N. <new...@US...>]

Hello,

I'm trying to figure out why I can't get the compiler to work with
LaTeX-Suite.

Following the FAQ, the following info provided:

:echo Tex_CompileRule_dvi

Returns E121: Undefined variable Tex_CompileRule
E15: Invalid expression: Tex_CompileRule.dvi

I can run 

latex --src-specials \input{$*} 

I do not have a tex.vim file in my ~/.vim/ftplugin/ directory, but I do
have a tex-LatexSuite.vim file

:set makeprg

returns

makeprg=latex \\nonstopmode \\input\{$*.tex\}

:verbose set makeprg?

returns

makeprg=latex \\nonstopmode \\input\{$*.tex\}
       Last set from /home/thn/.vim/ftplugin/latex-suite/compiler.vim

:call RunLaTeX()

returns

:!make dvi 2>&1| tee /tmp/v485134/1
make: *** No rule to make target 'dvi'. Stop

I'm running SuSE 8.1, latex -version returns TeX (Web2C 7.3.7) 3.14159.

Any suggestions would be appreciated.  I'm spending lots of times going
back and forth between the shell and vim trying to fix all my compile
errors.

Thanks,

Tom

-- 
Tom Newman <new...@US...>

[Vim-latex-devel] Help with Compile

[Tom N. <new...@US...>]

Hello,

I'm trying to figure out why I can't get the compiler to work with
LaTeX-Suite.

Following the FAQ, the following info provided:

:echo Tex_CompileRule_dvi

Returns E121: Undefined variable Tex_CompileRule
E15: Invalid expression: Tex_CompileRule.dvi

I can run 

latex --src-specials \input{$*} 

I do not have a tex.vim file in my ~/.vim/ftplugin/ directory, but I do
have a tex-LatexSuite.vim file

:set makeprg

returns

makeprg=latex \\nonstopmode \\input\{$*.tex\}

:verbose set makeprg?

returns

makeprg=latex \\nonstopmode \\input\{$*.tex\}
       Last set from /home/thn/.vim/ftplugin/latex-suite/compiler.vim

:call RunLaTeX()

returns

:!make dvi 2>&1| tee /tmp/v485134/1
make: *** No rule to make target 'dvi'. Stop

I'm running SuSE 8.1, latex -version returns TeX (Web2C 7.3.7) 3.14159.

Any suggestions would be appreciated.  I'm spending lots of times going
back and forth between the shell and vim trying to fix all my compile
errors.

Thanks,

Tom

-- 
Tom Newman <new...@US...>

[Vim-latex-devel] TL8 and latexSuite

[Mikolaj M. <mi...@wp...>]

Hello,

In next 2 month new release of TeXLive is coming. Of course lS will be
present. Staszek Wawrykiewicz one of the leaders of this project
proposed some changes to texrc to make lS more TL8 compatible:

--8<--
----- Section " 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.
let s:CompileFlags = ''
TexLet g:Tex_EscapeChars = '{}\'
TexLet g:Tex_CompileRule_dvi = 'latex ' . s:CompileFlags .
                        \ ' -interaction=nonstopmode $*'

TexLet g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi'

" 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 $*.tex'

----- Section " Viewer rules {{{
" Viewer rules {{{
" these programs are for viewing other formats.
" NOTE: latex-suite will automatically append file.<format> to these functions
"       when calling them. The viewer therefore cannot accept arguments after
"       the filename.
"       Important for Windows users:
"       you should adapt the absolute path for gsview32 and AcroRd32 calls;
"       below you can find some standard locations of those programs.
"       Tex_ViewRule_dvi value can be set to 'yap -1' or 'windvi'.
if has('win32')
        TexLet g:Tex_ViewRule_ps = 'gsview32'
        TexLet g:Tex_ViewRule_pdf = 'AcroRd32'
        TexLet g:Tex_ViewRule_dvi = 'yap -1'

--8<--

It works, and I have nothing against little forking, but what do you
think about including this in main branch?

Mikolaj

Re: [Vim-latex-devel] =?iso-8859-2?Q?probl?= =?iso-8859-2?Q?em_with_=E2?=

[Mikolaj M. <mi...@wp...>]

On Wed, Mar 12, 2003 at 09:00:51AM -0500, Alan Schmitt wrote:
> So I added the following to my texrc:
> inoremap <buffer> <silent> <M-p> <C-r>=Tex_MathBF()<CR>
> (it is MathBF that is giving me trouble)
> but it does not work.
> Where should I add this binding so that it is taken into account ?

Is this visible in :inoremap output?

Mikolaj

[Vim-latex-devel] problem with =?iso-8859-1?Q?=E2?=

[Alan S. <ala...@po...>]

Hi,

I have a problem when trying to input =E2 in tex (that is a ^ over a 'a').
As it corresponds to =E2, which is grabbed by brackets.vim

I tried to follow the advice there:
" NOTE: The insert mode maps are created only if maps are no maps already to
" the relevant functions Tex_MathBF, Tex_MathCal and Tex_LeftRight. This is=
 to
" enable people who might need the alt keys for typing to use some other
" keypress to trigger the same behavior. In order to use some other key, (s=
ay
" <C-c>) to use Tex_MathCal(), do the following
"
" 	inoremap <buffer> <silent> <C-c> <C-r>=3DTex_MathCal()<CR>

So I added the following to my texrc:
inoremap <buffer> <silent> <M-p> <C-r>=3DTex_MathBF()<CR>

(it is MathBF that is giving me trouble)
but it does not work.

Where should I add this binding so that it is taken into account ?

Alan

--=20
The hacker: someone who figured things out and made something cool happen.

Re: [Vim-latex-devel] Strange thing ...

[Benji F. <be...@me...>]

Alan Schmitt wrote:
> Hi,
> 
> I am writing a paper where one of the rules if called "GetPut".
> However, after a certain time, when I type it, I get a bunch or errors.
> More precisely, when I type
> etP
> after typing the P I get (hiting <cr> several times):
> 
> Error detected while processing function <SNR>19_LookupCharacter:
> line   47:
> E121: Undefined variable: s:Map_tex_etP
[more errors]
> 
> and the result is
> et0
> 
> When I restart vim all is fine.
> 
> Any clue where this is coming from ? (I'm wondering if it might be
> related to the wrap issue, in the sense that some case sensitivity gets
> unset, making vim believe I'm typing ETP, then not finding any function
> to call).

      The errors seem to be from plugin/imaps.vim .  You can verify this with

:scriptnames

I get

13: path/to/imaps.vim

but you should get 19, not 13.

      The strange thing is that my version of the LookupCharacter() function 
(and I just updated via cvs) does not have 47 lines.  (It has 32, from :function 
to :endfunction .)  If your version of LookupCharacter() is longer, please post 
it.  Make sure you are posting the version in your plugin/ directory.

HTH					--Benji Fisher

[Vim-latex-devel] Strange thing ...

[Alan S. <ala...@po...>]

Hi,

I am writing a paper where one of the rules if called "GetPut".
However, after a certain time, when I type it, I get a bunch or errors.
More precisely, when I type
etP
after typing the P I get (hiting <cr> several times):

Error detected while processing function <SNR>19_LookupCharacter:
line   47:
E121: Undefined variable: s:Map_tex_etP
Hit ENTER or type command to continue
Error detected while processing function <SNR>19_LookupCharacter:
line   47:
E15: Invalid expression:  s:Map_{ft}_{hash}
Hit ENTER or type command to continue
Error detected while processing function <SNR>19_LookupCharacter:
line   48:
E121: Undefined variable: s:phs_tex_etP
Hit ENTER or type command to continue
Error detected while processing function <SNR>19_LookupCharacter:
line   48:
E15: Invalid expression:  s:phs_{ft}_{hash}
Hit ENTER or type command to continue
Error detected while processing function <SNR>19_LookupCharacter:
line   49:
E121: Undefined variable: s:phe_tex_etP
Hit ENTER or type command to continue
Error detected while processing function <SNR>19_LookupCharacter:
line   49:
E15: Invalid expression:  s:phe_{ft}_{hash}
Hit ENTER or type command to continue
Error detected while processing function <SNR>19_LookupCharacter:
line   58:
E121: Undefined variable: rhs
Hit ENTER or type command to continue
Error detected while processing function <SNR>19_LookupCharacter:
line   58:
E116: Invalid arguments for function IMAP_PutTextWithMovement
Hit ENTER or type command to continue
Error detected while processing function <SNR>19_LookupCharacter:
line   58:
E15: Invalid expression: bs . IMAP_PutTextWithMovement(rhs, phs, phe)
Hit ENTER or type command to continue

and the result is
et0

When I restart vim all is fine.

Any clue where this is coming from ? (I'm wondering if it might be
related to the wrap issue, in the sense that some case sensitivity gets
unset, making vim believe I'm typing ETP, then not finding any function
to call).

Alan

-- 
The hacker: someone who figured things out and made something cool happen.

Re: [Vim-latex-devel] a couple bugs

[Alan S. <ala...@po...>]

* Srinath Avadhanula (sr...@fa...) wrote:
> > - if I have two vertical windows (after a vsplit), the quickfix window
> >   that is opened is huge (the whole height minus two lines), and the
> >   .log window is not opened (which is bad as I thing it is a great
> >   help). Moreover, the cursor jumps to the left window (even if it
> >   contains an unrelated file), and one needs to do :cc to display the
> >   file with the error.
> 
> Try out version 1.22 of compiler.vim which fixes this. Please let me
> know if it works...

Well, I'm using the cvs version. I just did a "cvs diff" and the only
difference is the patch I sent you.

Alan

-- 
The hacker: someone who figured things out and made something cool happen.

Re: [Vim-latex-devel] why is wrap modified ?

[Alan S. <ala...@po...>]

* Srinath Avadhanula (sr...@fa...) wrote:
> 
> Hello Alan,
> 
> Thanks for the patch! This is definitely a bug. I haven't been getting
> time to fix bugs but I am willing to bet that this is a bug in the
> RunLaTeX() function. Specifically, there _is_ a line
> 	setlocal nowrap
> in there... The intention is that this happens after
> UpdatePreviewWindow() which is supposed to take focus to the .log
> window, but that part of the code is not quite robust.
> 
> Also, I tried compiling the foo.tex file you sent yesterday, but didn't
> get a hit-enter prompt... I'll try once more today and let you know.

If I find some time (read, if I get tired of writing the paper which is
long overdue and want to do a bit of hacking ;-) I'll try to see what
happens.

As for the foo.tex having you to hit <cr>, I found it is not
reproducable all the time. If I find a way to reproduce it, I'll post
it.

Alan

-- 
The hacker: someone who figured things out and made something cool happen.

Re: [Vim-latex-devel] a couple bugs

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

> I have stumbled upon a couple bugs
>
> - From time to time, when I run latex, I need to press 'Enter' for the
>   compilation to finish. Try to do \ll with the attached foo.tex (it
>   always gives me this problem), having more than one window (with only
>   one window it seems to work) (well, I cannot reproduce it all the
>   time, I'll try to find a fully reproducable procedure).
>
I do not seem to be able to reproduce this...

> - if I have two vertical windows (after a vsplit), the quickfix window
>   that is opened is huge (the whole height minus two lines), and the
>   .log window is not opened (which is bad as I thing it is a great
>   help). Moreover, the cursor jumps to the left window (even if it
>   contains an unrelated file), and one needs to do :cc to display the
>   file with the error.

Try out version 1.22 of compiler.vim which fixes this. Please let me
know if it works...

Srinath

Re: [Vim-latex-devel] why is wrap modified ?

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

Hello Alan,

Thanks for the patch! This is definitely a bug. I haven't been getting
time to fix bugs but I am willing to bet that this is a bug in the
RunLaTeX() function. Specifically, there _is_ a line
	setlocal nowrap
in there... The intention is that this happens after
UpdatePreviewWindow() which is supposed to take focus to the .log
window, but that part of the code is not quite robust.

Also, I tried compiling the foo.tex file you sent yesterday, but didn't
get a hit-enter prompt... I'll try once more today and let you know.

Thanks!
Srinath

On Tue, 4 Mar 2003, Alan Schmitt wrote:

> Hello,
>
> When I edit some tex files, I usually have wrap set. However after a
> compilation yielding an error, it gets unset. Is this bug known ?
>
> Alan Schmitt
>
> --
> The hacker: someone who figured things out and made something cool happen.
>

[Vim-latex-devel] why is wrap modified ?

[Alan S. <ala...@po...>]

Hello,

When I edit some tex files, I usually have wrap set. However after a
compilation yielding an error, it gets unset. Is this bug known ?

Alan Schmitt

-- 
The hacker: someone who figured things out and made something cool happen.

[Vim-latex-devel] a couple bugs

[Alan S. <ala...@po...>]

I have stumbled upon a couple bugs

- From time to time, when I run latex, I need to press 'Enter' for the
  compilation to finish. Try to do \ll with the attached foo.tex (it
  always gives me this problem), having more than one window (with only
  one window it seems to work) (well, I cannot reproduce it all the
  time, I'll try to find a fully reproducable procedure).

- if I have two vertical windows (after a vsplit), the quickfix window
  that is opened is huge (the whole height minus two lines), and the
  .log window is not opened (which is bad as I thing it is a great
  help). Moreover, the cursor jumps to the left window (even if it
  contains an unrelated file), and one needs to do :cc to display the
  file with the error.

Alan Schmitt

-- 
The hacker: someone who figured things out and made something cool happen.

[Vim-latex-devel] a comment / patch

[Alan S. <ala...@po...>]

Hi,

I've been using the latex suite for quite a while, but I had not been
upgrading for a very long time (more than a year). I decided to upgrade
today and I have a comment / patch.

I could not find a way to disable the use of a Makefile. I am working on
a paper with some other people who use a Makefile that is definitely not
tailored for the latex suite (interactive mode, missing targets). In
order not to use it, I did the following change:

Index: compiler.vim
===================================================================
RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/latex-suite/compiler.vim,v
retrieving revision 1.21
diff -u -p -r1.21 compiler.vim
--- compiler.vim        17 Jan 2003 18:41:44 -0000      1.21
+++ compiler.vim        3 Mar 2003 15:58:53 -0000
@@ -90,17 +90,11 @@ function! RunLaTeX()
        " close any preview windows left open.
        pclose!
 
-       " If a *.latexmain file is found, then use that file to
-       " construct a main file.
-       if Tex_GetMainFileName() != ''
-               let mainfname = Tex_GetMainFileName()
-       else
-               " otherwise just use this file.
+       " if a makefile and no *.latexmain exists, just use the make utility
+       " this also sets mainfname for the rest of the function
+       let mainfname = Tex_GetMainFileName()
+       if (glob('makefile') != '' || glob('Makefile') != '') && mainfname == ''
                let mainfname = expand("%:t:r")
-       endif
-
-       " if a makefile exists, just use the make utility
-       if glob('makefile') != '' || glob('Makefile') != ''
                let _makeprg = &l:makeprg
                let &l:makeprg = 'make $*'
                if exists('s:target')
@@ -110,6 +104,11 @@ function! RunLaTeX()
                endif
                let &l:makeprg = _makeprg
        else
+       " otherwise, if a *.latexmain file is found, then use that file to
+       " construct a main file.
+               if mainfname == ''
+                       let mainfname = expand("%:t:r")
+               endif
                exec 'make '.mainfname
        endif

This change basically short circuits the makefile if latexmain is
defined.

I have subscribed to the mailing list. I might send some more comments
as I write a paper.

Alan Schmitt

-- 
The hacker: someone who figured things out and made something cool happen.

[Vim-latex-devel] Re: :make % for tex-files

[Benji F. <be...@me...>]

Benji Fisher wrote:
> c....@gm... wrote:
>  > Hi,
>  >
>  > when I compile a tex-file, e.g. Trans.tex from within vim with :make 
> %  and
>  > then hit ENTER as I am asked by "Hit EENTER or type command to 
> continue" the
>  > file Trans.aux is diplayed in the vim window. What is strange is that 
> this
>  > doesn't happen with another file, say test.tex. Here I return to 
> test.tex
>  > after hitting ENTER, as I would like to.
>  >
>  > Any hints why one file behaves as I want to and the other doesn't?
> 
>      Are you in the directory of the file you are editing in both cases?
> 
> :pwd
> 
> What are you using to compile?
> 
> :set makeprg?

> makeprg=latex \\nonstopmode \\input\{*\}
> 
> 
> The tex-file is compiled correctly.
> I think a multiply defined label is to blame. In the quickfix window the line 
> 
> ./Trans.aux|| Label `eq:34' multiply defined.
> 
> is highlighted. All other lines start either with || or the filename.
> And that's the reason why this behaviour did not occure when I copy and pasted the contents of the file to another one and compiled it for the first time, because there the .aux file which contains the informations about labels and so on did not yet exist.
> Having deleted one of the doubly defined label everything worked again as I wanted it to.
> 
> Is there a way to avoid this behaviour?

      It looks as though you are using LaTeX suite, so I am forwarding this to 
the vim-latex mailing list.  I am not sure whether this is the intended 
behavior.  If the only error in your file is a multiply-defined label (or, 
presumably, something else that tex finds in your .aux file) then LaTeX suite 
seems to take you there.

HTH					--Benji Fisher

Re: [Vim-latex-devel] sourcing package files under windows

[Mikolaj M. <mi...@wp...>]

On Thu, Feb 27, 2003 at 01:30:26PM -0500, Benji Fisher wrote:
> >        exec "normal! /{\<CR>lv/}\<CR>h\"ay"
> >
> >Solution is to remove h.
> >But I would like to know if this is working on other machines before
> >commiting.
> How about
> 	exec "normal! /{\<CR>\"ayi}"
> instead?  Besides being shorter, it works {
> even here
> }
> I think.

Old version worked also but there was problems with cutting letters.
Your solution works and is less expensive.

m.