vim-latex-devel

[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

[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

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.