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

[Vim-latex-devel] [Contact] Inserting references

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

Hi All,



Just found the latex-suite and tried my hands on it. 



i was going 
through the tutorial, and when found some inconsistancies, couldnt really 
figureout what was happening:



1) eqnarray + F5



i get the eqn template 
as



\\begin{eqnarray}

    \\label{}<++>

\\end{eqnarray}<++>



After 
inserting the label eqn:something and <c-j>,

and then the eqn how do i get past the 
last <++>. 

i did the usual <c-j> after the equation so it was 
like



\\begin{eqnarray}

   1 + 1 = 2

   
label{eqn:something}

\\end{eqnarray}



and now when i try the reference 
addition, like



This is a \\ref{} and press F9, i get the window split, and after an 
<enter>, the reference changes to



\\ref{\\begin{equation}:something 
\\end{equation}}.



Am i missing something?



With warm 
regards



karthik



PS: i accidently posted the previous mail, hence the 
incomplete mail  

[Vim-latex-devel] [Contact] Inserting references

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

Hi All,



Just found the latex-suite and tried my hands on it. 



i was going 
through the tutorial, and when found some inconsistancies, couldnt really 
figureout what was happening:



1) eqnarray + F5



i get the eqn template 
as



\\begin{eqnarray}

    \\label[]<++>

\\end{eqnarray}<++>



After 
inserting the label eqn:something and <c-j>,

and then the eqn how do i get past the 
last <++>. 

i did the usual <c-j> after the equation so it was 
like



\\begin{eqnarray}



\\end{eqnarray}  

[Vim-latex-devel] bibtex problem

[Brian K. <bk...@gm...>]

OK, I'm having the same problem with bibtex after having upgraded to
the development version

Brian

On Wed, 30 Jun 2004 13:26:45 -0700, Ryan Krauss
<vim-latex-devel-form@so...> wrote:
>
>
> I recently started using Vim Latex-Suite and I really like it.  I
am having a problem
> though.  When I run Latex, Bibtex is not always running.  I went
into windows explorer
> and deleted all the extra files latex makes to see if I could force
is to run bibtex, and
> it is not even generating a bbl file.  Is there an easy to force a
Bibtex run?  I thought
> about writing a simple script to simply run a shell command to call
bibtex with the
> current file name, but I don\"t know how to send the current file
name to a script (and I
> couldn\"t easily find out how to do this from the help menus).
>
> Please help.
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit http://www.blackhat.com
> _______________________________________________
> Vim-latex-devel mailing list
> Vim-latex-devel@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] kdvi forward search

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

On Wed, 30 Jun 2004, Brian Keats wrote:

> For some reason, kdvi forward search wouldn't work for me, even though
> viewing did. It works fine for xdvi though.
>
> My hack was to change the 'else' cases to the kdvi execute string from
> the Tex_ViewLaTeX() function as follows:
>
I am afraid I don't understand what the problem was precisely and how
this is supposed to fix it...

It seems that if you have

let g:Tex_UseEditorSettingInDVIViewer = 1
let g:Tex_ViewRule_dvi = 'kdvi'

in your texrc then latex-suite will issue

silent! !kdvi --unique file:foo.dvi\#src:12file.tex &

when you press \ls. Which should be what you want to happen...

Isn't it?

Srinath

Re: [Vim-latex-devel] [Contact] Bibtex problem

[Brian K. <bk...@gm...>]

I'm assuming that you have the line \bibliography{bib_file} in your
tex file. It works for me.

Brian

On Wed, 30 Jun 2004 13:26:45 -0700, Ryan Krauss
<vim...@so...valid> wrote:
> 
> 
> I recently started using Vim Latex-Suite and I really like it.  I am having a problem
> though.  When I run Latex, Bibtex is not always running.  I went into windows explorer
> and deleted all the extra files latex makes to see if I could force is to run bibtex, and
> it is not even generating a bbl file.  Is there an easy to force a Bibtex run?  I thought
> about writing a simple script to simply run a shell command to call bibtex with the
> current file name, but I don\'t know how to send the current file name to a script (and I
> couldn\'t easily find out how to do this from the help menus).
> 
> Please help.
> 
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 


-- 
Brian Keats M.A.Sc.
University of Waterloo
CEIT 3104
519.888.4567 x7257
bri...@ie...

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

[Brian K. <bk...@gm...>]

For some reason with latex-suite, vimspell will only highlight
spelling error inside curly braces {}. In the summary at the bottom it
reports the right number of mispelled words, but ignores most of the
text. Does anyone have any idea where I could start looking to debug
this?

-- 
Brian Keats M.A.Sc.
University of Waterloo
CEIT 3104
519.888.4567 x7257
bri...@ie...

Re: [Vim-latex-devel] \\ll don\'t work

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

Hi.

* On Tue, Jun 29, 2004 at 04:13:39AM -0700, taquang <vim...@so...valid> wrote:
> I got vim-latex from debian testing. While invoking latex from menu
> tex-suite -> compile worked perfectly, using the short cut \\ll
> didn\'t seem to work. The docu stated that one has to \"press \\ll\"
> in normal mode but as far as I see, nothing happened. Is that a
> problem with mapleader? 

Just \ll, not \\ll

> How can I change the \"mapleader\"?

    :h mapleader

Your .vimrc in a good place to change this value.

> Another question: Is there a way, ie shortcut, to change the color of
> the latex\'s keywords to the same color of the background? I `don'\'t
> mean rip off the latex\'s keywods, but just \"hide\" them.

I think it is possible with something like:
    hi Statement guifg=white guibg=white

-> :h hi

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

[Vim-latex-devel] [Contact] Bibtex problem

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

I recently started using Vim Latex-Suite and I really like it.  I am having a problem 
though.  When I run Latex, Bibtex is not always running.  I went into windows explorer 
and deleted all the extra files latex makes to see if I could force is to run bibtex, and 
it is not even generating a bbl file.  Is there an easy to force a Bibtex run?  I thought 
about writing a simple script to simply run a shell command to call bibtex with the 
current file name, but I don\'t know how to send the current file name to a script (and I 
couldn\'t easily find out how to do this from the help menus).



Please help.  

[Vim-latex-devel] kdvi forward search

[Brian K. <bk...@gm...>]

For some reason, kdvi forward search wouldn't work for me, even though
viewing did. It works fine for xdvi though.

My hack was to change the 'else' cases to the kdvi execute string from
the Tex_ViewLaTeX() function as follows:

    if Tex_GetVarValue('Tex_UseEditorSettingInDVIViewer') == 1 &&

    ...

    elseif Tex_GetVarValue('Tex_UseEditorSettingInDVIViewer') == 1 &&
viewer == "kdvi"

      let execString = 'silent! !kdvi --unique
file:'.mainfnameRoot.'.dvi\#src:'.line('.').expand("%").' &'

    else

      let execString = 'silent! !kdvi --unique
file:'.mainfnameRoot.'.dvi\#src:'.line('.').expand("%").' &'

    endif

__________________

      if Tex_GetVarValue('Tex_UseEditorSettingInDVIViewer') == 1 &&
      ....
      elseif Tex_GetVarValue('Tex_UseEditorSettingInDVIViewer') == 1 &&
            \ s:viewer == "kdvi"
        let execString = 'silent! !kdvi --unique '.mainfname.'.dvi &'
      else
        let execString = 'silent! !kdvi --unique '.mainfname.'.dvi &'
      endif

-- 
Brian Keats M.A.Sc.
University of Waterloo
CEIT 3104
519.888.4567 x7257
bri...@ie...

[Vim-latex-devel] [Contact] \\ll don\'t work

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

Hi,

I got vim-latex from debian testing. While invoking latex from menu tex-suite 
-> compile worked perfectly, using the short cut \\ll didn\'t seem to work. The docu 
stated that one has to \"press \\ll\" in normal mode but as far as I see, nothing 
happened. Is that a problem with mapleader? How can I change the 
\"mapleader\"?

Another question: Is there a way, ie shortcut, to change the color 
of the latex\'s keywords to the same color of the background? I don\'t mean rip off the 
latex\'s keywods, but just \"hide\" them.

Thank you very much.

Taquang  

[Vim-latex-devel] [Contact] Where should I set g:Tex_CompileRule_dvi

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

I\'m going to

    let g:Tex_CompileRule_dvi = \'tex $*\'



I put the command in 
_vimrc, but it doesn\'t work.



Where I should put this command.  

Re: [Vim-latex-devel] problems with referencing, compiling. Windows 2000.

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

On Thu, 24 Jun 2004, Ian Langmore wrote:

> My setup:
> Windows 2000, SP4.  VIM version 6.3 compiled June 7.  Latex suite 1.5.

Actually, due to time constraints I have not updated latex-suite 1.5 in
quite a while. I have been meaning to update the download page and
remove that release, but never find the time. I always keep telling
myself that I'll do it "tomorrow" but never get around to it.

Download the latest dev version of latex-suite instead. It should be
significantly more stable. I fixed quite a few problems with
file-names-with-spaces which affect the windows platform, so you might
get lucky. The latest dev version is below the 1.5 release on the
download page. The download instructions are common for both.

> Basic problem:  I was going through the tutorial.  Everything worked fine
> until the section on inserting a reference.  Step 7 suggests writing
> (\ref{}) and hitting F9 between {}.  When I hit F9 a small DOS window
> briefly pops up on the taskbar, VIM starts to do something (happens very
> fast), and then nothing.  It should be noted that at first I had F9 mapped

Did you install a working `grep` program for your computer? The windows
'findstr' which is used by default is not good enough for latex-suite.
My personal setup is windows+cygwin and cygwin contains the grep
command, but I am sure you'll find a standalone grep.exe somewhere on
the web. I have been meaning to test a few etc but again not much
time...

Try opening a small file with the word "foo" in it and then type:

:grep -nH foo %

from within vim in normal mode. After that finishes, type:

:cwindow

If it works (i.e you get a quickfix window with the matches), then we'll
proceed further.

> Next problem:  I went on to the compile section of the tutorial, and when I
> hit \ll  VIM sputtered again, but no .dvi file was made anywhere.   The
> compile GUI command gives the same results.

It looks like you might not have the latex.exe file in the windows path.
On windows, go to:

Control Panel > System > Advanced > Environment Variables

And modify the PATH variable to include the directory in which latex.exe
resides.

> 1.	When I try the "echo" command, I get
> latex -interaction=nonstopmode $*
> I am unsure what command to try and execute.  I tried typing \input but
> after hitting "i" vim went into insert mode.

I meant trying to make your OS execute the above command from within vim. Basically
type the following sequence of letters in vim while in normal mode

:!latex -interaction=nonstopmode %

NOTE: The initial : is necessary to go into vim's "command mode". The
      '!' makes vim pass the subsequent string to the OS.

> 2.	:set makeprg does give the same result
> 3.	Gives the E117 Unknown function: Tex_RunLaTeX().   But I am using the
> most current version available!  I am not using a bash shell.

Thats because you are using latex-suite 1.5. Use the 2004-06-13 version
instead.

http://vim-latex.sourceforge.net/download/latexSuite20040613.zip

> P.S.  If this thing gets working I promise to give $20 to the orphans.
> Seriously.

Cool!

Srinath

[Vim-latex-devel] [Contact] Problems with multiple compiling

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

Hi there,



I just updtated to Vim 6.3 (from 6.2) and updated MiKTeX on my PC (WinXP).  
I did a clean install of latex-suite as well, but kept my previous texrc file.  However, 
now whenever I compile with \'\\ll\' it will only run latex and bibtex once, and then 
the prompt:



\'Hit ENTER or type command to continue\' 



will appear.  It 
doesn\'t seem to compile multiple times automatically.  Previously, under 6.2, the 
multiple compilation worked fine. 



As I\'ve kept my texrc file that was working on 
the previous version, I really don\'t know what to change or do apart from compiling it 
multiple times manually.  Has anyone else had similar problems?  Or is there something 
really obvious I\'m missing?  Thanks.



jiun.  

[Vim-latex-devel] problems with referencing, compiling. Windows 2000.

[Ian L. <ila...@uc...>]

Hello I have just installed the VIM-Latex suite.  This was a fresh install
of VIM and the Latex suite so everything is up to date.  I do have some
previous VIM experience.  I encountered a problem (described below), and
un-installed VIM, then reinstalled everything.

My setup:
Windows 2000, SP4.  VIM version 6.3 compiled June 7.  Latex suite 1.5.

Basic problem:  I was going through the tutorial.  Everything worked fine
until the section on inserting a reference.  Step 7 suggests writing
(\ref{}) and hitting F9 between {}.  When I hit F9 a small DOS window
briefly pops up on the taskbar, VIM starts to do something (happens very
fast), and then nothing.  It should be noted that at first I had F9 mapped
to another program shorcut.  I unmapped it and then did the re-install, so I
don't think that is the problem any more.  Note that :map <F9> gives "No
mapping found" as a reply.

Next problem:  I went on to the compile section of the tutorial, and when I
hit \ll  VIM sputtered again, but no .dvi file was made anywhere.   The
compile GUI command gives the same results.

I followed the "here" link for suggestions about compiling problems.
http://vim-latex.sourceforge.net/documentation/latex-suite/latex-compiling.h
tml


Suggestion #
1.	When I try the "echo" command, I get
latex -interaction=nonstopmode $*
I am unsure what command to try and execute.  I tried typing \input but
after hitting "i" vim went into insert mode.
tex.vim does not exist in my ftplugin directory, but bibtex.vim does exist
in my ftplugin/latex-suite directory.

2.	:set makeprg does give the same result
3.	Gives the E117 Unknown function: Tex_RunLaTeX().   But I am using the
most current version available!  I am not using a bash shell.

Thanks a lot to anyone who can help.
-Ian

P.S.  If this thing gets working I promise to give $20 to the orphans.
Seriously.

[Vim-latex-devel] [Contact] ltags modification

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

Hi,



I just discovered the latex-suite today and have been playing around for it 
for a while now. I noticed that the ltags script as-is only honors one level of 
inclusion, which was not sufficient for me.



Thus, I created a new version which 
now recurses into arbitrary levels of inclusion. Cycles are detected and 
skipped.



I\'m writing this via the web mail form at vim-latex.sourceforge.net. 
If you\'re interested, please let me know how I can contribute the script.



Best 
regards and thanks for latex-suite,



Christoph Schmitz <cs...@cs...>  

Re: [Vim-latex-devel] View document in another directory

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

* On Sat, Jun 19, 2004 at 05:05:18PM +0200, Luc Hermitte <her...@fr...> wrote:
> Thanks! So far it works fine.

Actually, there is one problem line 239 of compiler.vim.
On Windows, the extension is no more used while it is required --
AcroRd32 complains now.
    
The line 
    :let execString = 'start '.s:viewer.' "$*.'.s:target.'"'
seems to fix the problem


Regarding the log file, vim should not complain when the file has
changed. In order to fix this, I've added the following hack into one
tex-ftplugin:
    augroup autoreadLog
      au!
      au BufReadPost *.log :setlocal autoread |:setlocal nomodifiable
    aug END
but I guess there is a simplier and less invasive solution.


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

Re: [Vim-latex-devel] View document in another directory

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

Hi.

* On Fri, Jun 18, 2004 at 05:55:34PM -0700, Srinath Avadhanula <srinath@f=
astmail.fm> wrote:
> I have followed your previous idea of just creating an imitation of
> vim's native :make utility. For now, we just substitute $* with the
> main file name, but in the future it could be as general purpose as
> vim's own.

Thanks! So far it works fine.

BTW, I'm testing the files on the CVS (v1.69 IIRC).
I have not set Tex_ViewRule_html, but Tex_ViewRuleComplete_html.
And =AB:TTarget html=BB gives me the following error:
    =ABNo View rule defined for target html
     Please specify a rule in texrc.vim
         :help Tex_CompileRule_format
     for more information.=BB

Where I see the following problems:
- I think we should not get any error message in this case
- the file to modify is not texrc.vim but texrc
- as the help for Tex_CompileRule_format does not say that a view rule
  must be specified, shouldn't the error message point to
  Tex_ViewRule_format ?


--=20
Luc Hermitte
http://hermitte.free.fr/vim/

Re: [Vim-latex-devel] View document in another directory

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

On Sat, 19 Jun 2004, Luc Hermitte wrote:

> * On Fri, Jun 18, 2004 at 04:58:55PM -0700, Srinath Avadhanula <sr...@fa...> wrote:
> > Actually you can make it work with !start too. Here's a little demo:
> >
> > Open vim (not necessarily with latex-suite activated) and do:
> >   let &mp = 'start gvim $*'
> >   silent! make! %
> > you will need gvim.exe to be in your windows $PATH of course. You should
> > see another instance of gvim startup and attempt to reread the file....
>
> I though of this solution, but it does not indicate us if the file is
> not found, and neither v:shell_error nor :copen are of any help [1]. And
> even more important:
>     let &makeprg='AcroRd32 $*.pdf'
>     silent make foo
> works, but
>     let &makeprg='start AcroRd32 $*.pdf'
>     silent make foo
> does not.
>

Yes. You're right... I have followed your previous idea of just creating
an imitation of vim's native :make utility. For now, we just substitute
$* with the main file name, but in the future it could be as general
purpose as vim's own.

Srinath

Re: [Vim-latex-devel] View document in another directory

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

* On Fri, Jun 18, 2004 at 04:58:55PM -0700, Srinath Avadhanula <srinath@f=
astmail.fm> wrote:
> Actually you can make it work with !start too. Here's a little demo:
>=20
> Open vim (not necessarily with latex-suite activated) and do:
>   let &mp =3D 'start gvim $*'
>   silent! make! %
> you will need gvim.exe to be in your windows $PATH of course. You shoul=
d
> see another instance of gvim startup and attempt to reread the file....

I though of this solution, but it does not indicate us if the file is
not found, and neither v:shell_error nor :copen are of any help [1]. And
even more important:
    let &makeprg=3D'AcroRd32 $*.pdf'  =20
    silent make foo
works, but=20
    let &makeprg=3D'start AcroRd32 $*.pdf'  =20
    silent make foo
does not.

AcroRd32 seems to receive an incorrect filename in the latter case.


[1] This issue is raised by:
    :let &mp=3D'start! cygstart incorrectpath/$*.html'
    :silent! make foo
    And by extension, if the file to view has not been generated yet,
    \lv would not even tell us there is nothing to view.
    Without =ABstart=BB, the error can be retrieved with :copen
--=20
Luc Hermitte
http://hermitte.free.fr/vim/

Re: [Vim-latex-devel] View document in another directory

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

On Sat, 19 Jun 2004, Luc Hermitte wrote:

> * On Fri, Jun 18, 2004 at 03:38:16PM -0700, Srinath Avadhanula <sr...@fa...> wrote:
> > This way you could have set Tex_ViewRule_html to something like
> >     :let Tex_ViewRule_html = '!start cygstart html/$*.html'
> > and have things work OOTB.
>
> That's neat. But a bit problematic.
> While this works perfectly with cygstart (because this program forks),
> it can not be used with start (execution error) which would be required
> with programs that do not fork like AcroRd32 -- I've just made some
> experiments.

Actually you can make it work with !start too. Here's a little demo:

Open vim (not necessarily with latex-suite activated) and do:

let &mp = 'start gvim $*'
silent! make! %

you will need gvim.exe to be in your windows $PATH of course. You should
see another instance of gvim startup and attempt to reread the file....

The silent! is necessary because vim tries to redirect the output of
"!start gvim file" to some temp file and then parse it for errors.
Without the "silent!" it gives an error that the temp file cannot be
opened.

I got carried away and have already implemented this in CVS.

> It seems we will need our own make-like command. Its only work beeing to
> substitute $* by the name of the result of the compilation.
> In the long run, it can even be extended to support custom formats like
> %pwd, %line, %col, ...
>
As of right now, I have made it substitute the substring
'{v:servername}' in &mp with v:servername. We could extend it to
something like:

    :function! Eval(expr)
    :    exec 'return '.a:expr
    :endfunction
    :let mp = substitute(&mp, '{\(.\{-}\)}', '\=Eval(submatch(1))', 'g')

>
> > > [Request: option for the preview window]
> > This should also be an easy thing to modify. I'll put it on the TODO.
>

This is also done in CVS. Should be uploading shortly.

Srinath

Re: [Vim-latex-devel] View document in another directory

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

* On Fri, Jun 18, 2004 at 03:38:16PM -0700, Srinath Avadhanula <sr...@fa...> wrote:
> > I'm trying to configure g:Tex_ViewRule_html.
> > The situation is that into the current directory I have a file
> > foo.tex and that I use TeX4HT to generate several HTML pages into
> > the subdirectory ./html/
> [...]
> But I think it would have been better to use the strategy for
> Tex_CompileRule_dvi. Basically something like:
>     :let _mp = &mp
>     :let &mp = Tex_ViewRule_dvi
>     :exec 'make '.mainfname
> 
> This way you could have set Tex_ViewRule_html to something like
>     :let Tex_ViewRule_html = '!start cygstart html/$*.html'
> and have things work OOTB.

That's neat. But a bit problematic.
While this works perfectly with cygstart (because this program forks),
it can not be used with start (execution error) which would be required
with programs that do not fork like AcroRd32 -- I've just made some
experiments.

It seems we will need our own make-like command. Its only work beeing to
substitute $* by the name of the result of the compilation.
In the long run, it can even be extended to support custom formats like
%pwd, %line, %col, ...

> Maybe have a seperate setting in addition to Tex_ViewRule_html?
> Something like Tex_ViewRuleComplete_html which if exists takes
> precedence over Tex_ViewRule_html?

Having both approaches to maintain may require more work than necessary.
However, it present the avantage to be more easy to upgrade LaTeXSuite
for end-users.

Moreover, I do not think the complete rule must unhide details like how
the viewer is launched into the background

> [...]
> As a hack in the while it takes me to modify latex-suite, why don't
> you make a little scriptlet which calls cygstart the way you want it
> to?  It would be a solution for the time being... Something like
>     #!/usr/bin/bash
>     cygstart $PWD/html/$*

Indeed. Thanks! (I should have though of it ... a few hours ago I wrote
a wrapper for gvim in order to add "--servername=LATEX" when gvim is
launched with (La)TeX files as parameters.)

> > [Request: option for the preview window]
> This should also be an easy thing to modify. I'll put it on the TODO.

Thanks.

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

Re: [Vim-latex-devel] View document in another directory

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

On Fri, 18 Jun 2004, Luc Hermitte wrote:

> I'm trying to configure g:Tex_ViewRule_html.
> The situation is that into the current directory I have a file foo.tex
> and that I use TeX4HT to generate several HTML pages into
> the subdirectory ./html/
>

Okay, this seems like a reasonable thing to want latex-suite to do by
default. I just looked at compiler.vim and it turns out that I use
something like:

    :let execString =3D '!start '.s:viewer.' "'.mainfname.'.'.s:target.'"'
    :exec execString

(here s:viewer =3D Tex_ViewRule_html and s:target =3D 'html')

But I think it would have been better to use the strategy for
Tex_CompileRule_dvi. Basically something like:

    :let _mp =3D &mp
    :let &mp =3D Tex_ViewRule_dvi
    :exec 'make '.mainfname


This way you could have set Tex_ViewRule_html to something like

    :let Tex_ViewRule_html =3D '!start cygstart html/$*.html'

and have things work OOTB.

Maybe have a seperate setting in addition to Tex_ViewRule_html? Something
like Tex_ViewRuleComplete_html which if exists takes precedence over
Tex_ViewRule_html?


> Playing with cygstart, I found out that =AB$PWD/html=BB was the argument =
I
> was looking for.
> Unfortunatelly, while
>     :!cygstart $PWD/html/ "foo.html"
> works very well,
>     :!start cygstart $PWD/html/ "foo.html"
> does not. :(
>
As a hack in the while it takes me to modify latex-suite, why don't you
make a little scriptlet which calls cygstart the way you want it to?
It would be a solution for the time being... Something like

#!/usr/bin/bash

cygstart $PWD/html/$*


and then point Tex_ViewRule_html to it...

> BTW, I have a request: I'd like an option to disable the default opening
> of the preview windows as the quickfix windows is enough for me 99% of
> the time.
>

This should also be an easy thing to modify. I'll put it on the TODO.

--=20
Srinath

[Vim-latex-devel] View document in another directory

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

Hello,

I'm trying to configure g:Tex_ViewRule_html.
The situation is that into the current directory I have a file foo.tex
and that I use TeX4HT to generate several HTML pages into
the subdirectory ./html/

My first attempt (Win32-vim + cygwin on Windows XP) was to define this
option to: 'cygstart html/'
Unfortunatelly, LaTeXSuite inserts a space just after
g:Tex_ViewRule_html, and thus tries to execute:
    :!start cygstart html/ "foo.html"
(It would have been the same with iexplorer)

Then, I read the man page of cygstart and found out about the =AB-d=BB
option. Unfortunatelly
    $>cygstart -d html foo.html
result in IE trying to open http://html/foo.html. Definitivelly not what
I expected.

Playing with cygstart, I found out that =AB$PWD/html=BB was the argument =
I
was looking for.
Unfortunatelly, while
    :!cygstart $PWD/html/ "foo.html"
works very well,
    :!start cygstart $PWD/html/ "foo.html"
does not. :(


Does anybody know a way to configure g:Tex_ViewRule_html to open the
file ./html/foo.html ?


BTW, I have a request: I'd like an option to disable the default opening
of the preview windows as the quickfix windows is enough for me 99% of
the time.

--=20
Luc Hermitte
http://hermitte.free.fr/vim/

[Vim-latex-devel] TMacro

[Jan U. H. <jan...@we...>]

Hi,

I am using latexSuite20040613.

When I type ":TMacro example"

this line gets inserted:

<---- Latex Suite End Macro ----

and not the example macro

juh

Re: [Vim-latex-devel] First steps with LS (at last)

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

* On Wed, Jun 16, 2004 at 09:38:38PM -0700, Srinath Avadhanula <srinath@f=
astmail.fm> wrote:
> Hmm... This does look like it might be a better way of doing things.
> The thing which confuses me is why vim is not doing
>     :runtime! compiler/tex.vim
> automatically when you open a tex file even though we have "filetype
> plugin on". Does vim only do:
>     :runtime! ftplugin/tex.vim
> when you open a tex file?!=20

More or less yes.=20
(-> :runtime! ftplugin/tex.vim ftplugin/tex_*.vim ftplugin/tex/*.vim)

> (I am surprised I didn't know this already if its true) Its not
> mentioned anywhere in the docs that you have to manually source the
> compiler ftplugin IIRC.

They are not compiler ftplugin, but just compiler plugins IIRC.

And vim can not know which ones must be sourced. The typical example is
with C++ code. Vim can not guess if we are using VC++, BCB, DM C/C++,
GCC, Open Watcom, ... Which means we can not have it automatically load
any compiler plugin.

(La)TeX is a special case as every (La)TeX compilers use the same &efm.
Hence we can have only one compiler/tex.vim which is common to
(fpTeX\|MiKTeX\|...)::(pdf(La)TeX\|(La)TeX\|...)

It is not the same with the other languages.

> > If t63 is loaded first, then tls will override the definitions that
> > need to be overriden, and LaTeXSuite will ignore the other ones I
> > guess. If tls is loaded first, then it can set =ABcurrent_compiler=BB
> > which will abort the sourcing of t63.
>=20
> ... I guess that if I have latex-suite's compiler/tex.vim NOT finish
> even if 'current_compiler' exists and set it to 'latex' when it does
> get sourced, then it will handle both cases. Have to check this a bit
> thoroughly.=20

I think so. Moreover, this is what is said at the end of
    :h write-compiler-plugin

Otherwise, it seems it is already the case as =AB:compiler tex=BB fixes t=
he
problem AFAIC -- when LaTeXSuite is at the end of 'runtimepath'.

--=20
Luc Hermitte
http://hermitte.free.fr/vim/