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

[Vim-latex-devel] [vim-latex - Help] A bug?

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=2061707
By: zlb

I have encountered a problem with one of my document.
I'm not sure whether it was because of a bug in vim-latex or
I was doing something wrong.

To illustrate the problem I have worked out a sample TeX file which only contains
the following lines:

------------------------- sample.tex -------------------
aaaaa

\section{AAA}

\begin{verbatim}
    \usepackage{anypackage}
\end{verbatim}
---------------------------- cut --------------------------

'sample.tex' can be loaded into vim without problem. But if
first open another TeX file by, say 'gvim somefile.tex', then load 'sample.tex'
with ':edit sample.tex', gvim blocks. By pressing Ctrl-C I get the following
messages:

Error detected while processing /home/zlb/.vim/ftplugin/tex_latexSuite.vim:
line   13:
Interrupted
Error detected while processing /usr/share/vim/vim61/ftplugin/tex.vim:
line    1:
Interrupted

The same problem also appears when toggling
between the two buffers with ":buffer 1" and ":buffer 2" commands, as long as
\section{AAA} is folded (the
problem does not appear if \section{AAA} is unfolded).

I was using 'latexSuite20030606.tar.bz'.


______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/monitor.php?forum_id=173627

[Vim-latex-devel] [vim-latex - Help] RE: Errors with vim-latex in windows

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=2061676
By: zlb

I'm new to vim-latex and I find it very useful. Thanks for your
work.

I also encountered this problem. I think that the problem is
caused by using the byte 0xa1 which is part of some GBK
chars as the seperator inTex_IgnoredWarnings.

A possible solution might be changing the seperator to 0x7f
which is not used by the Chinese encodings, nor in
ordinary texts in western encodings, I believe. And more
over its default catcode is 'invalid' in TeX.


______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/monitor.php?forum_id=173627

Re: [Vim-latex-devel] latex-completion

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

On Thu, 12 Jun 2003, Nico Mock wrote:

> Hello All,
>
> Anyway to include mechanik.tex into the search without moving it to my main
> directory ?
>

After taking a look at ~/.vim/ftplugin/tex/texview.vim, it looks like
the g:projFiles are used only in searching for citations, i.e for
completions to \cite...

Maybe Mikolaj will change this in the future. He's off on a trip for
a while...

Srinath

Re: [Vim-latex-devel] Ctrl-J & hlsearch

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

BTW, it would be really nice if you could send me your ~/.viminfo or
~/_viminfo when this bug happens... So to report a bug if it happens
again:

1. make a copy of your ~/.viminfo
2. try to remember what you did upto this point.

send me both these items.

Srinath

Re: [Vim-latex-devel] Ctrl-J & hlsearch

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

Hello,

On Thu, 12 Jun 2003, A. S. Budden wrote:

> Hi there,
>
> In my .vimrc, I have:
>
> set hlsearch
>
> So that when I search for things, it automatically highlights all the
> occurrences. However, when I use Ctrl-J as well as some of the macros
> like ETE in vim-latex, the { symbol is highlighted over the page until I
> do :noh
>
I did a little investigating and found that in certain cases, when
a \usepackage line is detected, then a { is inserted into the search
history. I removed that bug in the latest cvs. I still haven't been able
to reproduce any problems with { getting into the search history with
macros etc. Could you give me a better description of the problem
(with hopefully steps on how to reproduce it?) if the problem persists?

> Is there any way to make vim-latex do a :noh after it's various
> operations -- the bright yellow {s are annoying.

I would rather that vim-latex didn't do any :noh kind of things... If
this gets really annoying you can do something like

:nmap <F7> :set hls!<CR>:set hls?<CR>

and then have 'nohls' set by default and when you do searches, you can
press <F7> quickly.

HTH
Srinath

Re: [Vim-latex-devel] Ctrl-J & hlsearch

[Mpiktas <mp...@de...>]

Hi,

> In my .vimrc, I have:
>=20
> set hlsearch
>=20
> So that when I search for things, it automatically highlights all the
> occurrences. However, when I use Ctrl-J as well as some of the macros
> like ETE in vim-latex, the { symbol is highlighted over the page until =
I
> do :noh
>=20
> Is there any way to make vim-latex do a :noh after it's various
> operations -- the bright yellow {s are annoying.
>=20

Noticed the same thing, see my previous posts. Tried to look at scripts b=
ut=20
with no avail.

Mpiktas

[Vim-latex-devel] Ctrl-J & hlsearch

[A. S. B. <vim...@so...>]

Hi there,

In my .vimrc, I have:

set hlsearch

So that when I search for things, it automatically highlights all the
occurrences. However, when I use Ctrl-J as well as some of the macros
like ETE in vim-latex, the { symbol is highlighted over the page until I
do :noh

Is there any way to make vim-latex do a :noh after it's various
operations -- the bright yellow {s are annoying.

Many thanks in advance,

Al

[Vim-latex-devel] latex-completion

[Nico M. <nic...@cs...>]

Hello All,

latex-suite seems to be quite the stuff i need to write my thesis... But I 
have one question ....

latex-completion seems to work only for files within one directory and not for 
*.tex files I've added to the project. I've added 
the line 
let g:projFiles = "arbeit.tex,mechanik/mechanik.tex" 
to my arbeit.tex.latexmain file using TProjectEdit. 
<F9> after \ref{ ignores the file mechanik.tex .....
Anyway to include mechanik.tex into the search without moving it to my main 
directory ?

greetings

Nico

Re: [Vim-latex-devel] (no subject)

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

On Sun, 8 Jun 2003, Asokan  K wrote:

> I have found a bug, though.  The function keys F5, F9 and
> F10 work only in the first file in the buffer.
> Say, I have a main tex file run.tex.  I edit the file
> with
> gvim run.tex
> Then go to an included file, say intro.tex, with
> :e intro.tex
> But the function keys F5 and F9 have no effect in intro.tex

These problems have been fixed in the laest CVS. It will be a little
while before making another release.

> The new part-compilation option is good, but not quiet
> usefull for repeated use. Say, I select a part of the document
> compile it with F10 which creates a tem file in /temp directory.
> If I make some more corrections in the text, select the text
> and again part compile it creates a new file in the /temp dir.
> It would be nice if the new temp file overwrites the first so
> that by pressing \ls and refreshing the dvi I can see the
> changes.
>
I'll place this on the "to think about" list.

Srinath

Re: [Vim-latex-devel] Two suggestions about F9

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

On Wed, 11 Jun 2003, Srinath Avadhanula wrote:

> > 2/ A small bug - after completing argument for \ref, scrolloff doesn't
> > get back to its previous value (I use scrolloff=0), it stays at 100.
>
> I'll fix this.
>
Fixed in the latest CVS.

Srinath

Re: [Vim-latex-devel] Two suggestions about F9

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

On Fri, 30 May 2003, Jakub Turski wrote:

> Greetings ;)
>
> 1/ It is slow :/ Awfully. Running here on 1GHz athlon, there's a lag upon
> pressing [down] on the list with the choices. Can't this be improved?

The lag is in pressing <down> in the choices or loading up the choices
in the first place?

If the delay is in loading the choices for first time:

I cannot think about anything which can be done... <F9> works by calling
grep which is external to vim... The time taken after that should be
negligible... Infact <F9> is essentially just the standard vim grep
command. I assume therefore that doing something like
    :grep \\label{ *.vim
from within vim is also very slow for you... For me (Pentium 4 1.3 GHz),
there is a fractional second lag, but its not a big deal. How many .tex
file do you have? And how big? Thats mostly the reason for the
slowdown. Are you using fgrep or findstr... fgrep should be decently
fast.

> 2/ A small bug - after completing argument for \ref, scrolloff doesn't
> get back to its previous value (I use scrolloff=0), it stays at 100.

I'll fix this.

> I'm using latest CVS.
Thanks for the info

Srinath

[Vim-latex-devel] Re-working the manual

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

Hello,

Enthused by Animesh's efforts to write a tutorial, I am simultaneously
trying to improve the current documentation. In particular, I am
translating the current documentation from vim-help format to xml. This
will help create easily navigable html files unlike the present
situation where there is one big file.

Take a peek at the current version:

http://vim-latex.sourceforge.net/tutorial/latex-suite/index.html

The major addition to the current documentation is the addition of the
"Customization" section, which basically describes each of the settings
in the texrc file in detail linking to relevant sections etc.

I have also translated the biggest chapter, the Latex-Suite Macros from
vim-help to xml.

The xml source for all of this is under the
vim-latex/tutorial/latex-suite.xml module in the project's CVS
repository. It can be viewed online at:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vim-latex/vim-latex/tutorial/

Take a look...

A request to everyone interested: Please help with the translation!!!
And Mikolaj, could you please henceforth put any new documentation
directly into the xml file? I am working on and off on the xml2vimhelp
utility. It should be ready sometime, not soon though. In the meantime,
I think its better to maintain the xml version.

Thanks!

Srinath

Re: [Vim-latex-devel] Alt+somekey mappings

[Mpiktas <mp...@de...>]

Hi,

> Another way to have Alt not open up menus is
> 	:set nowinaltkeys
> However, that is much more aggressive in that you will never be able to
> access menus via the keyboard. But do you need to?

Thanks, I really do not need to:)
>=20
> I did not quite keep up with that discussion. If I remember correctly,
> European users want <M-l> to insert =C3=AD or something similar. But ag=
ain,
> some other European users find that there are some other ways to insert
> =C3=AD which are easier or something. Is that the case with you? Or do =
you
> never need to insert =C3=AD into your documents?
>=20
> If possible, please write a little about what you do so if someone else
> asks, I can sound a bit more intelligent :)
>=20

I am from Lithuania and Lithuanian alphabet differs from English that it =
has=20
letters =C4=85=C4=8D=C4=99=C4=97=C4=AF=C5=A1=C5=B3=C5=AB=C5=BE and doesn'=
t have letters xqwf. In the old days (5-6 years=20
ago :) there were problems with these letters, cause they weren't in defa=
ult=20
English (ISO-8859-1) keyboard layout and there were no way to produce the=
m=20
directly, so one way to elude this problem was to use special mappings to=
=20
produce these letters. Nowadays there is no need to use special mappings =
for=20
special letters. I can set my locale to lt_LT.utf-8 or lt_LT.iso8859-13,=20
configure a bit my X server and voila, I can type these special letters=20
directly, i.e. one letter with one key. So I do not need any special mapp=
ings,=20
instead I want to use them for something else. For example
I can use A-m to produce $<++>$<++> instead of =C4=A3, the letter which I=
 do not=20
use at all.

Mpiktas

Re: [Vim-latex-devel] Alt+somekey mappings

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

Thanks for the tips! A few things...

On Tue, 10 Jun 2003, Mpiktas wrote:

> Answering myself, yes there is. I edited file texmenuconf.vim and changed
> E&lements into Elements, and edited menu.vim in ../vim61 and changed &Buf=
fers
> into Buffers. So I can freely use mappings A-l and A-b, but I did not use
> them, because they are already used in brackets.vim in much more efficien=
t way
> than I wanted to use them:)
>

Another way to have Alt not open up menus is
=09:set nowinaltkeys
However, that is much more aggressive in that you will never be able to
access menus via the keyboard. But do you need to?

> > Another question would be where to find all default latex-suite shortcu=
ts?
> > In texrc is a link to texmaps.vim, but there is no such file in latex-s=
uite.
> > I'm especialy interested in mappings like A-q which produces special le=
tters
> > not found in default iso8859-1 encoding.
> I found in brackets.vim that European users have problems with A- mapping=
s.
> Yet my problem was to override the default shortcuts and imap surely does=
 that.

I did not quite keep up with that discussion. If I remember correctly,
European users want <M-l> to insert =ED or something similar. But again,
some other European users find that there are some other ways to insert
=ED which are easier or something. Is that the case with you? Or do you
never need to insert =ED into your documents?

If possible, please write a little about what you do so if someone else
asks, I can sound a bit more intelligent :)

> > Another little problem is that latex-suite highlights all { in text
> > if I use some special latex-suite shortcut like EEQ for example.
> > This behaviour always appears with newly opened .tex files (when
> > there are no other instances of gvim).
> >
>
> To this problem I found no cure. I think it is a bug. Should I file a bug
> report or what?
>
I'll look into this.

Thanks,

Srinath

Re: [Vim-latex-devel] Alt+somekey mappings

[Mpiktas <mp...@de...>]

Hi,

> I use latex-suite time from time, mostly when I need to write some repo=
rt:)=20
> I think it is great tool, and it makes life with tex/latex much more ea=
sier.=20
> However I stumbled into some problems. Namely I want to use shortcuts A=
-m=20
> and A-l. I tried to use call IMAP, yet it is overriden with menu shortc=
uts.=20
> A-m opens TeX-Math menu, A-l opens TeX-
> elements menu. Is there a way to elude these shortcuts and use mine ins=
tead?

Answering myself, yes there is. I edited file texmenuconf.vim and changed=
=20
E&lements into Elements, and edited menu.vim in ../vim61 and changed &Buf=
fers=20
into Buffers. So I can freely use mappings A-l and A-b, but I did not use=
=20
them, because they are already used in brackets.vim in much more efficien=
t way=20
than I wanted to use them:)


> Another question would be where to find all default latex-suite shortcu=
ts?=20
> In texrc is a link to texmaps.vim, but there is no such file in latex-s=
uite.=20
> I'm especialy interested in mappings like A-q which produces special le=
tters=20
> not found in default iso8859-1 encoding.
I found in brackets.vim that European users have problems with A- mapping=
s.=20
Yet my problem was to override the default shortcuts and imap surely does=
 that.

>=20
> Another little problem is that latex-suite highlights all { in text if =
I use=20
> some special latex-suite shortcut like EEQ for example. This behaviour=20
> always appears with newly opened .tex files (when there are no other=20
> instances of gvim).
>=20

To this problem I found no cure. I think it is a bug. Should I file a bug=
=20
report or what?

Mpiktas

Re: [Vim-latex-devel] Alt+somekey mappings

[Mpiktas <mp...@de...>]

Hi,


As always I forgot to write about what OS I'm using:) So I'm using Debian=
 Gnu/
Linux up to date Sid. Or Gnome 2.2 with Sawfish 1.3 and vim 6.1-474+2.

Mpiktas

[Vim-latex-devel] Alt+somekey mappings

[Mpiktas <mp...@de...>]

Hi,

I use latex-suite time from time, mostly when I need to write some report=
:) I=20
think it is great tool, and it makes life with tex/latex much more easier=
.=20
However I stumbled into some problems.=20
Namely I want to use shortcuts A-m and A-l. I tried to use call IMAP, yet=
 it=20
is overriden with menu shortcuts. A-m opens TeX-Math menu, A-l opens TeX-
elements menu. Is there a way to elude these shortcuts and use mine inste=
ad?=20
Another question would be where to find all default latex-suite shortcuts=
? In=20
texrc is a link to texmaps.vim, but there is no such file in latex-suite.=
 I'm=20
especialy interested in mappings like A-q which produces special letters =
not=20
found in default iso8859-1 encoding.

Another little problem is that latex-suite highlights all { in text if I =
use=20
some special latex-suite shortcut like EEQ for example. This behaviour al=
ways=20
appears with newly opened .tex files (when there are no other instances o=
f=20
gvim).

I would be very grateful for any explanations

Mpiktas

[Vim-latex-devel] Updated quickstart

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

Hello,

I have almost finished writing up the quickstart for latex-suite. Check
it out here:

http://vim-latex.sourceforge.net/doc/tutorial/quickstart.html

I do not plan on expanding it much more because thats part of the
tutorial Animesh is writing up.

Animesh:

I have created a module in the vim-latex CVS repository under
vim-latex/tutorial which contains the last VLS.txt file you gave me.
I will add you as a developer to our sf.net project. (For now) please
make commits only in the vim-latex/tutorial module.

Also, it might be easier in the long run to write directly in xml and
use saxon or something to convert to html. I am working (pretty rarely)
on a tool to convert docbook xml to vim-help format.

Srinath

[Vim-latex-devel] Two suggestions about F9

[Jakub T. <ya...@ch...>]

Greetings ;)

1/ It is slow :/ Awfully. Running here on 1GHz athlon, there's a lag upon
pressing [down] on the list with the choices. Can't this be improved?

2/ A small bug - after completing argument for \ref, scrolloff doesn't get back
to its previous value (I use scrolloff=0), it stays at 100.

I'm using latest CVS.

Q.
-- 
   __    __.--------------------------http://yacoob.dnsalias.net/cv.html---.__
  (oo)  |             Bother! said Pooh, as Scotty beamed him up.             |
 / \/ \ |                                                                     |
 `V__V' `--.__penguin_#128720______________________________________________.--'

[Vim-latex-devel] Restructuring of compiler.vim and wizardfuncs.vim

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

Hello,

[This email is mostly meant for core developers]

Restructured compiler.vim to include the stuff about part compilation.
This does not belong in wizardfuncs.vim imo. Also setting g:tfile and other
such global variables to handle part compilation seems very awkward.
Changed code around so that minimal changes are required.

The present behavior is when part compilation is required, then
Tex_PartCompile() creates a temporary file with b:fragmentFile set. This
buffer variable tells RunLaTeX() that this is a fragment and to ignore
*.latexmain, makefile etc.

Also changed maps around. It looks like part compilation only makes sense
in visual mode. Therefore \ll in normal mode compiles present file and \ll
in visual mode compiles the visually selected portion. The user can
always recover the last selection by pressing gv in normal mode.

Also the previous way of defining \lv in visual mode doesn't make sense.
For example, if the user chooses a different portion of the file and
presses \lp, then it would show the .dvi file from whatever fragment was
compiled last, not the present chosen fragment. The only sensible way for
this to work is to show the dvi file compiled from the present file.
b:fragmentFile helps ViewLaTeX() do this better.

Hopefully, this should make all of this much less confusing.

Summary:
1. \ll in normal mode: works like always.
2. \ll in visual mode: compiles visually selected portion. <F10> also does
   the same thing. <F10> only works in visual mode.
   \ll in visual mode also has the effect of taking focus to the
   fragment file generated from the current selection.
3. \lv (only in normal mode): views dvi file generated from whatever
   file is being currently edited. Thus to view the dvi file from
   a fragment, use \lv when you are editing the fragment.

Plese let me know asap if I have inadvertently left any bugs in.

Srinath

[Vim-latex-devel] (no subject)

[Asokan K <as...@re...>]

Hello every body.  Thanks for the latest release of Latex Suite.
I am one who use the script extensively.  Thanks to all those
involved in the project.

I have found a bug, though.  The function keys F5, F9 and
F10 work only in the first file in the buffer.
Say, I have a main tex file run.tex.  I edit the file
with
gvim run.tex
Then go to an included file, say intro.tex, with
:e intro.tex
But the function keys F5 and F9 have no effect in intro.tex

The new part-compilation option is good, but not quiet
usefull for repeated use. Say, I select a part of the document
compile it with F10 which creates a tem file in /temp directory.
If I make some more corrections in the text, select the text
and again part compile it creates a new file in the /temp dir.
It would be nice if the new temp file overwrites the first so
that by pressing \ls and refreshing the dvi I can see the 
changes.

regards

Asokan




___________________________________________________
Get www. mycompany .com and 5 matching email ids.
Just Rs. 1499/ year.
Click here http://www.rediffmailpro.com

Re: [Vim-latex-devel] Re: Whats happening?!

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

On Sat, Jun 07, 2003 at 04:10:01AM -0700, Srinath Avadhanula wrote:
> On Sat, 7 Jun 2003, Srinath Avadhanula wrote:
> > Hello,
> >
> > Tried using latex-suite after a while. Found out that the <F9> thing for
> > inserting references does not work. Then took a brief look at
> > texviewer.vim but was instantly confounded. Much to my shock I also just
> Sorry for the little outburst. I finally realized (after spending quite
> a bit of time twiddling my thumbs) that this was a problem in vimrun.exe
> which only windows users will experience (so its perfectly
> understandable if this was ignored).
> Also, the latest CVS doesn't seem to have the multiple menu problem but
> if I install the latest CVS tarball on top of existing versions, I get
> the problem... Will investigate more later.

It this is tar.gz tarball from sf.net it is highly probable sf.net
problem. Alas, in many occasions their tarballs were broken: or package
format isn't proper or something with versions. 

> But we will have to figure out a way to be compatible with the original
> explorer.vim. We cannot just clobber something which ships with the
> standard vim distro.

We need something to handle more sophisticated projects when files of
various types are dispersed throughout directories. latexSuite can now
automagically nice handle projects in one directory without any help
from user but this is not always the case. Also help for viewing those
files as project is like in IDE is good thing. For such functionality we
need modified version of one of explorer variations. Maybe something
like opsplorer.vim (with tree view) would be better but explorer.vim was
easier to modification or addition of new features. With current
standard explorer.vim it is impossible eg insert filename with relative
path. Of course you can try to persuade Bram to make explorer.vim
"pluginable" but it will be widely available from Vim 6.3 - what with
backward compatibility to 6.0? Especially when 6.2 looks buggy
release...

m.

ps. I am leaving tomorrow morning and in next three weeks I will have
very limited access to mail. Don't expect answers from me until begin of
July.

[Vim-latex-devel] Re: Whats happening?!

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

On Sat, 7 Jun 2003, Srinath Avadhanula wrote:

> Hello,
>
> Tried using latex-suite after a while. Found out that the <F9> thing for
> inserting references does not work. Then took a brief look at
> texviewer.vim but was instantly confounded. Much to my shock I also just

Sorry for the little outburst. I finally realized (after spending quite
a bit of time twiddling my thumbs) that this was a problem in vimrun.exe
which only windows users will experience (so its perfectly
understandable if this was ignored).

Also, the latest CVS doesn't seem to have the multiple menu problem but
if I install the latest CVS tarball on top of existing versions, I get
the problem... Will investigate more later.

But we will have to figure out a way to be compatible with the original
explorer.vim. We cannot just clobber something which ships with the
standard vim distro.

Srinath

[Vim-latex-devel] Whats happening?!

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

Hello,

Tried using latex-suite after a while. Found out that the <F9> thing for
inserting references does not work. Then took a brief look at
texviewer.vim but was instantly confounded. Much to my shock I also just
found out that we are using a "changed" copy of explorer.vim. With the
exact same command names etc!!! Is this what we really want?!!! This
will ruin things for people who want to use the original explorer.vim
for what it was designed for! I do not understand how we can do this.
This _has_ to change. Also I am slowly getting the feeling that
latex-suite is getting a little too heavy. There are multiple files all
over the place, several functions do the very same thing etc etc.

I really hope some time can be spent on these issues instead of working
to keep adding feature after feature after feature... Since I began
playing with latex-suite yesterday, I found that half the things no
longer work, there are obvious bugs like multiple menus etc :( I feel
kind of lost in the middle of all this.

Srinath

Re: [Vim-latex-devel] latexSuite 20030605

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

Hello,

I just updated to the latest version and when I start up LS, I get
a _huge_ number of menus... In addition to the original menus, I get
a lot of duplicates. I get TeX-Math, I get Math. In addition, I get
Dimensions, Counters, Fonts and Environments which are already available
in various other locations...

I hope this can be rectified soon. Also, in the latex-suite directory,
there are various new files such as mathmacros-utf.vim etc... Wonder
what these are for. The better way seems to be to convert everything to
utf8 since vim can read these. We definitely should avoid duplicates.

I have been out of the loop for so long that I do not even know how to
fix this. After taking a cursory look at the current status, I get the
feeling that latex-suite is getting rather large... Hope there is not
too much redundancy...

Srinath

On Fri, 6 Jun 2003, Mikolaj Machowski wrote:

> Hello,
>
> Looks only I have problems with unescaped chars in compiler.vim
> Srinath reversed changes and 20030605 is an official stable version.
>
> Enjoy! :)
>
> m.
>