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

[Vim-latex-devel] automatic/remembered TTarget for a directory/project?

[Maciej K. <ma...@dg...>]

Hello,

Is it possible to somehow remember what :TTarget was set to last time
for a given file or project?  I thought that this setting might be
remembered with :mksession, but it isn't.  If there is no way currently,
I would like to nominate this for a feature request.

Example of when the above is useful: I occasionally work on a paper
which specifically requires PDF submission, and thus I will always want
to use pdflatex (i.e., TTarget = pdf) for it, despite generally
preferring dvi.  It would be nice that, whenever I load up the
corresponding .tex file (perhaps by sourcing a session file), the
TTarget was already set correctly.

-- 
Maciej Kalisiak|mac@] "It is better to deserve honours and not have them than
dgp.toronto.edu|www.]  to have them and not deserve them." -- Mark Twain
dgp.toronto.edu/~mac]  

Re: [Vim-latex-devel] New features: compiler, taglist, system-local

[Mikolaj M. <mi...@wp...>]

Dnia Monday 06 of October 2003 22:53, Artur R. Czechowski napisał:
> I am sorry about replying for relatively old mails, but I have a really
> lack of time last days.
>
> On Mon, Sep 29, 2003 at 02:50:31AM +0200, Mikolaj Machowski wrote:
> > Everything is now only in CVS. Tested on Linux. Aha. Name of local
> > directory is made:
> >
> > if has("unix") || has("macunix")
> >     let s:macrodirpath = $HOME."/.vim/ftplugin/latex-suite/macros/"
> > elseif has("win32")
> >     if exists("$HOME")
> >         let s:macrodirpath =
> > $HOME."/vimfiles/ftplugin/latex-suite/macros/" else
> >         let s:macrodirpath =
> > $VIM."/vimfiles/ftplugin/latex-suite/macros/" endif
> > endif
>
> How do you differentiate installation in user directory from system-wide
> installation?
>
Hmm? I don't have to differentiate. lS only checks for particular
files in various directories.

m.

Re: [Vim-latex-devel] New features: compiler, taglist, system-local

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

I am sorry about replying for relatively old mails, but I have a really lack
of time last days.

On Mon, Sep 29, 2003 at 02:50:31AM +0200, Mikolaj Machowski wrote:
> Everything is now only in CVS. Tested on Linux. Aha. Name of local
> directory is made:
> 
> if has("unix") || has("macunix")
>     let s:macrodirpath = $HOME."/.vim/ftplugin/latex-suite/macros/"
> elseif has("win32")
>     if exists("$HOME")
>         let s:macrodirpath = $HOME."/vimfiles/ftplugin/latex-suite/macros/"
>     else
>         let s:macrodirpath = $VIM."/vimfiles/ftplugin/latex-suite/macros/"
>     endif
> endif   
How do you differentiate installation in user directory from system-wide
installation?

Regards
	Artur
-- 
Zyzio pojedzony i wyspany, w temp. 24 stopni Celsjusza, siakieś
500 m n.p.m. to jest jednostka Wredniości i wynosi 1 Wredny Zyzio.
(c) by Zyzio the Wredny, all right and lefts reserved

Re: [Vim-latex-devel] Features like preview-latex

[Mikolaj M. <mi...@wp...>]

Dnia Friday 03 of October 2003 17:55, Aditya Mahajan napisał:
> Please have a look at http://www.angelfire.com/vt2/conceal/
> and http://www.angelfire.com/vt2/conceal/Introduction.html for
> a snapshot. 

This is Vince Negri patch and it will be in Vim 6.3

>
> My question:
>  Is it possible to do something like this in a vim script. This is what
> I think is possible....

I am planning to add this feature when it will be official part of Vim.
This is:
1. Too much work to do when it will be used by small group of people
(how many use unofficial - yet - patches?)
2. I will significantly increase size of LaTeX-Suite.

I am afraid you have to wait for 6.3 + ca. one month to see it in
LaTeX-Suite. Maybe if you could convince Bram to already include this in
patches for Vim 6.2 I would start to work on it but no earlier. But Bram
constantly refuse to add new features currently. Sorry.

m.

Re: [Vim-latex-devel] Features like preview-latex

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

Hi Srinath,

Sep 21  Srinath Avadhanula wrote about Re: [Vim-latex-devel] Features like...

>Hi Aditya,
>
>On Fri, 19 Sep 2003, Aditya Mahajan wrote:
>
>> this package for preview-latex (http://preview-latex.sourceforge.net/) for
>> xemacs, and by the look of it, it looks really impressive.
>>  The main feature that I am concerned about is the ability to display
>> math. I always liked that feature in lyx also. I am wondering, why it can
>> not be done in (g)vim. I think that one could use a unicode encoding for
>> the file and replace \sum by sigma from unicode and go about it. The only
>>
>I must admit preview-latex does sound extremeley impressive and might be
>very useful. But IMHO you underestimate the complexity of rendering
>equations using unicode fonts. Simple things like $x^2 + y^2 = z^2$
>might be fine, because most probably we could just use the singe line
>itself, but with more complex equations where the latex source occupies
>much more space than the equation displayed, things will get very very
>complex indeed.
>
>You will notice that preview-latex actually runs latex and then
>ghostscript to generate the bitmap and then displays that inline in the
>document. I beleive that a project which aims to do something like this
>in native vim script is going to be as complicated as LaTeX itself!
>
>Infact, an easier solution would be to patch VIM itself to allow for
>inline graphics and then use the same route which preview-latex does.
>Ofcourse, having delved into the VIM source only very briefly, I do not
>know if this is even feasible.
>

Please have a look at http://www.angelfire.com/vt2/conceal/
and http://www.angelfire.com/vt2/conceal/Introduction.html for
a snapshot. This is closer to what I had in mind, though I do not like
some of the aspects of the implementation. I think that somethings like
having section headings in bold and using unicode characters to display
greek symbols would be much better. It does not try to render equations,
but is much closer to what I would like to have. But the only trouble is
that is is given as a patch to the original code, but I do not have the
courage to read the entire vim code and try to figure it out.

My question:
 Is it possible to do something like this in a vim script. This is what
I think is possible....
 open a preview window and scrollbind it to the main tex window. This is
exactly what the author of conceal is doing. Make some changes to the
higlight scheme to be used for preview window (how?? the preview window
has no tags!) to have things like bold underline, a different color for
the math mode and replacement of simple math characters (you mentioned
that there was a script that already did this, so that will save some
work) and we have a system where we can preview as we type.

Maybe I am still on a bit of a nostalgia from lyx. I learnt latex
b working on lyx. And I found it amazing. Then I shifted to typing
documents in latex as lyx does not give me as much control as raw latex
does. Also there was the problem of editing in lyx, use the arrow keys,
copy paste, everyhting was too primitive. That is why I shifted to
latex+vim. Now I wonder of (g)vim can give atleast some comparable
viewing.


Cheers
aditya

>Quite frankly, I would not even attempt something this complicated
>myself :(
>
>Also, for simple things like displaying the actual greek character theta
>instead of \theta, the greek Sigma character in place of \sum etc, I
>beleive someone has already done something like that in VIM. I do not
>have the URL handy though. And I wonder how they handle the case where
>in some places, the user wants \sum but wants to display \sigma in other
>places...
>
>Srinath
>

[Vim-latex-devel] system-local: 2 problems

[Mikolaj M. <mi...@wp...>]

But these features are not complete. It doesn't break
any existing functionality but is not ready yet.

There are still unresolved
problems:

1. main.vim

" This line seems to be necessary to source our compiler/tex.vim file.  " 
The
" docs are unclear why this needs to be done even though this file is " the 
first
" compiler plugin in 'runtimepath'.
runtime compiler/tex.vim

But with system installation this may will source local version of
compiler. Maybe something like

let lscompilerpath = fnamemodify(s:path, ":p:h")
exe 'source '.lscompilerpath.'tex.vim'

Or we could entirely get rid of compiler/tex.vim, put its contents in
latex-suite/compiler.tex and avoid sourcing of compiler/tex.vim by
including if | endif into main.vim.

2. installation: Makefile

Because I would like to make it more like regular programs Makefile
needs "make install", "make uninstall". But here is problem:

Vim is installed in very various ways. Eg. Mdk don't follow Vim FHS and
there is no place for vimfiles (or vim-scripts as in Debian policy)
dirs.

I am playing now with vim.spec for Mdk and will try to convince
maintainers to follow Vim FHS and even better Debian Vim scripts policy.
With two major distributions following this guidelines it would be
easier to change other.

Maybe we could ask Bram to include vim-scripts directory as an official
directory in Vim FHS? With support in official vim-docs we would have
another point.

In meantime we could offer install.sh script. It could give nice dialogs
with possible choices and explanations about them:

~/.vim - local installation
/usr/local/share/vim/vimfiles  - system wide installation with locally
	build Vim
/usr/share/vim - Vim from package in distro not following Vim FHS
/usr/share/vim/vimfiles - Vim from package in distro which follows Vim
	FHS
/usr/share/vim/vim-scripts - Vim from package in distro which follows
	Debian Vim scripts policy

Of course it could be automated (eg. checking `which vim` could 
answer where Vim is installed and give proper default, maybe check for
`uname -a`).

Such script could allow also for basic preconfiguration of texrc
(default target, latex flavour).

 http://yacoob.dnsalias.net/sakwa/vim-policy.txt

 m.

Re: [Vim-latex-devel] bug in ps compilation

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

On Sun, 28 Sep 2003, jorgep wrote:

> When I choose to compile directly to ps file the compiler does't catch the
> errors on the dvi compilation.
>
Yes... This is a known limitation at the moment. I will work on this
after about 2 weeks.

If someone is interested, the relevant function is RunLaTeX() in
compiler.vim....

Thanks,
Srinath

[Vim-latex-devel] bug in ps compilation

[jorgep <jo...@it...>]

When I choose to compile directly to ps file the compiler does't catch the 
errors on the dvi compilation.

Thank's for your attention

[Vim-latex-devel] New features: compiler, taglist, system-local

[Mikolaj M. <mi...@wp...>]

Hello,

New features implemented. 
They can be separated in three parts:

1.
compiler + texrc

Possibility to disable going to bug/warning immediately after compilation.

2.
taglist.vim support

As I mentioned earlier taglist.vim is the most popular interface to
ctags (also popular program). Support is enabled by default. You have to
have only taglist.vim (2.8 is enough) and ctags (at least 5.0). You
don't need to configure anything else. Use :Tlist command (taglist.vim)
to open window with tags in current file.

3.
system-local

Commands, both creating menus and :, are looking for files in all &rtp
directories. Behaviour difference little depending on context:

packages - sources (using runtime!) all related files in rtp directories
_in_ latexSuite FHS (ftplugin/latex-suite/packages). Files provided with
latexSuite have plugin headers (|write-plugin|), thus they behave as
regular ftplugin/syntax/plugin etc. files.

templates - you see only all files from
rtp:ftplugin/latex-suite/templates dirs but if file in local dir has the
same name as file in system dir it overshadows system version.

macros - 
When you try to edit file from system directory it is copied to local
dir with '-local' suffix. Don't remove file if it is not in local
directory. Check if exist macro with this name, and forces to pick
another name.

Everything is now only in CVS. Tested on Linux. Aha. Name of local
directory is made:

if has("unix") || has("macunix")
    let s:macrodirpath = $HOME."/.vim/ftplugin/latex-suite/macros/"
elseif has("win32")
    if exists("$HOME")
        let s:macrodirpath = $HOME."/vimfiles/ftplugin/latex-suite/macros/"
    else
        let s:macrodirpath = $VIM."/vimfiles/ftplugin/latex-suite/macros/"
    endif
endif   

Probably if on MS-Windows systems doesn't exist $HOME variable it is
single-user machine and there is no need for difference.

m.

Re: [Vim-latex-devel] Turn off goto error?

[<mi...@wp...>]

On 26 Sep 2003 at 11:41, Preben Randhol wrote:

> mi...@wp... wrote on 26/09/2003 (10:24) :
> 
> > Don't understand. This method of not going to error doesn't work or
> > described bug doesn't occur?
> 
> First the line number was wrong. Second when I tried it didn't work. See
> my other post for what I had to do to fix the problem.

OK. Send me patch or better (for me) fragment of file.

m.

[Vim-latex-devel] Windows $HOME (related to Revolution)

[<mi...@wp...>]

Hello,

Real implementing of system-wide/local auxiliary files is going well. The only big problem is $HOME directory on Windows and 
Macro related commands.

Macro commands allow for editing, creating and removing custom files in s:path/macros/ directory. But s:path is path to script - 
which in distribution (I hope) version will be non-writable area for common user.

I can create in variable s:macropath depending on OS. For *nices it will be
$HOME/.vim/ftplugin/latex-suite/macros

But what on Windows? Any hints?

m.

Re: [Vim-latex-devel] Revolution! :)

[<mi...@wp...>]

On 25 Sep 2003 at 20:53, Luc Hermitte wrote:

> > Jokes aside. There are still issues:
> > creating menus is based on list returned by globpath(). How to sort
> > endresults and remove duplicate entries? 
> 
> The last entry according to 'runtimepath' should be the one! Or the
> first, as you wish. I'm not sure sort or uniq will be very useful here.

Hmm. I think you are right here. I will do it another way:

for package files add common plugin header (if exists() finish etc.) and source them if repeated as regular runtime files are treated.

for templates/macros :read in only first entry. Sourcing last has no sense. Files in $HOME obviously should have priority.

dictionaries: add all dictionaries with asked name.

> 
> Just in case, with :SearchInRuntime, I would have written something
> like:
>     function s:AddFileToList(file)
>       let fn = fnamemodify(a:file, ':t')
>       if s:list =~ a:file
> 	" use the "keep the last entry"-policy
> 	let s:list = substitute(s:list, 
>             \ "^\\(\\|\n\\)\\zs[^\\n]*".fn."\\ze\\(\n\|$\\)", a:file, 'g')
>       else
> 	let s:list = s:list . "\n".a:file
>       endif
>     endfunction
>     command! -nargs=1 LetFiles :call s:AddFileToList('<q-args>')
> 
>     let s:list = ''
>     SearchInRuntime! :LetFile packages/foo*.vim

This function is nice but requires iterating through list of files which is sloooow in VimL. 

> The best solutions for uniq and sort have been included into
> system_utils.vim avaible on my web site.
>     http://hermitte.free.fr/vim/ressources/vimfiles/plugin/system_utils.vim

Thanks. I will look into it.

m.

Re: [Vim-latex-devel] Strange black blocks in Gvim (GTK+ version)

[<mi...@wp...>]

On 25 Sep 2003 at 21:53, Preben Randhol wrote:

> Hi
> 
> I get some strange black blocks of text when I am compiling latex in
> 1.5-rc1. Is the background of the text set to black? 
> 
> It says Latex run number: 1 
> 
> and then some black blocks appear and go away.
> 
Can't confirm.
Which version of Vim do you have? Some GTK versions have problems with fonts.

m.

Re: [Vim-latex-devel] Revolution! :)

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

Hello!

Unfortunately, I am really busy nowadays with some studying. I have
a big oral examination coming up in the next few weeks and I have
promised myself that I will not be doing any coding till after the exam
is done.

On Thu, 25 Sep 2003 mi...@wp... wrote:

> OK. Subject is exaggeration, but not so much.
> Sounds unimpressive but it allow for creating real distribution
> packages and real *nix behaviour with system wide files and local
> modifications. I am dusting off 'man rpm' ;)
>
:)

The changes sound excellent. I will incorporate them into the tree as
soon as I get back.

> Jokes aside. There are still issues: creating menus is based on list
> returned by globpath(). How to sort endresults and remove duplicate
> entries? I remember long discussions on vim-list about Sort and Uniq.

I do not think we want to remove duplicates. After all, how do we know
that $VIM/ftplugin/latex-suite/packages/amsmath.vim is the same as
$VIM/ftplugin/latex-suite/packages/amsmath.vim? Hmmm... Maybe have
a single menu item for amsmath but source every
ftplugin/latex-suite/packages/packages.vim in the runtimepath... just
a simple:
    runtime! ftplugin/latex-suite/amsmath.vim

> (after win-test) with Tex_file_rtp() in main.vim? I can proceed with
> implementation for templates and macros.

I thought we had decided on the CamelCase convention for function names.
Could you please follow the convention as well? I am kinda anal about
being consistent :) Please!

Let me recap:

1. Code according to the following modeline:
    vim:noet:sw=4:ts=4

2. Follow CamelCase for function names, variable names etc.

3. Function names should be verbs. For example, if Tex_file_rtp() is
   supposed to find a file in 'rtp', use Tex_FindInRTP() instead of
   Tex_file_rtp().

4. Variable names should be nouns as far as possible.

Anyway, please try to maintain this convention...


Srinath

[Vim-latex-devel] Strange black blocks in Gvim (GTK+ version)

[Preben R. <ra...@pv...>]

Hi

I get some strange black blocks of text when I am compiling latex in
1.5-rc1. Is the background of the text set to black? 

It says Latex run number: 1 

and then some black blocks appear and go away.

Preben

Re: [Vim-latex-devel] Revolution! :)

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

Hello,

* On Thu, Sep 25, 2003 at 08:15:50PM +0200, mi...@wp... <mi...@wp...> wrote:
> First is only diff (diff -u -3 -p), second is complete file
> packages.vim. Revolution is: now functions in packages.vim looks in
> all rtp directories for package files and creates complete list.

> Sounds unimpressive but it allow for creating real distribution
> packages and real *nix behaviour with system wide files and local
> modifications. I am dusting off 'man rpm' ;)

Sounds important : one of the first things I added into mu-template --
thanks to searchInRuntime.vim (which defines some hybrid commands
between :runtime and the unix's `find' tool)

> Jokes aside. There are still issues:
> creating menus is based on list returned by globpath(). How to sort
> endresults and remove duplicate entries? 

The last entry according to 'runtimepath' should be the one! Or the
first, as you wish. I'm not sure sort or uniq will be very useful here.

Just in case, with :SearchInRuntime, I would have written something
like:
    function s:AddFileToList(file)
      let fn = fnamemodify(a:file, ':t')
      if s:list =~ a:file
	" use the "keep the last entry"-policy
	let s:list = substitute(s:list, 
            \ "^\\(\\|\n\\)\\zs[^\\n]*".fn."\\ze\\(\n\|$\\)", a:file, 'g')
      else
	let s:list = s:list . "\n".a:file
      endif
    endfunction
    command! -nargs=1 LetFiles :call s:AddFileToList('<q-args>')

    let s:list = ''
    SearchInRuntime! :LetFile packages/foo*.vim


> I remember long discussions on vim-list about Sort and Uniq. I didn't
> follow it closely. Could someone suggest the best solutions?

The best solutions for uniq and sort have been included into
system_utils.vim avaible on my web site.
    http://hermitte.free.fr/vim/ressources/vimfiles/plugin/system_utils.vim


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

Re: SOLVED Re: [Vim-latex-devel] Turn off goto error?

[<mi...@wp...>]

On 25 Sep 2003 at 11:14, Preben Randhol wrote:

> 
> Could one do something like this for latex-suite as a default? I mean
> one can have Tex_GotoError = 1 as default, but that one can turn it off
> if one want to?

Srinath, could you do it? I don't have access to CVS :(
Maybe with comment it can don't work perfectly in some terminals.

m.

[Vim-latex-devel] Revolution? Attachments ...

[<mi...@wp...>]

Grrr.
I forgot about attachments. Kmail has nice feature to scan message for keywords like 'attaching, patch' and prompt user if there is 
no attachment. Now I am forced to use Pegasus (should be happy no OE :) and forgot about them.

[Vim-latex-devel] Revolution! :)

[<mi...@wp...>]

OK. Subject is exaggeration, but not so much.

Attaching two files:
packages.diff
packages.vim

(Files are ff=unix)
Big comments inside.

First is only diff (diff -u -3 -p), second is complete file packages.vim. Revolution is: now functions in packages.vim looks in all rtp 
directories for package files and creates complete list. Sounds unimpressive but it allow for creating real distribution packages and 
real *nix behaviour with system wide files and local modifications. I am dusting off 'man rpm' ;)

Jokes aside. There are still issues:
creating menus is based on list returned by globpath(). How to sort endresults and remove duplicate entries? I remember long 
discussions on vim-list about Sort and Uniq. I didn't follow it closely. Could someone suggest the best solutions?

I tested it on Linux. Vim does good job with globpath() and directory separators but could someone check it on Windows (on this 
machine I cannot install Vim)?

Currently I don't have access to cvs. Srinath, could you commit this (after win-test) with Tex_file_rtp() in main.vim? I can proceed with 
implementation for templates and macros.

m.

SOLVED Re: [Vim-latex-devel] Turn off goto error?

[Preben R. <ra...@pv...>]

Preben Randhol <ra...@pv...> wrote on 24/09/2003 (12:51) :

I found the place where the GotoError was called. It was in fucntion:

function! Tex_SetupErrorWindow()

I change the end of the function from:

»··»··" resize the window to just fit in with the number of lines.
»··»··exec ( line('$') < 4 ? line('$') : 4 ).' wincmd _'
»··»··call GotoErrorLocation(mfnlog)
»··endif

to

»··»··" resize the window to just fit in with the number of lines.
»··»··exec ( line('$') < 4 ? line('$') : 4 ).' wincmd _'
      if exists('g:Tex_GotoError') && g:Tex_GotoError == 1
»··»··   call GotoErrorLocation(mfnlog)
      else    
         wincmd k
      endif   
»··endif

and the I set g:Tex_GotoError in texrc as mi...@wp... suggested.
Thanks for help by the way.

Could one do something like this for latex-suite as a default? I mean
one can have Tex_GotoError = 1 as default, but that one can turn it off
if one want to?

Thanks in advance.

Preben

Re: [Vim-latex-devel] Turn off goto error?

[Preben R. <ran...@pv...>]

mi...@wp... wrote on 25/09/2003 (10:08) :
> Simple and brute solution:
> 
> Go to ftplugin/latex-suite/compiler.vim and comment line 586 (call GotoErrorLocation(mfnlog)).
> 
> More advanced solution is to create in texrc new variable:
> 
> " This forces LaTeX-Suite to go to each error/warning generated by LaTeX.
> let Tex_GotoError = 1
> 
> Make it enable by default. And in compiler.vim:
> if exists("Tex_GotoError) && Tex_GotoError == 1
> 	call GotoErrorLocation(mfnlog)
> 	" because cursor stays in error list window
> 	wincmd k
> endif
> 
> But there is one question. In linux terminal it can behave strange (vim 6.2.96, lS-1.5-rc1, multi-gnome-terminal):
> 
> Comment line 586. Run \ll in file with fault. Everything is OK. Return to main window, :only, run \ll once more. Cursor vanishes. You 
> have to press <Cr>. Currently this is not problem because <cr> is the first command in GotoErrorLocation().
> 
> Can anybody confirm this?
> 
> m.

I use latexSuite-1.5-rc1 and this method doesn't work.

-- 
Preben Randhol ------------- http://www.pvv.org/~randhol/vim --
                 "Vim : simply the best text editor out there."

[Vim-latex-devel] g:Tex_CompileRule

[Troy H. <the...@ma...>]

LaTeX-suite developers,

Thanks for a GREAT product for vim.  I'm impressed at all the work that 
has been done.  I have noticed a feature that seems unnatural though.  
This may or may not be a bug, but in any event, I would love to know how I 
would go about fixing it.

I was wondering why pdflatex seems to prompt me to "Hit ENTER or type 
command to continue" when there are in fact no errors on my compile.

Also, because pdflatex generally gives better looking PDF's than 
tex->dvi->ps->pdf, I usually just use pdflatex all the time instead of 
LaTeX and DVIPS and PS2PDF.  Therefore, I set the following variables in 
my tex.vim

let g:Tex_DefaultTargetFormat = 'ps'
let g:Tex_FormatDependency_ps = 'pdf,ps'
let g:Tex_CompileRule_ps = 'acroread -toPostScript -pairs $*.pdf $*.ps'
let g:Tex_ViewRule_ps = 'ggv'
let g:Tex_ViewRule_pdf = 'acroread'

That particular g:Tex_CompileRule_ps is the command line option of 
acroread to convert the PDF into PS.  Anyway, I've noticed also that this 
command executes properly without any errors, and I'm prompted to "Hit 
ENTER or type command to continue".

I was wondering if you could tell me how to eliminate this prompt (as long 
as no errors are encountered in the compilation process).

Thanks so much,

##########################################################################
Troy Henderson                  Office: Blocker Building 619
Department of Mathematics       Phone : (979) 845-7769
Texas A&M University            E-mail: the...@ma...
College Station, TX 77845       URL   : http://www.math.tamu.edu/~thenders
##########################################################################

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

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

On Wed, 24 Sep 2003, steffen wrote:

> Hi!
>
> I have a problem compiling latex-documents with the vim-latex-suite. I
> read on this page (in the FAQ)
>
> http://vim-latex.sourceforge.net/index.php?subject=faq#faq-2
>
> what to do, if vim does nothing, when you write :make. Well here are
> the results:

Everything seems to be working according to your description!

I think you are confused about how to use latex-suite's compilation
functionality. You are supposed to type \ll in normal mode, not type
:make. See the following manual section:

http://vim-latex.sourceforge.net/documentation/latex-suite/latex-compiling.html

Srinath

[Vim-latex-devel] Vim-Latex

[steffen <ps...@ko...>]

Hi!

I have a problem compiling latex-documents with the vim-latex-suite. I
read on this page (in the FAQ)

http://vim-latex.sourceforge.net/index.php?subject=faq#faq-2

what to do, if vim does nothing, when you write :make. Well here are
the results:

I can run the value of makeprg

pdflatex -interaction=nonstopmode $*

on command line (using the filename, instead of $*). This works. I can
even execute in vim the command:

!pdflatex -interaction=nonstopmode %

And i can call the function RunLaTeX() - VIM shows the errors in my
latex-document and opens 2 additional windows.

My operating system is WinXP, i'm using Vim6.2 + MikTeX.

Maybe you have some idea, what i can do to solve that problem. Thank
you in advance,

Steffen

-- 
http://www.kontraphon.de                   mailto:ps...@ko...

[Vim-latex-devel] Turn off goto error?

[Preben R. <ra...@pv...>]

When I type \ll latex compiles my document and then I am moved to to
place where a Warning was issued. Is there a way to prevent this? The
problem is that I get some warnings about som citations or references I
haven't put in yet and I keep having to go my way back in the document
every time. I guess I can turn on the ignore warnings, but it would be
nice to see them, just not automatically jump to them. Can this be done?

Thanks in advance

Preben Randhol