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

[Vim-latex-devel] Inverse and Forward Search : This is not what I expected

[ahmet n. <ahm...@ya...>]

Hi,

I am a new gvim(linux) and latex-suite user. I was
using MikTeX and YAP previewer for mytex files in
Windows. My editor of choice was WinEdt. Recently, I
switced to Debian/sarge. I was expecting the  same
functionality of inverse and forward search in TeTeX.
However what I observed in TeTeX is different in
MikTeX.

When I make a forward search in WinEdt, YAP was
displaying the position roughly corresponding to your
current position in YAP. It  points the corresponding
line and puts a circle on the line(one line below or
above of it at the worst). Inverse searching in  YAP
works almost the same: When you initiate  the inverse
search from the YAP previewer, the editor displays the
corresponding source line in a small margin of error.

In my Debian/Sarge system, I use TeTeX(ver:3.0.13) and
Xdvi(ver:22.84.9). When I initiate a forward search
from gvim, Xdvi draws a rectangle around the paragraph
in which the corresponding line in the source file
belongs to. So it is a big margin of error. Inverse
search works with the same big margin of error. It
doesn't matter where you click in a paragraph in Xdvi,
it always points the begining of a paragraph in the
corresponding source file.

I don't know what is the wrong with these inverse and
forward search. I don't think gvim is a culprit. I
tried with different editors(emacs,nedit) and
different dvi viewers(kdvi). Maybe TeTeX doesn't
handle well '--src-specials' with comparison to
MikTeX. 

I would like to thank all the developers of  the
latex-suite. I feel now that I am much more productive
than before.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Vim-latex-devel] Documentation update: alt-key macros

[Cristian R. <cr...@li...>]

Hi, while reading in the FAQ about re-mapping some alt-key macros conflicti=
ng
with Italian accented characters (everything works fine now!), I noticed th=
at
the FAQ ("Q: Typing some European characters...", the first "here" link)
points to this page:

http://vim-latex.sourceforge.net/documentation/latex-suite/bracketing-macro=
s.html
(Section 3.10, covering the Alt-L, Alt-M, Alt-C macros)

=2E..while in the current HTML online version of the documentation, Section=
 3.10
corresponds to the page

http://vim-latex.sourceforge.net/documentation/latex-suite/altkey-mappings.=
html
(which features the Alt-L, Alt-B, Alt-C, Alt-I macros)

(as a sidenote: Section 3.10 of the documentation in vim format shipping in
the latest package features the Alt-L, Alt-M, Alt-C, Alt-I macros; maybe the
HTML version is not in sync with the vim version)

Unless I am missing something, I think that the link in the FAQ should be
updated (pointing to the alt-key-mappings.html file).

Hope this helps (I'd be happy to contribute in bug-fixing the documentantion
if you need any help)

Cri

--=20
  GPG/PGP Key-Id 0x943A5F0E      -     http://www.linux.it/~cri/cri.asc

Re: [Vim-latex-devel] Invalid arguments for function substitute, etc

[Gregor B. <gre...@gm...>]

> many other files contain such commands. Do you have any idea why
> multi-line commands causes problems to my vim?

The worst thing is that if I copy the IMAP function in my .gvimrc it
WORKS?! No problem with back-slashes... But, as soon as I put the IMAP
function in my ~/.vim/plugin/ directory I get the same errors. Any
clues?

Gregor

Re: [Vim-latex-devel] Invalid arguments for function substitute, etc

[Gregor B. <gre...@gm...>]

> Interesting... Can you do a quick check... Run the command
>
> :echo substitute("12a\nb\<CR>c d", '\([^[:alnum:]]\)',
> '\=3D"_".char2nr(submatch(1))."_"', 'g')
>
> and see if you get any errors. You should get the string:
>
> 12a_10_b_13_c_32_d

I get this string. I looked in the IMAP function and found out what
the problem is. In file plugin/imaps.vim, line 181 you start a
command:

=09exe 'inoremap <silent>'
=09=09=09=09\ escape(lastLHSChar, '|')
=09=09=09=09\ '<C-r>=3D<SID>LookupCharacter("' .
=09=09=09=09\ escape(lastLHSChar, '\|"') .
=09=09=09=09\ '")<CR>'

The problem is that my vim does not "understand" this as one command.
If I join this lines and remove back-slashes, the IMAP executes
correctly. I also get all the menus in gvim. The only problem is that
many other files contain such commands. Do you have any idea why
multi-line commands causes problems to my vim?

Gregor

> If this is not causing errors, it might be some tricky i18n issue...
> If this is causing errors, it might be that vim is not compiled with
> expression support or something similar.

Re: [Vim-latex-devel] Invalid arguments for function substitute, etc

[Srinath A. <sri...@gm...>]

On 1/31/06, Gregor Berginc <gre...@gm...> wrote:
> Dear Srinath,
>
> I attached the file, produced by the above procedure. Hopefully, it
> will help you see what the problem might be.
>

Interesting... Can you do a quick check... Run the command

:echo substitute("12a\nb\<CR>c d", '\([^[:alnum:]]\)',
'\=3D"_".char2nr(submatch(1))."_"', 'g')

and see if you get any errors. You should get the string:

12a_10_b_13_c_32_d

If this is not causing errors, it might be some tricky i18n issue...
If this is causing errors, it might be that vim is not compiled with
expression support or something similar.

Srinath

Re: [Vim-latex-devel] Invalid arguments for function substitute, etc

[Gregor B. <gre...@gm...>]

Dear Srinath,

Thanks for your reply.

> 1. open a tex file. You are going to see some errors.
> 2. issue the following command:
>     :redir @a | messages | redir END
> 3. Open a new empty buffer and paste the contents of register @a. (use "a=
p)

I attached the file, produced by the above procedure. Hopefully, it
will help you see what the problem might be.

Best,
Gregor

--
Gregor Berginc, Ph.D. Student
University of Ljubljana, Faculty of CIS
Trzaska 25, SI-1001 Ljubljana, Slovenia
tel: +386 1 4776630, fax: +386 1 4264647
www: http://vicos.fri.uni-lj.si/gregor

Re: [Vim-latex-devel] Invalid arguments for function substitute, etc

[Srinath A. <sri...@gm...>]

Hi,

Unfortunately, I will need more information to help you because I
cannot reproduce this. At the very least, I would like to know which
file and line number is causing this error. This information is
provided when vim gives the error messages. To properly capture the
errors, do something like this

1. open a tex file. You are going to see some errors.
2. issue the following command:
    :redir @a | messages | redir END
3. Open a new empty buffer and paste the contents of register @a. (use "ap)

This file should hopefully elaborate on where the error occured etc.
If you can email that to me, I should be able to help you further.

Srinath

On 1/30/06, Gregor Berginc <gre...@gm...> wrote:
> Dear all,
>
> I have just installed the latex suite for vim, following the steps on
> the homepage. The help works like a charm, but the file plugin prints
> a lot of error messages like the one in the subject. I am using vim
> 6.4.
>
> Thanks for your help.
>
> Best,
> Gregor
>
> --
> Gregor Berginc, Ph.D. Student
> University of Ljubljana, Faculty of CIS
> Trzaska 25, SI-1001 Ljubljana, Slovenia
> tel: +386 1 4776630, fax: +386 1 4264647
> www: http://vicos.fri.uni-lj.si/gregor
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid=103432&bid#0486&dat=121642
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] Invalid arguments for function substitute, etc

[Gregor B. <gre...@gm...>]

Dear all,

I have just installed the latex suite for vim, following the steps on
the homepage. The help works like a charm, but the file plugin prints
a lot of error messages like the one in the subject. I am using vim
6.4.

Thanks for your help.

Best,
Gregor

--
Gregor Berginc, Ph.D. Student
University of Ljubljana, Faculty of CIS
Trzaska 25, SI-1001 Ljubljana, Slovenia
tel: +386 1 4776630, fax: +386 1 4264647
www: http://vicos.fri.uni-lj.si/gregor

[Vim-latex-devel] search for bibtex entry by regexp

[Fabian B. <f.b...@gm...>]

Hi,

I am a happy user of vim-latex, but I am missing a feature
like searching for bibtex-entry by an regular expression.
As far as I understand the manual, <F9> is looking just for
corresponding keys and e.g. not for any word in the title.

I would like to know, if anybody has a work-around for
searching the keys by regexp in vim or maybe an external
script?

Greetings!
Fabian

-- 

Re: [Vim-latex-devel] bug with <F7> command

[Srinath A. <sri...@gm...>]

On 1/23/06, Javier Rojas <jer...@gm...> wrote:
> - I type on an empty line the word subsection*, and when I press <F7>, I'=
m
> sent to the command menu, instead of getting \subsection*{}<++>. Of cours=
e,
> when the command name is made of alphabetic chars only, it works as expec=
ted.
> I'm not sure if this is a bug in vimLaTeX or if I can get the expected
> behavior setting some vim options, specially about the chars that can be =
a
> word.
>
You could have made this work my extending the 'isk' setting to
include the * character. However, I think that its not good to do
this. I modified the code so that commands ending in a * would also
count. This I think will take care of most cases. This is in CVS.

> - I'm using the penultimate CVS version, I guess is the version released =
after
> a bugfix related with the <F7> command within places like a \section{} or=
 so.
> When I select some text visually and then press <F7>, I'm asked for a com=
mand
> name (as expected), and when I give it and hit enter... nothing happens.
>
This was a bug. I fixed this in CVS.

I've also made a release with both these changes.

HTH
Srinath

[Vim-latex-devel] bug with <F7> command

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

Hi,

The <F7> mapping is not working as expected. I've seen two cases

- I type on an empty line the word subsection*, and when I press <F7>, I'm 
sent to the command menu, instead of getting \subsection*{}<++>. Of course, 
when the command name is made of alphabetic chars only, it works as expected. 
I'm not sure if this is a bug in vimLaTeX or if I can get the expected 
behavior setting some vim options, specially about the chars that can be a 
word.

- I'm using the penultimate CVS version, I guess is the version released after 
a bugfix related with the <F7> command within places like a \section{} or so. 
When I select some text visually and then press <F7>, I'm asked for a command 
name (as expected), and when I give it and hit enter... nothing happens. 
According to the docs, the selected text should be enclosed within a command 
of the name that I provided. I'm not completely sure, but I think this 
started to happen since the penultimate bugfix.

I would really appreciate if somebody could let me know if is having this 
problems too.

Thanks in advance
-- 
Javier

Re: [Vim-latex-devel] Latex-suite error

[Srinath A. <sri...@gm...>]

Hi,

Thanks for catching this and the fix.

On 1/15/06, Christian Ebert <bla...@gm...> wrote:
> Hello Tom,
>
> * Tom Vawter on Sunday, January 15, 2006 at 17:39:25 -0600:
> > ImportError:  No module named stringio
> >
> You might try and make a copy of outline.py and replace every
> occurence of `stringio' (all lowercase) with either StringIO
> (exactly like I spelled it) or even cStringIO which is supposed
> to be a bit faster.

This is a pretty embarassing mistake... The problem was I developed this
feature while working on a windows machine and since windows is not case
sensitive to filenames, python on windows is able to import modules
which are named off in case.

I have fixed this in CVS. I'm making a release right now.

Srinath

Re: [Vim-latex-devel] Latex-suite error

[Christian E. <bla...@gm...>]

Hello Tom,

* Tom Vawter on Sunday, January 15, 2006 at 17:39:25 -0600:
> Traceback (most recent call last):
>     File "<string>", line 1 in ?
>     File "/Users/tvawter/.vim/ftplugin/latex-suite/outline.py", line 12,
> in ? 
> import stringio
> ImportError:  No module named stringio
> 
> 
> I removed the outline.py file and was able to compile latex.

You might try and make a copy of outline.py and replace every
occurence of `stringio' (all lowercase) with either StringIO
(exactly like I spelled it) or even cStringIO which is supposed
to be a bit faster.

HTH

c
-- 
_B A U S T E L L E N_ lesen!  --->> <http://www.blacktrash.org/baustellen.html>

[Vim-latex-devel] `stringio' in outline.py

[Christian E. <bla...@gm...>]

Hello,

Due to a discussion on the vim list I downloaded the most recent
version which contains a python script outline.py.

Up to now I haven't experienced any problems which is strange
because IMHO there is a mistake in outline.py:

Line 12 goes:

import stringio

I am quite sure the module is called StringIO (or cStringIO)
respectively:

$ python -c 'import StringIO'
$ python -c 'import stringio'
Traceback (most recent call last):
  File "<string>", line 1, in ?
ImportError: No module named stringio

Strange.

BTW cvs checkout is not working since a few days.

c
-- 
_B A U S T E L L E N_ lesen!  --->> <http://www.blacktrash.org/baustellen.html>

[Vim-latex-devel] Latex-suite error

[Tom V. <tom...@ea...>]

I am using Mac OS X and the vim latex-suite (build date Jan 9, 2006).
When trying to compile a latex file, I got the following error message:

Error detected while processiing
/Users/tvawter/.vim/ftplugin/latex-suite/main.vim:
line 32:
E484:  Can't open file /Users/tvawter/.vim/ftplugin/latex-suite/texrc
Error detected while processing
/Users/tvawter/.vim/ftplugin/latex-suite/texviewer.vim:
line 727:
Traceback (most recent call last):
    File "<string>", line 1 in ?
    File "/Users/tvawter/.vim/ftplugin/latex-suite/outline.py", line 12,
in ?=20
import stringio
ImportError:  No module named stringio


I removed the outline.py file and was able to compile latex.  Of course
the outline file is missed and I get the error:


Error detected while processing
/Users/tvawter/.vim/ftplugin/latex-suite/texviewer.vim:
line 727:
Traceback (most recent call last):
    File "<string>", line 1 in ?
ImportError: No module named outline.


This problem has been submitted and commented on in the vim help list.
While I am able to compile, seeing the big red error message is of
concern. =20

Tom Vawter

Re: [Vim-latex-devel] compiling multiple times fails

[Srinath A. <sri...@gm...>]

Hi!

On 1/9/06, Javier Rojas <jer...@gm...> wrote:
> I did as you said, and the output of :call Tex_PrintDebug('comp') was
>
> I think the problem is due to the line 571
>
>   if errlist =3D~ 'E42: No Errors'
>
> in file ftplugin/latex-suite/main.vim
>

Actually, I think there's no reason to just check for '^E42: '. That
should be quite robust at seeing there are no errors. I changed it in
CVS (and made a release) with this fix.

Srinath

Re: [Vim-latex-devel] compiling multiple times fails

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

I did as you said, and the output of :call Tex_PrintDebug('comp') was

=2D----------------------------------%<-----------------------------------
=2E.. (same lines as you)...
=2E..
Tex_CompileLatex: execing [make! t.tex]                                    =
                                                  =20
Tex_CompileMultipleTimes: errors =3D [                                     =
                                                    =20
Se ha detectado un error al procesar function=20
Tex_RunLaTeX..Tex_CompileMultipleTimes..Tex_GetErrorList:                  =
    =20
l=EDnea    2                                                               =
                                                    =20
E42: No hay errores]                                                       =
                                                  =20
Tex_RunLaTeX: errlist =3D [                                                =
                                                    =20
Se ha detectado un error al procesar function Tex_RunLaTeX..Tex_GetErrorLis=
t:                                                =20
l=EDnea    2                                                               =
                                                    =20
E42: No hay errores]                                                       =
                                                  =20
Tex_RunLaTeX: There were errors in compiling, breaking chain...            =
                                                  =20
Tex_SetupErrorWindow: mfnlog =3D t.log                                     =
                                                    =20
=2DTex_RunLaTeX
=2D----------------------------------%<-----------------------------------

as you can see, the error messages are in spanish, my LANG is es_ES. So I=20
changed it temporally to en_US, deleted any auxiliar file, and reopened vim=
,=20
in order to send you the error messages in english. When I did \ll... it=20
worked!!! It compiled the document twice.

I think the problem is due to the line 571

  if errlist =3D~ 'E42: No Errors'=20

in file ftplugin/latex-suite/main.vim

meanwhile, I'll change that line for "E42: No hay errores"

=2D-=20
Javier

Re: [Vim-latex-devel] compiling multiple times fails

[Srinath A. <sri...@gm...>]

Hi

On 1/8/06, Javier Rojas <jer...@gm...> wrote:
> latex-suite doesn't compile multiple times. For instance, this file
>
> \documentclass{article}
> \begin{document}
> \section{uno}
> some text \label{sec:1}
> \section{2}
> in the section \ref{sec:1}
> \end{document}
>
> only is compiled one time when I use the command \ll, despite the warning=
 of
> the compiler. On others tests I've made, latex-suite doesn't launch the
> bibtex command when necessary.
>
> I have already checked the Tex_MultipleCompileFormats and
> g:Tex_MultipleCompileFormats variables and both contain the string dvi,pd=
f
>
It works for me on both windows/miktex and ubuntu/tetex.

I am not sure why its not working for you, but a good first step towards
finding out why is to set g:Tex_Debug to 1 in your ~/.vim/ftplugin/tex.vim,
remove all auxillary files (.dvi, .aux, .log), then press \ll and finally
capture the output of

    :call Tex_PrintDebug('comp')

For the little example file in your case, this is the output:
Notice the line "Need to rerun to get cross-references right...".
If that line doesn't exist in your output, then it might be a problem with
the function Tex_IsPresentInFile()

-----------------------------------%<-----------------------------------
compiler.vim: Catching LatexSuiteFileType event
+Tex_SetTeXCompilerTarget: setting target to [dvi] for Compiler
+Tex_SetTeXCompilerTarget: setting target to [dvi] for Viewr
compiler/tex.vim: sourcing this file
+Tex_RunLaTeX, b:fragmentFile =3D 0
Tex_RunLaTeX: compiling to target [dvi]
Tex_RunLaTeX: getting dependency chain =3D [dvi]
+Tex_SetTeXCompilerTarget: setting target to [dvi] for Compiler
Tex_RunLaTeX: setting target to dvi
Tex_RunLaTeX: compiling file multiple times via Tex_CompileMultipleTimes
Tex_CompileMultipleTimes: latex run number : 1
Tex_CompileLatex: getting mainfname =3D [f.tex] from Tex_GetMainFileName
Tex_CompileLatex: execing [make! f.tex]
Tex_CompileMultipleTimes: errors =3D []
Tex_CompileMultipleTimes: Need to rerun to get cross-references right...
Tex_CompileMultipleTimes: latex run number : 2
Tex_CompileLatex: getting mainfname =3D [f.tex] from Tex_GetMainFileName
Tex_CompileLatex: execing [make! f.tex]
Tex_CompileMultipleTimes: errors =3D []
Tex_CompileMultipleTimes: Ran latex 2 time(s)
Tex_RunLaTeX: errlist =3D [
 1:  ]
Tex_SetupErrorWindow: mfnlog =3D f.log
-Tex_RunLaTeX
-----------------------------------%<-----------------------------------

Srinath

[Vim-latex-devel] compiling multiple times fails

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

Hi,

latex-suite doesn't compile multiple times. For instance, this file

\documentclass{article}                                                                                                                                                                                                                  
\begin{document}                                                                                                                  
\section{uno}                                                                                                                     
some text \label{sec:1}                                                                                                           
\section{2}                                                                                                                       
in the section \ref{sec:1}                                                                                                        
\end{document}

only is compiled one time when I use the command \ll, despite the warning of 
the compiler. On others tests I've made, latex-suite doesn't launch the 
bibtex command when necessary.

I have already checked the Tex_MultipleCompileFormats and 
g:Tex_MultipleCompileFormats variables and both contain the string dvi,pdf

I'm using vim 6.3.86 on Slackware. However, I've seen this thing happening too 
in SuSE 9.2 and 10

Is there something I'm missing in my config files? I'm using the latest 
version (latexSuite20051208.tar.gz). 

Any help about this would be appreciated. In the worst case, it will be nice 
if somebody can tell me how to debug it.

Thanks in advance.
-- 
Javier

Re: [Vim-latex-devel] [Patch] fold title for \caption[desc]{longdesc} captions

[Srinath A. <sri...@gm...>]

VGhhbmtzIGEgbG90ISBJIGFwcGxpZWQgeW91ciBwYXRjaC4gSSdsbCBtYWtlIGEgcmVsZWFzZSBz
b29uLgoKVGhhbmtzLApTcmluYXRoCgpPbiAxLzIvMDYsIEJvcmlzIER1mmVrIDxib3Jpc2R1c2Vr
QGNtYWlsLmN6PiB3cm90ZToKPiBIaSwKPgo+IEkgYXR0YWNoZWQgYSBwYXRjaCByZXNvbHZpbmcg
dGhlIGZvbGxvd2luZyBpc3N1ZTogd2hlbiBlbnZpcm9ubWVudCBsaWtlCj4gImZpZ3VyZSIgb3Ig
InRhYmxlIiBpcyBmb3VuZCwgaXQgaXMgZm9sZGVkIGJ5IFZpbS1MYVRlWCBhbmQgdGl0bGUgb2Yg
dGhlIGZvbGQKPiBpcyBzZXQgdG8gY29udGVudCBvZiBcY2FwdGlvbi4gVGhpcyBkb2VzIGhhbmRs
ZSBjb3JyZWN0bHkgc2l0dWF0aW9ucyB3aGVuIHRoZQo+IGNvbW1hbmQgaXMgb2YgdXN1YWwgZm9y
bQo+Cj4gXGNhcHRpb257RGVzY3JpcHRpb24ufSwKPgo+IGJ1dCBub3QKPgo+IFxjYXB0aW9uW1No
b3J0IERlc2NyaXB0aW9uXXtMb25nIERlc2NyaXB0aW9ufS4KPgo+IE15IHBhdGNoIGVuYWJsZXMg
Zm9sZCB0aXRsZSBmb3IgdGhlIHNlY29uZCBmb3JtLCB3aGVyZSBpdCB1c2VzIHRoZSB0ZXh0IGZy
b20KPiAiU2hvcnQgRGVzY3JpcHRpb24iIGFzIHRoZSBmb2xkIHRleHQuIEl0IHdvcmtzIGZvciBt
ZSwgSSBzYXcgaXQgd29ya2luZyB3aXRoCj4gImZpZ3VyZSIgYW5kICJ0YWJsZSIgZW52aXJvbm1l
bnRzLiBQYXRjaCBzaG91bGQgYmUgYXBwbGllZCBhZ2FpbnN0IGZvbGRpbmcudmltCj4gZmlsZS4K
Pgo+Cj4gUmVnYXJkcywKPiBCb3JpcyBEdXNlawo+IDp3cQo+Cj4KPgo=

[Vim-latex-devel] [Patch] fold title for \caption[desc]{longdesc} captions

[Boris <bor...@cm...>]

Hi,

I attached a patch resolving the following issue: when environment like 
"figure" or "table" is found, it is folded by Vim-LaTeX and title of the fold 
is set to content of \caption. This does handle correctly situations when the 
command is of usual form

\caption{Description.},

but not

\caption[Short Description]{Long Description}.

My patch enables fold title for the second form, where it uses the text from 
"Short Description" as the fold text. It works for me, I saw it working with 
"figure" and "table" environments. Patch should be applied against folding.vim 
file.


Regards,
Boris Dusek
:wq

[Vim-latex-devel] ANN: A new feature: better \ref completion

[Srinath A. <sri...@gm...>]

Hi,

Wanted to announce a new feature inspired by ref-Tex.

After using the \ref completion in latex-suite to write my PhD, I
discovered that iti becomes really painful to use when there are a
HUGE number of equations distributed over multiple files. Its still
better than nothing, but an obvious improvement is to show the labels
grouped together according to which sections etc they occur in. This
will make it easier to zoom into the relevant section/subsection to
choose the correct label without having to skip over lots of
irrelevant labels.

Screenshot:

http://tinyurl.com/8ul9v

After downloading the latest release
(http://vim-latex.sourceforge.net/index.php?subject=3Ddownload&title=3DDown=
load)
to enable this feature, you need to use the setting

let g:Tex_UseOutlineCompletion =3D 1

in your ~/.vim/ftplugin/tex.vim file and if necessary, make the file
~/.vim/ftplugin/latex-suite/outline.py executable. You WILL need
python on your system. Its a very preliminary implementation which
should work well for eqnarray, equation, figure and align labels. I
need to consult with other folks who have more experience with latex
to make this more refined.

Please let me know what you think.

Thanks,
Srinath

Re: [Vim-latex-devel] environments

[Srinath A. <sri...@gm...>]

Hi,

On 12/22/05, Baris Erbas <be...@an...> wrote:

>
> under the directory you wrote above I don't have tex.vim file but rather =
I
> have two files bib_latexSuite.vim, tex_latexSuite.vim and two directories
> latex-suite and tex. The file tex.vim is under /compiler and /indent

Take a look at the following two pages:

http://vim-latex.sourceforge.net/documentation/latex-suite/customizing-late=
x-suite.html
http://vim-latex.sourceforge.net/documentation/latex-suite/customizing-macr=
os.html#Tex_Env_name

You will need to create the tex.vim file yourself if it doesn't already
exist. Its not part of latex-suite.

HTH
Srinath

RE: [Vim-latex-devel] environments

[Baris E. <be...@an...>]

Dear Javier


>create (or modify) the file ~/.vim/ftplugin/tex.vim, 

under the directory you wrote above I don't have tex.vim file but rather I
have two files bib_latexSuite.vim, tex_latexSuite.vim and two directories
latex-suite and tex. The file tex.vim is under /compiler and /indent
directories. /compiler/tex.vim is about the \ll \lv and such commands and
/indent/tex.vim is about indentation.
So am I missing something?
I will read all the available help and check all the files under ./vim but
in the meantime it would be great to have a little help to speed things up.

best wishes

Baris

>and put a line (don't
>split it like my email client does) like this on it
>
>let
>Tex_Env_{'figure'}="\\begin{figure[htbp]\\centering\<CR>\\includegraphics[w
>idth=<++>]
>{<++>}\<CR>\\caption{<+caption+>}\\label{fig:<+label+>}\<CR>\\end{figure}\<
>CR><++>"
>
>the stuff between double quotes is the way you'll redefine the environment,
>in
>this case figure, in yours, equation. Don't forget the scape backslash. You
>can define too new environments this way, and get the expansion with the
><F5>
>key
>
>All this I've explained is in the docs of vim-latex, although, in my
>opinion,
>a bit not so well presented, because you sort of know what to write but
>don't
>where to put it. Read the docs,
>
>Greets
>--
>Javier
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log
>files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>Vim-latex-devel mailing list
>Vim...@li...
>https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

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

[Srinath A. <sri...@gm...>]

Hi,

On 12/21/05, Shawn Young <spa...@gm...> wrote:

> been getting a couple of years ago.  Three windows, with one of them
> showing a list of keywords and another showing the context of the
> highlighted keyword!  I think this is the expected behavior.  Great,
> but, if I type \citet{foo<F9>, I get the same results as before, that
> is a screen flash and then the bibtex files added to the buffer list,
> but nothing else.  Very much unlike Dan, I don't have any idea how to
> proceed.  What kind of information would be relavent?

I just tried doing the completion with the latest version from CVS and
indeed, partial completion does work for me. Lets try to figure why its
not working for you.

1. I hope you are using the latest developement version and not the 1.5
   release.

2. Could you do the following:
   i. Put
        let g:Tex_Debug =3D 1
        set shell=3Dbash
        set grepprg=3Dgrep\ -nH\ $*
   in your ~/.vimrc or ~/.vim/ftplugin/tex.vim

   ii. Try opening the file which I'm attaching at the end of this
   email in vim. Go to the spot which says "\ref{fig:}" and then press
   <F9> with the cursor just after ":".

   iii. Type
        :call Tex_PrintDebug()
   and let me know what the output of the command is.

> Also, as with Dan, I want to say thanks for the effort you've put into
> this great tool!

Thanks for the encouragement!

Srinath

PS: the file for trying out:

\documentclass[a4paper]{article}
\begin{document}

This is a new file
\begin{figure}[h]
        \begin{center}
                \psfig{figure=3Dfigname.eps}
        \end{center}
        \caption{Some random caption}
        \label{fig:lab}
\end{figure}

This is another equation
\begin{equation}
        2 &=3D& 3
        \label{eqn:impossible}
\end{equation}

And another

\begin{equation}
        e^{i\pi} + 1 &=3D& 0
        \label{eqn:possible}
\end{equation}

This is a \ref{fig:} to a figure.
This is a \ref{eqn:} to an equation.

\end{document}