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

Re: [Vim-latex-devel] Opening file with acrord in windows

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

On Wed, 19 May 2004, Aditya Mahajan wrote:

>   It turns out that the error occurs because acrobat reader does not
> recognize the directory from which it was launched. This is easy to
> see. CD to a directory having a pdf file, say test.pdf and on command
> prompt type
> acrord32 file.pdf

This is pretty strange. On my system (windows XP + Adobe Acrobat Reader
5.0), if I have the reader open (but without the file) and if I issue
a command like

    AcroRd32 file.pdf

from a command prompt after cd'ing to the directory containing the file,
Acrobat does correctly launch the file...

> Note that I have changed "%:p:t:r" to "%:p:r" so that mainfname points
> to the complete path of the file.
>
> Now \lv calls
>   :!start Acrord32 "complete_path_to_file/file.pdf"
> and the file shows correctly. Also the filename is surrounded with
> quotes, so everything should be fine.
>

Unfortunately, there are a LOT of issues when doing this. For one,
enclosing the file name in quotes doesn't work on some systems when the
the actual shell command is interpreted by bash or similar which quotes
the command... Escaping on the other hand works in *nix but not on
windows...

I cannot trivially make this change without making tests on other
systems...

Srinath

[Vim-latex-devel] Opening file with acrord in windows

[Aditya M. <adi...@al...>]

Hi,
  In windows, there is a problem re-viewing the pdf file in Acrord. To 
reproduce this problem, write a sample latex code, set output format 
to pdf (:TTarget pdf) and compile the file. Then open the file by \lv
Acrobat Reader is launched and the file shows correctly. Now close the 
file in Acrobat Reader (Do not close the reader!) and from within vim, 
try viewing the file again by \lv. Acrobat gives an error saying 
"There is an error opening the document, the file could not be found"

  It turns out that the error occurs because acrobat reader does not 
recognize the directory from which it was launched. This is easy to 
see. CD to a directory having a pdf file, say test.pdf and on command 
prompt type
acrord32 file.pdf

Acrobat Reader will give the same error. It can locate the file if the 
complete file path is mentioned. So one needs to modify 
latex-suite/compiler.vim as follows

259: let mainfname = Tex_GetMainFileName(':p:r')
262: let mainfname = expand("%:p:r")

Note that I have changed "%:p:t:r" to "%:p:r" so that mainfname points 
to the complete path of the file.

Now \lv calls
  :!start Acrord32 "complete_path_to_file/file.pdf"
and the file shows correctly. Also the filename is surrounded with 
quotes, so everything should be fine.

Aditya

-- 
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008

Re: [Vim-latex-devel] Trying to understand the quickfix-window

[David E. <es...@fa...>]

I just discovered a way to make this work, although it doesn't seem like
this is supposed to be what I do based on the manual.

let g:Tex_FormatDependency_ps = 'dvi,ps'
let g:Tex_DefaultTargetFormat = 'ps'

doesn't work right. But if I change the TargetFormat to dvi,ps
everything works fine. So whether or not that is configuration I can
deal with it.

Thanks,
David


On Mon, 2004-05-17 at 22:11 -0700, Srinath Avadhanula wrote:
> On Mon, 17 May 2004, David Escott wrote:
> 
> > I am trying to understand the quickfix-window and I am a little confused
> > by what is happening. I use gvim almost exclusively and I would prefer
> > to use that (don't know if that makes any difference).
> 
> vim/gvim should behave the same in this regard.
> 
> 
> > So anyways I have a tex file with known errors. If is ps (dvi->ps) it
> > doesn't show errors. With the mode dvi it shows the errors correctly. Is
> 
> This is not supposed to happen. If there are errors in the dvi step,
> then latex-suite should interrupt the build process.
> 
> I very recently (yesterday or so) made a few fixes to this part of
> latex-suite when I noticed something similar. Download the very latest
> version and retry. If you still get this behavior, then do the
> following:
> 
> Put
>     let g:Tex_Debug = 1
> in your ~/.vim/ftplugin/tex.vim file and then redo the compilation. Then
> tell me what
>     :call Tex_PrintDebug('comp')
> says.
> 
> Srinath
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
-- 
David Wright Escott

Re: [Vim-latex-devel] Trying to understand the quickfix-window

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

On Mon, 17 May 2004, David Escott wrote:

> I am trying to understand the quickfix-window and I am a little confused
> by what is happening. I use gvim almost exclusively and I would prefer
> to use that (don't know if that makes any difference).

vim/gvim should behave the same in this regard.


> So anyways I have a tex file with known errors. If is ps (dvi->ps) it
> doesn't show errors. With the mode dvi it shows the errors correctly. Is

This is not supposed to happen. If there are errors in the dvi step,
then latex-suite should interrupt the build process.

I very recently (yesterday or so) made a few fixes to this part of
latex-suite when I noticed something similar. Download the very latest
version and retry. If you still get this behavior, then do the
following:

Put
    let g:Tex_Debug = 1
in your ~/.vim/ftplugin/tex.vim file and then redo the compilation. Then
tell me what
    :call Tex_PrintDebug('comp')
says.

Srinath

[Vim-latex-devel] Trying to understand the quickfix-window

[David E. <es...@fa...>]

I am trying to understand the quickfix-window and I am a little confused
by what is happening. I use gvim almost exclusively and I would prefer
to use that (don't know if that makes any difference).

So anyways I have a tex file with known errors. If is ps (dvi->ps) it
doesn't show errors. With the mode dvi it shows the errors correctly. Is
this expected? Does the error list not work unless the mode is dvi? I
prefer usually to view it as ps since I find it more asthetically
pleasing, but if there is no work around I may go back to dvi. 

Thanks,
David
-- 
David Wright Escott

Re: [Vim-latex-devel] [Contact] Completion problems

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

On Mon, 10 May 2004, Vaidotas Zemlys wrote:

> > As of now, latex-suite tries to complete the \ref command from \label's
> > found in *all* .tex files in the directory of the file being edited. If
> > you put all the .tex files of a project in the same directory, then you
> > should be all set.
> >
>
> Is this a configurable option? I would like that latexsuite tried to complete
> \ref command only in edited file, not all the files in the directory. Is this
> possible?
>
I just changed the viewing function so that now latex-suite will
complete \ref's from \label's found in the main file in which the
current file is \include'd and all the the \include'd files therein.
Basically, if you have

main.tex
    \input{file1}
    \input{file2}

Then if you are editing file1.tex, latex-suite searches for labels in
main.tex, file1.tex and file2.tex.

This means that if you have multiple .tex files in the same directory
but they are not part of a master file, then \label's will be searched
for each file individually.

Srinath

[Vim-latex-devel] [Contact] grep.exe -nH $*

[Milan B. <vim...@so...>]

Solving the problem with grep.exe for win32.



grep and <F9> work under Linux 
without problem, but using windows I could not get any output (any windows with 
offer).



I found grep.exe which has the totally same output as the GNU grep (I use 
diff to found differences, if any).



What could be a  solution? Please!  

Re: [Vim-latex-devel] irritating interaction between vim-latex, pstricks and errors

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

On Tue, 11 May 2004, David Escott wrote:

> Dear vim-latex
>
> I'm having the most incredibly annoying interaction between pstricks and
> vim-latex.
>
[snip]
> let g:Tex_IgnoredWarnings = 0

This is where the problem is. Tex_IgnoredWarnings is supposed to be
a "\n" delimited list of patterns which latex-suite will ignore when it
parses the latex output. See

http://vim-latex.sourceforge.net/documentation/latex-suite/compiler-customization.html#Tex_IgnoredWarnings

I think you meant to set g:Tex_IgnoreLevel to zero. With your sample
file and with this problem setting removed, I get the error in the
sample file itself, i.e, the cursor doesn't jump to multido.sty.

Try it out and let me know. In trying to figure out this error, I fixed
a small problem in latex-suite. Try the latest release.

Srinath

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

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

On Wed, 12 May 2004, Brian Keats wrote:

> The changelog for the latest development version says that kdvi is now
> supported. I tried "let g:Tex_ViewRule_dvi = 'kdvi'", but I still end up with
> xdvi for viewing. Does anyone have this working?
>
I cannot reproduce this. For me, if I set g:Tex_ViewRule_dvi = 'kdvi',
kdvi pops up as expected. Are you using the correct version?

Srinath

[Vim-latex-devel] (no subject)

[Brian K. <bf...@en...>]

The changelog for the latest development version says that kdvi is now
supported. I tried "let g:Tex_ViewRule_dvi = 'kdvi'", but I still end up with
xdvi for viewing. Does anyone have this working?

Brian Keats




----------------------------------------
This mail sent through www.mywaterloo.ca

Re: [Vim-latex-devel] irritating interaction between vim-latex, pstricks and errors

[Luc H. <her...@fr...>]

Hello,

* On Tue, May 11, 2004 at 02:39:49PM -0400, David Escott <es...@fa...> wrote:
> Problem: Compiling a file with an error, and \usepackage{pst-all} causes
> the current buffer to be closed and a new buffer with the following text
> opened:

Did you have a look at vim's option: switchbuf ?
I had such problems with :make and C++ programs. I obtain the less worse
behaviour with:
    set switchbuf=useopen
And now I read the documentation again, I wonder if 
    set switchbuf=useopen,split 
is not what I was lookging for...

HTH,
-- 
Luc Hermitte
http://hermitte.free.fr/vim/

[Vim-latex-devel] [Contact] abbreviations not working with vim-latexsuite

[Jens K. <vim...@so...>]

Hi,



I use vim-latexsuite and have also set some abbreviations in vim. Whenever I 
want to use them it doesn\'t work. I can view all ab\'s with \":ab\". AFAIS it happens 
with an empty vimrc also.



Best regards



Jens  

[Vim-latex-devel] irritating interaction between vim-latex, pstricks and errors

[David E. <es...@fa...>]

Dear vim-latex

I'm having the most incredibly annoying interaction between pstricks and
vim-latex. 

Problem: Compiling a file with an error, and \usepackage{pst-all} causes
the current buffer to be closed and a new buffer with the following text
opened:

\ProvidesPackage{multido}[1997/03/25 package wrapper for multido.tex]
\input multido.tex
\endinput

Steps to reproduce: 

Compiling the following file will cause this to occur.

\documentclass[12pt]{article}
\usepackage{pst-all}
\begin{document}
  \begin{center}
    \begin{center}

      Joe
    \end{center}
%comment
\end{document}

This is a very subtle bug both the whitespace line, the extra
\begin{center}, and the %comment are needed to make this happen.

In the past I have noticed that in situations where the file which
compiles cleanly (ie no problem using \ll in vim) but which has an
overfull \hbox has a really nasty behavior.

Introducing an error like the one above will cause the buffer to be
closed and the multido buffer opened. Moreover correcting that error
WILL NOT fix the problem with \ll. The problem persists until the
overfull \hbox is fixed.

I was unable to reproduce that here.

Finally I have had  trouble with errors in general during compile. The
documentation states that: 

...This runs latex on the current file and displays the errors in a
|quickfix-window| below the file being edited. You can then scroll
through the errors and press <enter> to be taken to the location of the
corresponding error. Along with the errors being listed in the quickfix
window, the corresponding log file is also opened in |preview| mode
beneath the quickfix window. It is scrolled automatically to keep in
sync with the error being viewed in the quickfix window. You will be
automatically taken to the location of the first error/warning unless
you set the g:Tex_GotoError variable to 0...

Which has *never* worked for me (I use gVIM exclusively, but I gather it
might work on the console, although the pstricks problem  still there).
At best I had the program jumping to the line of the error, but it
wouldn't tell me what the error was-- which was irritating enough to
cause me to let g:Tex_GotoError=0.

If anyone has any hints or knows something I might be doing wrong I
would really appreciate it. I'm really tempted to throw my fist through
the monitor everytime I have to reopen the file.

Thanks David

A few tidbits that may be of use, let me know if there is anything else
of relevance:

My texrc is:

let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
let g:Tex_FormatDependency_ps = 'dvi,ps'
let g:Tex_DefaultTargetFormat = 'ps'
set grepprg=grep\ -nH\ $*
set sw=2
set iskeyword+=:
let g:Tex_ViewRule_ps = 'ggv'
let g:Tex_FoldedEnvironments = 'pspicture,'
let g:Imap_UsePlaceHolders = 0
let g:Tex_IgnoredWarnings = 0

gvim --version

VIM - Vi IMproved 6.2 (2003 Jun 1, compiled May  9 2004 21:07:16)
Included patches: 1-517
Compiled by escott@localhost
Huge version with GTK2 GUI.  Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments
+cryptv +cscope +dialog_con_gui +diff +digraphs +dnd -ebcdic +emacs_tags +eval
+ex_extra +extra_search +farsi +file_in_path +find_in_path +folding -footer
+fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap
 +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession
+modify_fname +mouse +mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm
+mouse_netterm +mouse_xterm +multi_byte +multi_lang +netbeans_intg -osfiletype
+path_extra +perl +postscript +printer +python +quickfix +rightleft -ruby
+scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax
+tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse
+textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual
+visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup
+X11 -xfontset +xim +xsmp_interact +xterm_clipboard -xterm_save
   system vimrc file: "/etc/vim/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "/etc/vim/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/X11R6/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include     -O3 -march=athlon-xp -funroll-loops -pipe  -I/usr/X11R6/include  -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -I/usr/lib/perl5/5.8.4/i686-linux/CORE  -I/usr/include/python2.3 -pthread
Linking: gcc  -L/usr/X11R6/lib   -rdynamic   -L/usr/local/lib -o gvim   -Wl,--export-dynamic -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0   -lXt -lncurses -lgpm -rdynamic  -L/usr/local/lib /usr/lib/perl5/5.8.4/i686-linux/auto/DynaLoader/DynaLoader.a -L/usr/lib/perl5/5.8.4/i686-linux/CORE -lperl -lutil -lc -L/usr/lib/python2.3/config -lpython2.3 -lpthread -lutil -lm -Xlinker -export-dynamic

I use Gentoo so this is compiled locally, and I have version 2.02 of the teTeX distribution.

-- 
David Wright Escott

Re: [Vim-latex-devel] [Contact] Completion problems

[Vaidotas Z. <v.z...@po...>]

Hi,

> > I will finish by a small feature request: the completion for
> > \"\\ref{}\" only proposes references that were declared in the same
> > file. It would be great if the choice was globally over all the latex
> > project (ie if it was possible to reference to labels declared in
> > another file).
> >
> As of now, latex-suite tries to complete the \ref command from \label's
> found in *all* .tex files in the directory of the file being edited. If
> you put all the .tex files of a project in the same directory, then you
> should be all set.
>

Is this a configurable option? I would like that latexsuite tried to comple=
te =20
\ref command only in edited file, not all the files in the directory. Is th=
is =20
possible?

The main.vim file in ftplugin/latex-suite directory tells me that its versi=
on =20
is 1.46 and it was modified last time in 2003/08/29

Mpiktas

Mpiktas

Re: [Vim-latex-devel] [Contact] :TTarget pdf/dvi

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

On Sun, 9 May 2004, Sebastian Menge wrote:

> I just tried to map the command \":TTarget pdf\" to <F8> using
>
> :map <F8>
> :TTarget pdf <return>
>

It looks like you have a spurious space. It should be

map <F8> :TTarget pdf<return>

NOT

map <F8> :TTarget pdf <return>

Or a little shorter:

map <F8> :TTarget pdf<CR>

HTH
Srinath

PS: Since you are not subscribed to this list, further replies from you
to this list will be silently ignored. If you want to continue this
thread, please subscribe.

[Vim-latex-devel] [Contact] :TTarget pdf/dvi

[Sebastian M. <vim...@so...>]

Hi!



I just tried to map the command \":TTarget pdf\" to <F8> using 



:map <F8> 
:TTarget pdf <return>



When pressing <F8> i get the following error (sorry for 
german messages)



> Fehler beim Ausführen von \"function

> 
SetTeXTarget..Tex_SetTeXCompilerTarget\":

> Zeile   19:

> E121: Variable 
nicht definiert: g:Tex_CompileRule_pdf

> E116: Unzulässige Argumente für 
Funktion

> escape(g:Tex_CompileRule_{target}, g:Te

> x_EscapeChars)

> 
E15: ungültiger Ausdruck:  escape(g:Tex_CompileRule_{target},

> 
g:Tex_EscapeChars)



What am I doing wrong?



regards, Sebastian.  

Re: [Vim-latex-devel] [Contact] Completion problems

[Julien U. <22...@st...>]

On Mon, 10 May 2004 09:10 am, Srinath Avadhanula wrote:

> > 1) The completion for \\cite{} is not working anymore in the main file (I
> > get an empty buffer instead of the list of choices)
>
> This is a bug which needs to be fixed. 

After doing a "diff" between the stable version and the latest CVS version I 
found out where the problem was: 
I replaced line 536 of texviewer.vim:
 	"exec "silent! grepadd ".Tex_EscapeForGrep('@.*{'.a:prefix)." %"
by
 	exec "silent! grepadd '".Tex_EscapeForGrep('@.*{'.a:prefix)."' %"
(the older version present in the 1.5 release), and it solved my problem.

Here are the debug messages in case you still need them:
**************************************************
s:type = cite, typeoption = 
calling Tex_GrepForBibItems
searching for bibkeys in main.tex (buffer #1)
found bibliography command in main.tex
trying to search through [file1]
silent! find file1.bib
finding .bib file [file1.bib]
using pattern @.*{
+Tex_SetupCWindow
+Tex_SyncPreviewWindow
*********************************************************

> This should tell us what latex-suite is trying to do. In addition, if
> you can give an idea of how your files are arranged, that will be great.

The completion wasn't working even with this test file:
***************main.tex*****************
\documentclass[a4paper]{book}
\begin{document}
\cite{}
\bibliography{file1}
\end{document}
****************************************

> > 2) The mapping <F9> does not work any more in the included files
> > (opened with \"gf\" in vim).
>
> This bug has been fixed in the latest CVS.

It was still not working for me, although all I had to do was to add an imap 
in my "tex.vim". My files are arranged in the following way:

main directory:
main.tex
main.tex.latexmain
mystyle.sty
  | Part 1
	Chapter1.tex
	Chapter2.tex
  |Part 2
	etc...
  |Biblio
	file1.bib
	file2.bib
	etc...

Thanks for your quick answer and your help

Julien

Re: [Vim-latex-devel] [Contact] Completion problems

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

On Sun, 9 May 2004, Julien wrote:

> 1) The completion for \\cite{} is not working anymore in the main file (I
> get an empty buffer instead of the list of choices)
>

This is a bug which needs to be fixed. Can you do the following:

1. Put
    let Tex_Debug = 1
   in your ~/.vim/ftplugin/tex.vim

2. Try the \cite{} completion again. After the empty quick-fix window
   appears, type
    silent! redir @a | call Tex_PrintDebug('view') | redir END

3. Open a temporary buffer and insert the contents of register a into
   it. (with "ap)

This should tell us what latex-suite is trying to do. In addition, if
you can give an idea of how your files are arranged, that will be great.

> 2) The mapping <F9> does not work any more in the included files
> (opened with \"gf\" in vim).
>

This bug has been fixed in the latest CVS.

> I will finish by a small feature request: the completion for
> \"\\ref{}\" only proposes references that were declared in the same
> file. It would be great if the choice was globally over all the latex
> project (ie if it was possible to reference to labels declared in
> another file).
>
As of now, latex-suite tries to complete the \ref command from \label's
found in *all* .tex files in the directory of the file being edited. If
you put all the .tex files of a project in the same directory, then you
should be all set.

Otherwise, latex-suite currently doesn't complete \label's for all .tex
files in the project. This is a useful thing to have, which I'll put on
the TODO list.

-- 
Srinath

[Vim-latex-devel] [Contact] Completion problems

[Julien <vim...@so...>]

Hi, 



I am a happy user of LaTeX Suite with gvim 6.2 on linux, but I have a problem with 
included files. 

With the stable version 1.5, I was not able to compile from an 
included file when this file was in a subdirectory. In this mailing list I found and 
followed the advice of installing the unstable  version.

This did solve my 
compiling problem, however with this unstable version (20040315), I met some other 
problems:

1) The completion for \\cite{} is not working anymore in the main file (I 
get an empty buffer instead of the list of choices)

2) The mapping <F9> does not work 
any more in the included files (opened with \"gf\" in vim).



I solved (2) by moving 
\"latex-suite/texviewer.vim\" to \"tex/texviewer.vim\", but was unable to find a 
solution for (1). Being an intensive user of this mapping, I came back to the stable 
version waiting for a solution. Is there anything I am doing wrong, or that I can do to 
solve this problem?



I will finish by a small feature request: the completion for 
\"\\ref{}\" only proposes references that were declared in the same file. It would be 
great if the choice was globally over all the latex project (ie if it was possible to 
reference to labels declared in another file). 



Thanks a lot for the good work, 
this package is highly addictive...



Julien  

Re: [Vim-latex-devel] [Contact] Vim-Latex Compiling and Viewing help !

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

On Wed, 5 May 2004 vim...@so...valid wrote:

> let g:Tex_CompileRule_dvi = \'latex
> --src-specials  \\input{$*}\' in this file. so now when i do :echo
> Tex_CompileRule_dvi it is printing what is required:
>
> latex --src-specials
> \\input{$*}
>
I suggest using

let g:Tex_CompileRule_dvi = 'latex --src-specials --interaction=nonstopmode $*'

I think this is what the manual suggests... The \\input thing is prone
to shell escape errors.


> I dont understand what is meant by executing on the terminal; in which
> directory; i tried to execute in a couple of directories but it doesnt
> work. It says latex not recognized as internal or external command.
> etc..
>
This is the problem. The directory where latex.exe resides should be
included in your %PATH% settings. In windows, the %PATH% setting is
changed in "Control Panel > System > Advanced > Environement Variables".

> :call RunLaTeX() says unknown function RunLaTeX

This needs to be updated. It should have been Tex_RunLaTeX.

Srinath

[Vim-latex-devel] [Contact] Vim-Latex Compiling and Viewing help !

[<vim...@so...>]

Hi,



I am having a big problem with compiling and running latex. first of all there 
is no .vimrc file there is a _vimrc file and it seems to be working because i used it to 
supress the <<>> marks.



1. I put 

let g:Tex_CompileRule_dvi = \'latex 
--src-specials  \\input{$*}\' in this file. so now when i do :echo 
Tex_CompileRule_dvi it is printing what is required:

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



But that is all; from there on none of the instructions are working as 
they are intended to work. When i try to compile the screen flutters a little bit and 
nothing else ever happens.



I dont understand what is meant by executing on the 
terminal; in which directory; i tried to execute in a couple of directories but it 
doesnt work. It says latex not recognized as internal or external command. 
etc..



:set makeprg? and :verbose set makeprg? result 
in

makeprg=make



:call RunLaTeX() says unknown function RunLaTeX

  

[Vim-latex-devel] folding with autoformatting does not work (Debian bug #246798)

[Artur R. C. <ar...@he...>]

Hello,
Using latexSuite with autoformatting turned on[1] results with the following
formatting:

 \begin{figure}[h]
 \begin{center}\epsfig{file=walkthrough/file-displayed.eps,
 width=3.5in}\end{center} \caption{The file \proxydotc in the Source Code
 Viewer} \label{fig: authoring and browsing annotations}     \end{figure}

Automatic folding does not work in this case - you can check Debian BTS[2]
for details.

Attached patch solves the problem. Please, include it into package.

Cheers
	Artur

[1] :set fo+=a
[2] http://bugs.debian.org/246798
-- 
<Izzunia> co to jest 'nadnocnik' ?
<Falconne> Izzunia: to taki mniejszy supersedes ;)

Re: [Vim-latex-devel] [Contact] Windows Volume/Drive for RunLaTeX

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

On Wed, 21 Apr 2004, Franz Zotter wrote:

> the directory from C: to \"D:/path.../\" it\'s not enough to execute
> \"cd D:/path.../\" on my windows system, obviously it is also takes
> a \"D:\"-command.
>
Thats strange. What version of windows/vim are you using? On recent
windows/vim combinations, doing a simple
    :cd d:/
command from within vim does indeed change the directory to the correct
path. Infact just doing
    :d:/
from within should result in a "E488: Trailing characters" error.
I have a feeling that this might be a problem with spaces in the file
name again. Whats the precise filename you are trying to compile?

Thanks
Srinath

[Vim-latex-devel] [Contact] probs when starting the viewer

[Ulrich V. <vim...@so...>]

Hi,



I am using VIM 6.2 under Windows XP together with latex-suite - thank your very 
much for developing latex-suite !!



When I try to start the viewer with \\lv I get 
the following command in the last line:



:!start windvi c:\\DirectoryName\\ 
withSpace\\filename.dvi

Hit ENTER or type command to continue



Nothing more 
happens!?



I tried the same thing in a directory which name contains no 
space...and everything is fine.



In this case only the filename without the 
pathname is generated i. e. the last line looks like



:!start windvi 
filename.dvi



Have you any hint for me to solve this 
problem?



Regards,



Ulrich

  

[Vim-latex-devel] [Contact] Code-folding of article

[Alf B L. <vim...@so...>]

I use \\part{} in some of my articles, and the code-folding doesn\'t seem to support 
this.