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

[Vim-latex-devel] .vimrc file

[Diego A. <daa...@ya...>]

Dear developers,

I am trying to install and use VIM-Latex on a Win XP laptop per these instructions:

http://vim-latex.sourceforge.net/index.php?subject=download&title=Download

Step 1 of 4 was completed very well and the files were extracted correctly.  The second step is what's causing me grief   I can't find a file named .vimrc anywhere but I do find a file called _vimrc which has:

set nocompatible
source $VIMRUNTIME/vimrc_example.vim
source $VIMRUNTIME/mswin.vim
behave mswin

set diffexpr=MyDiff()
function MyDiff()
  let opt = '-a --binary '
  if &diffopt =~ 'icase' | let opt = opt . '-i ' | endif
  if &diffopt =~ 'iwhite' | let opt = opt . '-b ' | endif
  let arg1 = v:fname_in
  if arg1 =~ ' ' | let arg1 = '"' . arg1 . '"' | endif
  let arg2 = v:fname_new
  if arg2 =~ ' ' | let arg2 = '"' . arg2 . '"' | endif
  let arg3 = v:fname_out
  if arg3 =~ ' ' | let arg3 = '"' . arg3 . '"' | endif
  let eq = ''
  if $VIMRUNTIME =~ ' '
    if &sh =~ '\<cmd'
      let cmd = '""' . $VIMRUNTIME . '\diff"'
      let eq = '"'
    else
      let cmd = substitute($VIMRUNTIME, ' ', '" ', '') . '\diff"'
    endif
  else
    let cmd = $VIMRUNTIME . '\diff'
  endif
  silent execute '!' . cmd . ' ' . opt . arg1 . ' ' . arg2 . ' > ' . arg3 . eq
endfunction

Is that the file that you are referring to or should I write a .vimrc file with the following?


filetype plugin on
set shellslash
set grepprg=grep\ -nH\ $*
filetype indent on

Please help me 

Regards,


Diego Acosta



 		
---------------------------------
Yahoo! Music Unlimited - Access over 1 million songs.Try it free. 

[Vim-latex-devel] [vim-latex - Help] .vimrc or _vimrc in Win XP?

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

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

I am trying to install and use VIM-Latex on a Win XP laptop per these instructions:
 
http://vim-latex.sourceforge.net/index.php?subject=download&title=Download 
 
Step 1 of 4 was completed very well and the files were extracted correctly.
The second step is what's causing me grief I can't find a file named .vimrc
anywhere but I do find a file called _vimrc which has:
 
set nocompatible 
source $VIMRUNTIME/vimrc_example.vim 
source $VIMRUNTIME/mswin.vim 
behave mswin 
 
set diffexpr=MyDiff() 
function MyDiff() 
let opt = '-a --binary ' 
if &diffopt =~ 'icase' | let opt = opt . '-i ' | endif 
if &diffopt =~ 'iwhite' | let opt = opt . '-b ' | endif 
let arg1 = v:fname_in 
if arg1 =~ ' ' | let arg1 = '"' . arg1 . '"' | endif 
let arg2 = v:fname_new 
if arg2 =~ ' ' | let arg2 = '"' . arg2 . '"' | endif 
let arg3 = v:fname_out 
if arg3 =~ ' ' | let arg3 = '"' . arg3 . '"' | endif 
let eq = '' 
if $VIMRUNTIME =~ ' ' 
if &sh =~ '\<cmd' 
let cmd = '""' . $VIMRUNTIME . '\diff"' 
let eq = '"' 
else 
let cmd = substitute($VIMRUNTIME, ' ', '" ', '') . '\diff"' 
endif 
else 
let cmd = $VIMRUNTIME . '\diff' 
endif 
silent execute '!' . cmd . ' ' . opt . arg1 . ' ' . arg2 . ' > ' . arg3 . eq 
endfunction 
 
Is that the file that you are referring to or should I write a .vimrc file with
the following?
 
filetype plugin on 
set shellslash 
set grepprg=grep\ -nH\ $* 
filetype indent on 
 
Please help me  
 
Regards, 
 
 
-D- 

______________________________________________________________________
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/unmonitor.php?forum_id=173627

[Vim-latex-devel] [vim-latex - Help] .vimrc or _vimrc in Win XP?

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

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


I am trying to install and use VIM-Latex on a Win XP laptop per these
instructions:

http://vim-latex.sourceforge.net/index.php?subject=download&title=Download

Step 1 of 4 was completed very well and the files were extracted correctly.
The second step is what's causing me grief   I can't find a file named .vimrc
anywhere but I do find a file called _vimrc which has:

set nocompatible
source $VIMRUNTIME/vimrc_example.vim
source $VIMRUNTIME/mswin.vim
behave mswin

set diffexpr=MyDiff()
function MyDiff()
  let opt = '-a --binary '
  if &diffopt =~ 'icase' | let opt = opt . '-i ' | endif
  if &diffopt =~ 'iwhite' | let opt = opt . '-b ' | endif
  let arg1 = v:fname_in
  if arg1 =~ ' ' | let arg1 = '"' . arg1 . '"' | endif
  let arg2 = v:fname_new
  if arg2 =~ ' ' | let arg2 = '"' . arg2 . '"' | endif
  let arg3 = v:fname_out
  if arg3 =~ ' ' | let arg3 = '"' . arg3 . '"' | endif
  let eq = ''
  if $VIMRUNTIME =~ ' '
    if &sh =~ '\<cmd'
      let cmd = '""' . $VIMRUNTIME . '\diff"'
      let eq = '"'
    else
      let cmd = substitute($VIMRUNTIME, ' ', '" ', '') . '\diff"'
    endif
  else
    let cmd = $VIMRUNTIME . '\diff'
  endif
  silent execute '!' . cmd . ' ' . opt . arg1 . ' ' . arg2 . ' > ' . arg3 . eq
endfunction

Is that the file that you are referring to or should I write a .vimrc file with
the following?

filetype plugin on
set shellslash
set grepprg=grep\ -nH\ $*
filetype indent on

Please help me 

Regards,


-D-

______________________________________________________________________
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/unmonitor.php?forum_id=173627

[Vim-latex-devel] pdflatex fails when acrord32 is open

[marc <gm...@au...>]

When running pdflatex, if the resulting document is already open in 
Adobe Reader, then the compilation stops. This is a known problem with 
Adobe Reader which locks .pdf files for writing.

Producing a hack to close Adobe Reader is easy enough, but it's no use 
to me, because I always have multiple documents open.

This problem was solved years ago by WinEdt, albeit via DDE, so I'm 
surprised to see it with the latex suite. Is there a known fix? Thanks.

-- 
Best,
Marc

Re: [Vim-latex-devel] Problem with \cite and \ref completion under Windows

[Ricardo <rv...@gm...>]

Hi Hooman,

I don't know how to make grep work with Vim in XP but I have a setting in my
_vimrc file that instructs Vim to use the internal grep (I believe that this
is available only in Vim 7). The command is "set grepprg=internal". The
grepprg may give you the answers you need: "help grepprg".

ric


On 7/16/06, coupled cores <cou...@gm...> wrote:
>
> Hi List,
>
> I have installed a copy of GNU grep for in windows XP and it is
> working fine. I have installed it in a directory which doesn't have
> any spaces in its name and it is in the %PATH% variable. I can run
> grep from command line.
>
> The problem is that when I try to use F9 to complete my \ref and \cite
> commands, a new window called ___OUTLINE___ is opened and in there it
> is said that:
>
> 'E:/Program' is not recognized as an internal or external command,
> operable program or batch file.
>
> I don't know where to start to look for the roots of this problem. Has
> anybody experienced such a problem? Any solutions?
>
> Thansk,
>
> Hooman
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] .tex files without \documentclass \begin{document} and \end{document} aren't recognised as latex sources

[Ricardo <rv...@gm...>]

Hi Mark,

I believe that this has to do with Vim and not with latex-suite. Whenever
Vim loads an empty .tex file it will set the filetype as plaintex. In your
case you want the filetype as latex or tex. To solve this simple add to your
.tex files the line "%&latex" without the quotes to the beggining of the
file. This will instruct Vim to treate the file as latex and load the
latex-suite. FYI, I'm using Vim 7.

The Vim command "help ft-tex-plugin" will give you a little more info. Also
try "help filetype".

ric


On 7/15/06, Mark Gesing <mag...@gm...> wrote:
>
> Hi,
>
> I am in the habit of splitting my latex sources into several files so that
> the source is easier to manage.
>
> How can I set up the suite so that all files with filenames ending in
> *.tex enable the vim-latex suite? Currently only the document containing
> \documentclass{article}, \begin{document} and \end{document} gets recognized
> as a latex source.
>
> I have a feeling that this is the way it is supposed to work anyhow since
> in the tutorial the vim-latex menus are supposed to be available after ":e
> newfile.tex"
> (in my case the menus did not come up until I added
> \documentclass{article} \begin{document} \end{document} )
>
> Thank you very much.
>
> Mark.
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>
>
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>
>

[Vim-latex-devel] Problem with \cite and \ref completion under Windows

[coupled c. <cou...@gm...>]

Hi List,

I have installed a copy of GNU grep for in windows XP and it is
working fine. I have installed it in a directory which doesn't have
any spaces in its name and it is in the %PATH% variable. I can run
grep from command line.

The problem is that when I try to use F9 to complete my \ref and \cite
commands, a new window called ___OUTLINE___ is opened and in there it
is said that:

'E:/Program' is not recognized as an internal or external command,
operable program or batch file.

I don't know where to start to look for the roots of this problem. Has
anybody experienced such a problem? Any solutions?

Thansk,

Hooman

Re: [Vim-latex-devel] .tex files without \documentclass \begin{document} and \end{document} aren't recognised as latex sources

[Aditya M. <ad...@ii...>]

On Sat, 15 Jul 2006, Mark Gesing wrote:

> Hi,
>
> I am in the habit of splitting my latex sources into several files so that
> the source is easier to manage.
>
> How can I set up the suite so that all files with filenames ending in *.tex
> enable the vim-latex suite? Currently only the document containing
> \documentclass{article}, \begin{document} and \end{document} gets recognized
> as a latex source.
>
> I have a feeling that this is the way it is supposed to work anyhow since in
> the tutorial the vim-latex menus are supposed to be available after ":e
> newfile.tex"
> (in my case the menus did not come up until I added \documentclass{article}
> \begin{document} \end{document} )

It seems that your file is not being recognized as a latex file. Are 
you using vim7? What is the output of
:set ft?
(question mark is part of the command)

Try adding

let g:tex_flavor = "latex"

to your .vimrc


Aditya

[Vim-latex-devel] .tex files without \documentclass \begin{document} and \end{document} aren't recognised as latex sources

[Mark G. <mag...@gm...>]

Hi,

I am in the habit of splitting my latex sources into several files so that
the source is easier to manage.

How can I set up the suite so that all files with filenames ending in *.tex
enable the vim-latex suite? Currently only the document containing
\documentclass{article}, \begin{document} and \end{document} gets recognized
as a latex source.

I have a feeling that this is the way it is supposed to work anyhow since in
the tutorial the vim-latex menus are supposed to be available after ":e
newfile.tex"
(in my case the menus did not come up until I added \documentclass{article}
\begin{document} \end{document} )

Thank you very much.

Mark.

[Vim-latex-devel] Vim7: issues with quickfixing

[Tobias W. <to...@gm...>]

[I composed in HTML because of line breaking, sorry]

I’m using VIM-Latex with Vim7 and pdflatex 1.4.0 beta. I noticed that
quickfixing is not optimal because the parsing of the log output fails
in several regards.

The first is that the log is formatted to wrap at column 79. Often the
input line number of a warning is after a line break when the warning
message is too long.
I found that Tex allows to adjust the line length in texmf.cnf but then
the layout of the log is messed up to the effect that the file names to
which the warnings belong are not matched anymore.

Here is what I experience:

--- 79 columns, full log attached ----

[23] [24 <./fig/res-seg-a1.png> <./fig/res-seg-b1.png>
<./fig/res-seg-a2.pdf> <
./fig/res-seg-b2.pdf> <./fig/res-seg-a3.png> <./fig/res-seg-b3.png>])
(./chapters/sults.tex [25]
Chapter 2.

Package natbib Warning: Citation `popolvuh' on page 26 undefined on
input line 
3.


LaTeX Warning: Reference `sec:stage2' on page 26 undefined on input line
44.

----

As you can see the line number is not on the line of the warning and
breaks the errorformat pattern when the log is wrapped at column 79.

--- Column 87, full log attached ----

[23] [24 <./fig/res-seg-a1.png> <./fig/res-seg-b1.png>
<./fig/res-seg-a2.pdf> <./fig/re
s-seg-b2.pdf> <./fig/res-seg-a3.png> <./fig/res-seg-b3.png>])
(./chapters/sults.tex
[25]
Chapter 2.

Package natbib Warning: Citation `popolvuh' on page 26 undefined on
input line 3.


LaTeX Warning: Reference `sec:stage2' on page 26 undefined on input line
44.

----

Now, the line number is matched as %l but the file
name ./chapters/sults.tex is not where the efm expects it. The result is
that the warning in the quickfix window is with a line number but
without the file name.

The second issue is that – as you could see above – packages often have
their own warnings, which are not matched by the errorformat in
vim-latex. I managed to add "Package %.%# Warning" to the pattern. I
think this is enough.

The third issue is that a lot of stuff is given in the quickfix window
that doesn’t make sense – i.e., there are many lines with empty ||
addresses. Is it supposed to look like that or is my install messed up
in any way?
Here’s what it looks like:

---

|| (/usr/share/texmf-tetex/tex/latex/base/size12.clo
|| (/usr/share/texmf-tetex/tex/latex/setspace/setspace.sty
|| (/usr/share/texmf-tetex/tex/latex/base/fontenc.sty
|| 0 = TS1 (full)
|| (/usr/share/texmf-tetex/tex/latex/amsfonts/amssymb.sty
|| (./chapters/titlepage.tex
/home/towolf/Spine/spine.aux|| LaTeX Warning: Label `fig:strereo'
multiply defined.
|| Package microtype Warning: Unknown slot number of character
|| Package microtype Warning: Unknown slot number of character
|| (./spine.toc)
|| (./chapters/meth.tex [4
|| LaTeX Warning: Reference `sec:method-survey' on page 5 undefined on
input line
|58 warning| LaTeX Warning: Reference `sec-corpus' on page 6 undefined
on input line 58.
|| Package natbib Warning: Citation `Golub2004' on page 6 undefined on
input line
|386 warning| LaTeX Warning: Reference `sec.res-dec' on page 14
undefined on input line 386.
|| LaTeX Warning: Reference `sec.res-complexity' on page 15 undefined on
input lin
|500 warning| LaTeX Warning: Reference `fig.strata' on page 16 undefined
on input line 500.
|746 warning| LaTeX Warning: Float too large for page by 15.13017pt on
input line 746.
sults.tex|| Package natbib Warning: Citation `popolvuh' on page 26
undefined on input line
sults.tex|44 warning| LaTeX Warning: Reference `sec:stage2' on page 26
undefined on input line 44.
sults.tex|53 warning| LaTeX Warning: Reference `sec:stage3' on page 27
undefined on input line 53.
sults.tex|143 warning| LaTeX Warning: Float too large for page by
14.4069pt on input line 143.
|| Package natbib Warning: There were undefined citations.
|| LaTeX Warning: There were undefined references.
|| LaTeX Warning: There were multiply-defined labels.
||
 
---

My approach would be to keep the longer output lines and adjust the efm
so it catches the file names again. Any thoughts on that plan?

- Tobias

[Vim-latex-devel] Fwd: pdflatex problem

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

---------- Forwarded message ----------
From: Javier Rojas <jer...@gm...>
Date: Jul 10, 2006 11:12 AM
Subject: Re: [Vim-latex-devel] pdflatex problem
To: andrew <and...@gm...>



On 7/9/06, andrew <and...@gm...> wrote:
>
> Hi,
>
> I have a problem with pdflatex. Whenever I use \ll to compile the tex
> file to pdf, I get a list of "errors" in the quickfix window. But it
> is actually a list of sty files of some of the packages I used in the
> tex file. For example:
>
> /tmp/v504866/6|| (/usr/share/texmf-tetex/tex/latex/subfigure/subfigure.sty
> /tmp/v504866/6|| (/usr/share/texmf-tetex/tex/latex/amsfonts/umsa.fd)

I am sure there is no error in the tex file except some underfull or
> overfull boxes...
> This is very annoying. Compiling using the dvi rule has no problem.


Are you using eps figures? if so, convert them to jpg or pdf

convert fig.eps fig.jpg
or
epstopdf fig.eps

will do the trick on linux. remember that you can't use eps figures with
pdflatex. If the error keeps appearing, send the error messages to the list

Re: [Vim-latex-devel] Defining a new command in a vim-latex suite

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

On 7/10/06, ahmet nurlu <ahm...@ya...> wrote:
>
> Hi,
> I define a  new command  in a preamble  such as:
>
> \newcommand{\be}{\begin{equation}}
> \newcommand{\ee}{\end{equation}}
>
> When I start a new display equation like below:
>
> \be
> A^{ij} B_{ij}
> \ee
>
> Vim-Latex suite thinks that I wrote someting in math in text mode and puts
> some red blocks on subscripts and superscripts to warn me.
>
> How could I overcome this problem that the Vim-Latex suite accepts my
> definition for  a display math equation.
>

I think the only way to solve this issue would be to modify your latex
syntax file. It would be ask too much to latexsuite to wait that it could
search the definition and change the syntax higlightinng accordingly.

Sorry, no other thing that I can think about it

Javier Rojas

[Vim-latex-devel] Defining a new command in a vim-latex suite

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

Hi,
I define a  new command  in a preamble  such as:

\newcommand{\be}{\begin{equation}}
\newcommand{\ee}{\end{equation}}

When I start a new display equation like below:

\be
A^{ij} B_{ij}
\ee

Vim-Latex suite thinks that I wrote someting in math in text mode and puts some red blocks on subscripts and superscripts to warn me. 

How could I overcome this problem that the Vim-Latex suite accepts my definition for  a display math equation.

thanks,
Ahmet Nurlu


 		
---------------------------------
Do you Yahoo!?
 Everyone is raving about the  all-new Yahoo! Mail Beta.

[Vim-latex-devel] pdflatex problem

[andrew <and...@gm...>]

Hi,

I have a problem with pdflatex. Whenever I use \ll to compile the tex
file to pdf, I get a list of "errors" in the quickfix window. But it
is actually a list of sty files of some of the packages I used in the
tex file. For example:

/tmp/v504866/6|| (/usr/share/texmf-tetex/tex/latex/subfigure/subfigure.sty
/tmp/v504866/6|| (/usr/share/texmf-tetex/tex/latex/amsfonts/umsa.fd)

I am sure there is no error in the tex file except some underfull or
overfull boxes...
This is very annoying. Compiling using the dvi rule has no problem.
How can I solve this problem? BTW, the ignore level is set to 7 by
default...

-- 
andrew

Re: [Vim-latex-devel] Adobe Acrobat 7.0 (Full version) with Vim-LaTeX

[coupled c. <cou...@gm...>]

SGkgVmFpZG90YXMsCgpQbGVhc2UgYWNjZXB0IG15IGFwb2xvZ2llcyBpZiBJIGFtIGFza2luZyBz
dHVwaWQgcXVlc3Rpb25zLiBJIHN0aWxsCmNhbid0IG1ha2UgbXkgTGFUZVgtU3VpdGUgdG8gY2Fs
bCBBZG9iZSBBY3JvYmF0IFJlYWRlciB0byB2aWV3IG15IHBkZgpmaWxlcy4gTXkgdGV4cmMgZmls
ZSBpcyBpbiB0ZXggZm9sZGVyIGFuZCBhdCBhIGNvbW1hbmQgcHJvbXB0IEkgY2FuCnNheSBDOlw+
c3RhcnQgYWNyb3JkMzIgYW5kIEkgb3BlbiB0aGUgQWNyb2JhdC4gQnV0IHdoZW4gSSBpc3N1ZSB0
aGUKY29tbWFuZCBmcm9tIHdpdGhpbiB2aW06Cjohc3RhcnQgYWNyb3JkMzIKSSByZWNlaXZlIGFu
IGVycm9yIG1lc3NhZ2UuIEkgZ2V0IHN1Y2Nlc3Mgd2l0aAo6ISBzdGFydCBhY3JvcmQzMgpidXQg
dGhlIGNvbW1hbmQgd2luZG93IHJlbWFpbnMgb3BlbiB1bnRpbCBJIGhpdCBFbnRlci4KCkkgYWxz
byBkaWRuJ3QgZ2V0IHlvdXIgY29tbWVudCBvbiB0aGUgZGVidWcgZmlsZS4gV2hlcmUgc2hvdWxk
IEkgcHV0CnRoaXMgbGluZT8gQ291bGQgeW91IHBsZWFzZSBnaXZlIG1lIHNvbWUgbW9yZSBoaW50
cz8gSSByZWFsbHkKYXBwcmVjaWF0ZSB0aGF0LgoKSGF2ZSBhIGdvb2QgdGltZSwKCkhvb21hbgoK
T24gNi8xMS8wNiwgVmFpZG90YXMgWmVtbHlzIDx6ZW1seXNAZ21haWwuY29tPiB3cm90ZToKPiBI
aSwKPiDQdCwgMjAwNiAwNiAxMCAwMjoyNiAtMDQwMCwgY291cGxlZCBjb3JlcyByYfDrOgo+ID4g
SGksCj4gPgo+ID4gSSBhbSB1c2luZyBWaW0gNy4wIHVuZGVyIFdpbmRvd3MgWFAgYW5kIEkgaGF2
ZSBpbnN0YWxsZWQgVmltLUxhVGVYIG9uCj4gPiB0b3Agb2YgaXQuIE9uZSBwcm9ibGVtIHRoYXQg
SSBoYXZlIGlzIG5vdCBiZWluZyBhYmxlIHRvIHZpZXcgUERGCj4gPiBvdXRwdXQgb2YgbXkgdGV4
IGZpbGVzLiBJIGhhdmUgQWRvYmUgQWNyb2JhdCA3LjAgKGZ1bGwgdmVyc2lvbikgYW5kCj4gPiBh
ZnRlciBJIGNvbXBpbGUgbXkgZmlsZSB0byBQREYgdGFyZ2V0LCB0aGUgUERGIGZpbGUgaXMgZ2Vu
ZXJhdGVkLCBidXQKPiA+IGlzc3VpbmcgXGx2IGNvbW1hbmQgZG9lc24ndCBkbyBhbnl0aGluZy4K
PiA+Cj4gPiBDb3VsZCB5b3UgcGxlYXNlIGdpdmUgbWUgc29tZSBoZWxwIHRvIHJlc29sdmUgdGhp
cyBpc3NzdWU/Cj4gPgo+Cj4gTG9vayBhdCB5b3VyIHRleHJjIGZpbGUuIFRoZXJlIHNob3VsZCBi
ZSBhIGNvbmZpZ3VyYXRpb24gb3B0aW9uIGZvciB3aGF0Cj4gbGF0ZXhzdWl0ZSBjYWxsIHdoZW4g
dmlld2luZyBwZGZzLiBUcnkgZmluZGluZyBvdXQgd2hhdCBpcyB0aGUgbmFtZSBvZgo+IEFjcm9i
YXQgUmVhZGVyIGJpbmFyeSAoc2hvdWxkIGJlIHNvbWV0aGluZyBsaWtlIGFjcm9yZWFkLmV4ZSBv
cgo+IGFjcm9yZDMyLmV4ZSkgYW5kIGFkZCBpdHMgbG9jYXRpb24gdG8gUEFUSC4gRm9yIGRlYnVn
Z2luZyBwdXJwb3NlcyB5b3UKPiBjYW4gc2V0IHRoZSBsb2cgZmlsZSBhcyBkZXNyaWJlZCBpbiBt
eSBlYXJsaWVyIG1lc3NhZ2U6Cj4gaHR0cDovL3NvdXJjZWZvcmdlLm5ldC9tYWlsYXJjaGl2ZS9t
ZXNzYWdlLnBocD9tc2dfaWQ9MTcwMjY3NTMKPgo+IFZhaWRvdGFzCj4KPgo=

Re: [Vim-latex-devel] Adobe Acrobat 7.0 (Full version) with Vim-LaTeX

[Vaidotas Z. <ze...@gm...>]

Hi,
Št, 2006 06 10 02:26 -0400, coupled cores rašė:
> Hi,
> 
> I am using Vim 7.0 under Windows XP and I have installed Vim-LaTeX on
> top of it. One problem that I have is not being able to view PDF
> output of my tex files. I have Adobe Acrobat 7.0 (full version) and
> after I compile my file to PDF target, the PDF file is generated, but
> issuing \lv command doesn't do anything.
> 
> Could you please give me some help to resolve this isssue?
> 

Look at your texrc file. There should be a configuration option for what
latexsuite call when viewing pdfs. Try finding out what is the name of
Acrobat Reader binary (should be something like acroread.exe or
acrord32.exe) and add its location to PATH. For debugging purposes you
can set the log file as desribed in my earlier message:
http://sourceforge.net/mailarchive/message.php?msg_id=17026753

Vaidotas

[Vim-latex-devel] Adobe Acrobat 7.0 (Full version) with Vim-LaTeX

[coupled c. <cou...@gm...>]

Hi,

I am using Vim 7.0 under Windows XP and I have installed Vim-LaTeX on
top of it. One problem that I have is not being able to view PDF
output of my tex files. I have Adobe Acrobat 7.0 (full version) and
after I compile my file to PDF target, the PDF file is generated, but
issuing \lv command doesn't do anything.

Could you please give me some help to resolve this isssue?

Thanks,

-Hooman
P.S. I am a newbie to Vim.

Re: [Vim-latex-devel] Vim 7 Problem

[Norvell S. <nor...@gm...>]

Someone on the list told me to try setting the filetype manually and
that fixed the problem.  I dug around and found that a setting can be
made in the .vimrc or _vimrc file to get around setting the filetype
every time:

https://sourceforge.net/tracker/?func=detail&aid=1503673&group_id=52322&atid=466456

-- 
Norvell Spearman

[Vim-latex-devel] Using vim with TexShop

[Jeremy C. <jer...@gm...>]

Has anyone used vim/gvim as an external editor for TeXShop?  I have
configured TeXShop to be used with an external editor and also to
automatically update the preview, but I'm not sure if gvim and TeXShop
are communicating.  Any ideas?
Thanks,
Jeremy

[Vim-latex-devel] Vim 7 Problem

[Norvell S. <nor...@gm...>]

I'm using vim7 for win32 (the pre-built binary from vim.org) and
installed vim-latex according to the directions.  When I started the
tutorial and typed

    :e newfile.tex

I didn't get any LaTeX-related menus.  I saw this post from 10 May:

http://sourceforge.net/mailarchive/forum.php?thread_id=10313998&forum_id=12952

but I couldn't find any files named vimrc_tex that may be getting
sourced too deeply -- and didn't see anything in the installation
instructions about having to add a source command.  Am I missing
something painfully obvious?

Thanks.

-- 
Norvell Spearman

Re: [Vim-latex-devel] bug in F9 fill in

[Thomas G. <Tho...@st...>]

At a guess are you sure there is a definitions.tex, if there is is it using
correct path in the \input or \include.  I had errors when including 
files that
were not present and thus it spits out an error.  I added a correction to
outline.py (posted here earlier) that checks if there is a file and hopefully
doesnt crash so easily.

Tom

Quoting Josh Guffin <gu...@ui...>:

>
> When trying to use <F9> to fill in a \ref, vim-latex barfed while
> attempting to read a file which is in one of my ~/.texmf/...
> directories (definitions.tex).  i would fix it, but i don't speak
> python. here is the error:
>
>
> ----------------------------------------
> Traceback (most recent call last):
>   File "/Users/guffin/.vim/ftplugin/latex-suite/outline.py", line
> 183, in ?
>     print main(sys.argv[1], prefix)
>   File "/Users/guffin/.vim/ftplugin/latex-suite/outline.py", line
> 170, in main
>     contents = getFileContents(root, ext)
>   File "/Users/guffin/.vim/ftplugin/latex-suite/outline.py", line
> 27, in getFileContents
>     contents = re.sub(pat, lambda input: getFileContents(input,
> ext), contents)
>   File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
> python2.3/sre.py", line 143, in sub
>     return _compile(pattern, 0).sub(repl, string, count)
>   File "/Users/guffin/.vim/ftplugin/latex-suite/outline.py", line
> 27, in <lambda>
>     contents = re.sub(pat, lambda input: getFileContents(input,
> ext), contents)
>   File "/Users/guffin/.vim/ftplugin/latex-suite/outline.py", line
> 23, in getFileContents
>     contents = '\n'.join(open(fname).read().splitlines())
> IOError: [Errno 2] No such file or directory: 'definitions.tex'
> ----------------------------------------
>
>
> thanks
>
> josh
>
>
>
>
>
>
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] bug in F9 fill in

[Josh G. <gu...@ui...>]

When trying to use <F9> to fill in a \ref, vim-latex barfed while  
attempting to read a file which is in one of my ~/.texmf/...  
directories (definitions.tex).  i would fix it, but i don't speak  
python. here is the error:


----------------------------------------
Traceback (most recent call last):
   File "/Users/guffin/.vim/ftplugin/latex-suite/outline.py", line  
183, in ?
     print main(sys.argv[1], prefix)
   File "/Users/guffin/.vim/ftplugin/latex-suite/outline.py", line  
170, in main
     contents = getFileContents(root, ext)
   File "/Users/guffin/.vim/ftplugin/latex-suite/outline.py", line  
27, in getFileContents
     contents = re.sub(pat, lambda input: getFileContents(input,  
ext), contents)
   File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/sre.py", line 143, in sub
     return _compile(pattern, 0).sub(repl, string, count)
   File "/Users/guffin/.vim/ftplugin/latex-suite/outline.py", line  
27, in <lambda>
     contents = re.sub(pat, lambda input: getFileContents(input,  
ext), contents)
   File "/Users/guffin/.vim/ftplugin/latex-suite/outline.py", line  
23, in getFileContents
     contents = '\n'.join(open(fname).read().splitlines())
IOError: [Errno 2] No such file or directory: 'definitions.tex'
----------------------------------------


thanks

josh

Re: [Vim-latex-devel] kdvi and latex-suite

[Vaidotas Z. <ze...@gm...>]

Št, 2006 06 03 16:31 +0200, Knut Birger Lunde rašė:
> Hi, latex-suite is really great!
> However I can not make viewLatex \lv and forward search \ls work with  
> kdvi, by setting:
> let g:Tex_ViewRule_dvi = 'kdvi'.
> Des anyone have a solution for this problem?

At least in my texrc  I have

if has('win32')
	TexLet g:Tex_ViewRule_ps = 'gsview32'
	TexLet g:Tex_ViewRule_pdf = 'AcroRd32'
	TexLet g:Tex_ViewRule_dvi = 'yap -1'
elseif has('macunix')
	" Let the system pick.  If you want, you can override the choice here.
	TexLet g:Tex_ViewRule_ps = 'ggv'
	TexLet g:Tex_ViewRule_pdf = 'evince'
	" TexLet g:Tex_ViewRule_pdf = 'Acrobat\ Reader\ 5.1'
	TexLet g:Tex_ViewRule_dvi = 'xdvi'
else
	TexLet g:Tex_ViewRule_ps = 'ggv'
	TexLet g:Tex_ViewRule_pdf = 'evince'
	TexLet g:Tex_ViewRule_dvi = 'xdvi'

I remember that I had to explicitly set the same option for macunix and
else in order for my settings to work. That would be the first thing to
look at. The second would be to check the location of texrc file. Maybe
you have two copies both in ftplugin/tex and ftplugin/latex-suite. The
correct place is the first one. It is written in comments at the
beginning of the texrc file. If this does not help, use the debugging
file. Set 

TexLet g:Tex_DebugLog = '/home/mpiktas/tmp/lsuite.debug'

with apropriate file of course. Reload the latex-suite and try \lv. In
the debug file you will see what is happening. 

Good luck!

Vaidotas

Re: [Vim-latex-devel] kdvi and latex-suite

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

On Saturday 03 June 2006 16:31, Knut Birger Lunde wrote:
> Hi, latex-suite is really great!
> However I can not make viewLatex \lv and forward search \ls work with
> kdvi, by setting:
> let g:Tex_ViewRule_dvi = 'kdvi'.
> Des anyone have a solution for this problem?
> Thanks in advance

Hi,

does viewing a file with "kdvi file.dvi" work? If it does not work, then kdvi 
does not accept command-line prameters and it's not latex-suite's fault. If 
it works, then I can't help you either.

[Vim-latex-devel] kdvi and latex-suite

[Knut B. L. <knu...@nt...>]

Hi, latex-suite is really great!
However I can not make viewLatex \lv and forward search \ls work with  =

kdvi, by setting:
let g:Tex_ViewRule_dvi =3D 'kdvi'.
Des anyone have a solution for this problem?
Thanks in advance
-- =

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/