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

Re: [Vim-latex-devel] text clobbered in vim (but not gvim)

[Stephen W. <sw...@gm...>]

Thanks a lot Mirko.
kdvi is very nice, and works out of the box with gvim for forward and
backward search after inserting the -src-specials in
Tex_CompileRule_dvi
But you saved my a lot of head scratching to make backward search work
with vim so thanks (I guess if you don't start vim with --servername
KDVI, there's no one listening for backward searches?)

BTW, I meant to send my last few messages to the list, but I think
they only went to you... so I'm CC'ing this one to the list as it will
surely help others.

Thanks again,
Steve

On 27/11/2007, Mirko Hessel-von Molo <mi...@ma...> wrote:
> On Mon, 26 Nov 2007, Stephen Wilkinson wrote:
>
> >> Well kdvi reads source-specials. I got to work forward and backward search
> >> with it.  If you're interested I can let you know how.
> > Yes please! That would save me a lot of time and aggravation! I've
> > just installed kdvi and  finally I can scroll continuously between
> > pages!
>
> So it seems you already have kdvi as your default viewer for \lv (and \ls).
> Forward search should work with kdvi as soon as you enable the
> src-specials. To do that, put
>
> TexLet g:Tex_CompileRule_dvi = 'latex -src-specials -interaction=nonstopmode $*'
>
> into .vim/ftplugin/tex/texrc. This brings you to the right place in your
> dvi document when you issue \ls.
>
> For inverse search you need to tell kdvi which editor to call upon middle
> mouse button click. You do that in (my kdvi menus are in German, so I guess
> the English names) Options -> Preferences -> DVI Specials -> Editor for
> inverse search. Choose Custom editor and enter
>
> vim --servername KDVI --remote-silent +%l %f
>
> as custom command. This assumes that you started your vim using
>
> vim --servername KDVI filename.tex
>
> (Alternatively gvim, it just works the same.) You are free to choose a
> different servername, of course, only make sure its the same in both
> commands.
>
> Maybe I forgot something. If so, tell me ;-)
>
> Yours, Mirko
>
>
>

[Vim-latex-devel] vim-latex on Ubuntu Feisty: nautilus and current directory

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

Hi,

Just a hint for Ubuntu Feisty (probably applies to other Linux
distributions) users, who open tex files from nautilus using gvim. When
you open tex file from nautilus window, gvim does not set current
directory to the directory where the file is. This creates few problems
for vim-latex. I found two (possibly there are more):

1. ViewLateX command does not work, you cannot call xdvi or other viewer
using vim-latex
2. If you use bibliography with BibTeX, F9 completion does not work. 

All these problems goes away, if you set current directory to the
directory where the file resides. Here is the shortcut for  achieving
this:

nmap <F4> :exec 'cd '.expand("%:p:h")<CR> :echo getcwd()<CR>

Of course you can assign it to any keyboard shortcut you want to. 

I hope this hint will save somebody some time. It surely would have
saved mine.

Vaidotas Zemlys

Re: [Vim-latex-devel] output of xdvi shows in tex-file

[Qiuye W. <qi...@gm...>]

On Mon, Nov 19, 2007 at 02:19:17PM +0100, Thomi Dammann wrote:
>
>> when i press \lv or \ls in vim, ie launch the xdvi i always got the
>> output info of xdvi in the line of my tex file, where the cursor were.
>> It's really annoying although they just show temporary (they will
>> disappear if i move the cursor down or up till they are out of the
>> sight).
>To redraw the screen on xterm use <CTRL>L. This is much simpler than
>scrolling the screen up and down.
>
>To get rid the messages you can try
>
>:let g:Tex_ViewRule_dvi='xdvi>/dev/null 2>/dev/null'. (assuming you use
>Unix).

Thank you for the hints, i've found the way to keep the xdvi normally
work and now it's quite, but the `2>/dev/null' is also a good idea.
Thanks anyway.
  
Cheers,
QY

Re: [Vim-latex-devel] F9 completion problem in vim7

[Stephen W. <sw...@gm...>]

Ahmet,

You've probably fixed your problem by now, but this is just to say it seems
to work in vim 7.1 and the latest version of vim-latex suite for me.

Steve

On 05/11/2007, ahmet nurlu <ahm...@ya...> wrote:
>
> Hi,
>
> I have been getting this recent error with a vim7.1.
> It is not happening with vim6.4.
>
> The problem is that \cite{} command doesn't search
> through \begin{thebibliography} environment.(It is
> strange that  when I type "\cite" , its color becomes
> blue.)
>
> My tex file(try.tex) is something like:
> ------------------------------------->
> \documentclass{article}
> \usepackage{color}
> \usepackage{listings}
> \begin{document}
> try try try
>
> \cite{}<++>
>
> \begin{thebibliography}{99}
>        \bibitem{goossens93} Michel Goossens, The Latex
> Book
> \end{thebibliography}
> \end{document}
> ---------------------------------------------<
>
> when the cursor positions itself into the \cite{},
> pressing F9 brings no action.
>
> This problem doesn't arise if I prepare a bib
> file(trybib.bib) and put my bibliography index into
> it. For example,
>
> my_Directory/
>        try.tex
>        trybib.bib
> ------------------------------------------------->
> \documentclass{article}
> \usepackage{color}
> \usepackage{listings}
> \begin{document}
> try try try
>
> \cite{}<++>
> \bibliographystyle{plain}
> \bibliography{trybib}
>
> \end{document}
>
> I am using vim-latexsuite(debian/unstable). Any
> suggestions?
>
> Regards,
> Ahmet
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] text clobbered in vim (but not gvim)

[Martin S. <fo...@un...>]

On Tue, Nov 20, 2007 at 01:29:41PM +0000, Stephen Wilkinson wrote:
> I don't know how to > test for "if not" so I've put the statement in
> the "else" part

 if !has("gui_running")
     :nnoremap <buffer> <Plug>Tex_Compile :call Tex_RunLaTeX()\|redraw!<cr><cr>
 endif

by the way, I added another <cr> to the end of the line because I got
one of these annoying "Press ENTER or type command to
continue"-prompts..

> Martin, I saw your reply to the thread "output of xdvi shows in tex file" -
> and thought maybe the same trick would apply. I get the same problem with
> xdvi writing its output into my tex file

Well, I guess you have seen the

	xdvi.hushStdout: true

Setting for .Xdefaults already. If xdvi still writes to stderr, you could
try

	$ alias xdvi="xdvi 2>/dev/null"

This should work as
 
  $ xdvi 2>/dev/null somefilethatisnotdvi

does not print anything (while it does without redirection). You are on
a *nix system, aren't you?

> Thanks for your help,

You're welcome. I have profited so much from the FLOSS community that I
am glad I can help some other people myself. Good for my Karma (not that
I am a Buddhist, rather a fan of "My Name is Earl").

Martin

Re: [Vim-latex-devel] text clobbered in vim (but not gvim)

[Stephen W. <sw...@gm...>]

Hi Martin and Mirko,

Thank you both for your replies - glad to see I'm not alone with this
problem!

Martin, thanks for your suggestion which works for me. I've updated my
.vim/after/ftplugin/tex.vim file with the following (I don't know how to
test for "if not" so I've put the statement in the "else" part):

if has("gui_running")
else
    :nnoremap <buffer> <Plug>Tex_Compile :call Tex_RunLaTeX()\|redraw!<cr>
endif

Martin, I saw your reply to the thread "output of xdvi shows in tex file" -
and thought maybe the same trick would apply. I get the same problem with
xdvi writing its output into my tex file, so I tried this:

:nnoremap <buffer> <Plug>Tex_Compile :call Tex_ViewLaTeX()\|redraw!<cr>
**
but it doesn't work, and I'm not sure why. Any suggestions?

Thanks for your help,
Steve

On 19/11/2007, Martin Sander <fo...@un...> wrote:
>
> Hey, this annoyed me to (a lot). I don't remember that this has always
> been like this, maybe it has been introduced by vim 7.1.
> Anyways, my workaround was using gvim, but now you got me motivated to
> search for a real solution, and I found it:
>
>         $ tail -2 .vim/after/ftplugin/tex.vim
>         "refresh after compiling..
>         :nnoremap <buffer> <Plug>Tex_Compile :call
> Tex_RunLaTeX()\|redraw!<cr>
>
> (I found that in latex-suite/compiler.vim:796).
> A caveat is that you won't see the "compiled latex <n> times" message.
>
> Bye
>
> Martin
>
> On Sun, Nov 18, 2007 at 11:14:43PM +0000, Stephen Wilkinson wrote:
> > Hello everyone,
> >
> > I normally use gvim with vim-latex, but I recently I tried vim (i.e.
> > without the GUI), and when compiling with \ll or opening the viewer
> > with \lv, messages from the external programs clobber the text in the
> > vim window.
> >
> > For instance when compiling, I get:
> > This is BibTeX, Version 0.99c (Web2C 7.5.4)
> > The top-level auxiliary file: test.aux
> > The style file: plain.bst
> > Database file #1: test.bib
> >
> > at the bottom of the Vim window, and the text in the buffer
> > "disappears"... it's still there and I can move the cursor over it,
> > but it's invisible. If I use :redraw! all is well again (or else if I
> > change buffer, or split the window, or invoke help, any of these
> > probably cause redraw to be called and make the text reappear).
> >
> > Does anyone else have this problem? Can anyone suggest how I can make
> > the redraw automatic? I thought of adding :redraw! at the end of the
> > Tex_RunLaTeX and Tex_ViewLaTeX functions in
> > ftplugin/latex-suite/compiler.vim but I would prefer not to edit the
> > vim-latex files (as I'll lose changes at the next upgrade).
> >
> > Any suggestions welcome!
> > Thanks, Steve
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] Error when launching viewer with Vim.app on Mac OS X

[Stephen W. <sw...@gm...>]

Hi Jason,

It could be that the message disappears because the command line window only
has one line... so try increasing the number of lines in the command line
window with:

:set ch=20

for example. Then try compiling... and maybe the error message will be
visible then. (Use the same command to reset it to 1 when you're done).

HTH,
Steve

On 20/11/2007, Jason Stein <jas...@gm...> wrote:
>
> I recently installed Vim.app and vim-latex on a PowerMac G4 with Mac
> OS X. I also installed MacTeX. Compilation worked fine with
> <leader>-l, but viewing the resulting file does not work with
> <leader>-v. An error is briefly reported, but soon disappears. Anyone
> have any thoughts?
>
> --
> Jason T. Stein
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] Error when launching viewer with Vim.app on Mac OS X

[Jason S. <jas...@gm...>]

I recently installed Vim.app and vim-latex on a PowerMac G4 with Mac
OS X. I also installed MacTeX. Compilation worked fine with
<leader>-l, but viewing the resulting file does not work with
<leader>-v. An error is briefly reported, but soon disappears. Anyone
have any thoughts?

-- 
Jason T. Stein

Re: [Vim-latex-devel] output of xdvi shows in tex-file

[Thomi D. <Th...@Fa...>]

> when i press \lv or \ls in vim, ie launch the xdvi i always got the
> output info of xdvi in the line of my tex file, where the cursor were.
> It's really annoying although they just show temporary (they will
> disappear if i move the cursor down or up till they are out of the
> sight).
To redraw the screen on xterm use <CTRL>L. This is much simpler than
scrolling the screen up and down.

To get rid the messages you can try

:let g:Tex_ViewRule_dvi='xdvi>/dev/null 2>/dev/null'. (assuming you use
Unix).

Regards


Thomi

Re: [Vim-latex-devel] text clobbered in vim (but not gvim)

[Martin S. <fo...@un...>]

Hey, this annoyed me to (a lot). I don't remember that this has always
been like this, maybe it has been introduced by vim 7.1.
Anyways, my workaround was using gvim, but now you got me motivated to
search for a real solution, and I found it:

	$ tail -2 .vim/after/ftplugin/tex.vim
	"refresh after compiling..
	:nnoremap <buffer> <Plug>Tex_Compile :call Tex_RunLaTeX()\|redraw!<cr>

(I found that in latex-suite/compiler.vim:796).
A caveat is that you won't see the "compiled latex <n> times" message.

Bye

Martin

On Sun, Nov 18, 2007 at 11:14:43PM +0000, Stephen Wilkinson wrote:
> Hello everyone,
> 
> I normally use gvim with vim-latex, but I recently I tried vim (i.e.
> without the GUI), and when compiling with \ll or opening the viewer
> with \lv, messages from the external programs clobber the text in the
> vim window.
> 
> For instance when compiling, I get:
> This is BibTeX, Version 0.99c (Web2C 7.5.4)
> The top-level auxiliary file: test.aux
> The style file: plain.bst
> Database file #1: test.bib
> 
> at the bottom of the Vim window, and the text in the buffer
> "disappears"... it's still there and I can move the cursor over it,
> but it's invisible. If I use :redraw! all is well again (or else if I
> change buffer, or split the window, or invoke help, any of these
> probably cause redraw to be called and make the text reappear).
> 
> Does anyone else have this problem? Can anyone suggest how I can make
> the redraw automatic? I thought of adding :redraw! at the end of the
> Tex_RunLaTeX and Tex_ViewLaTeX functions in
> ftplugin/latex-suite/compiler.vim but I would prefer not to edit the
> vim-latex files (as I'll lose changes at the next upgrade).
> 
> Any suggestions welcome!
> Thanks, Steve

[Vim-latex-devel] text clobbered in vim (but not gvim)

[Stephen W. <sw...@gm...>]

Hello everyone,

I normally use gvim with vim-latex, but I recently I tried vim (i.e.
without the GUI), and when compiling with \ll or opening the viewer
with \lv, messages from the external programs clobber the text in the
vim window.

For instance when compiling, I get:
This is BibTeX, Version 0.99c (Web2C 7.5.4)
The top-level auxiliary file: test.aux
The style file: plain.bst
Database file #1: test.bib

at the bottom of the Vim window, and the text in the buffer
"disappears"... it's still there and I can move the cursor over it,
but it's invisible. If I use :redraw! all is well again (or else if I
change buffer, or split the window, or invoke help, any of these
probably cause redraw to be called and make the text reappear).

Does anyone else have this problem? Can anyone suggest how I can make
the redraw automatic? I thought of adding :redraw! at the end of the
Tex_RunLaTeX and Tex_ViewLaTeX functions in
ftplugin/latex-suite/compiler.vim but I would prefer not to edit the
vim-latex files (as I'll lose changes at the next upgrade).

Any suggestions welcome!
Thanks, Steve

Re: [Vim-latex-devel] output of xdvi shows in tex-file

[Qiuye W. <qi...@gm...>]

Hi,
thanks for the response. 

i do want to use gvim as my editor to edit the tex file, but
unfortunately i need a special input platform for my native language,
which has conflict with the gvim+vim-latexsuite combination.

i have also put the hushStdout in .Xdefaults, but just as in the
manpage of xdvi written, that errors or warnings will still be printed
to stderr even if the option is used.

i guess the only way to fix the problem is to let the xdvi absolutely
normal work, since there are no error, there will also be no output.
But this is already out of range of this list.

Anyway, thank you for the advices.

Cheers
QY
On Fri, Nov 16, 2007 at 01:08:26PM +0100, Martin Sander wrote:
>Hey.
>Workarounds:
>
>a) use gvim. Usuallally I use terminal-vim all the time, but for LaTeX I
>prefer gvim because it does not show console output  and because I found
>it easier to set up forward and backward searching.
>
>b) $ head .Xdefaults
>
>	xdvi.hushStdout: true
>
>some other useful (for me at last) settings for .Xdefaults:
>
>	xdvi.editor: gvim --servername %f --remote-silent +%l %f
>
>	xdvi.wheelTranslations: <Btn5Down>: forward-page()\n \
>	<Btn4Down>:back-page()\n
>
>	xdvi.mainTranslations: #override \
>	Ctrl<Btn1Down>: source-special()\n \
>	<Btn1Down>: do-href()drag(+)\n 
>	!<Btn1Down>: magnifier(*3)\n
>
>	xdvi.keepPosition: true
>
>see xdvi(1) for all these cryptic settings.
>
>happy vimming
>
>Martin
>
>On Fri, Nov 16, 2007 at 12:14:52PM +0100, Qiuye Wang wrote:
>> Hello list,
>> 
>> when i press \lv or \ls in vim, ie launch the xdvi i always got the
>> output info of xdvi in the line of my tex file, where the cursor were.
>> It's really annoying although they just show temporary (they will
>> disappear if i move the cursor down or up till they are out of the
>> sight).
>> 
>> i know this is the issue of xdvi, but is there any way that i can
>> prevent the output of appearing in my tex ie vim window?
>> 
>> Thank you.
>> 
>> Cheers
>> QY
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Microsoft
>Defy all challenges. Microsoft(R) Visual Studio 2005.
>http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>_______________________________________________
>Vim-latex-devel mailing list
>Vim...@li...
>https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] output of xdvi shows in tex-file

[Martin S. <fo...@un...>]

Hey.
Workarounds:

a) use gvim. Usuallally I use terminal-vim all the time, but for LaTeX I
prefer gvim because it does not show console output  and because I found
it easier to set up forward and backward searching.

b) $ head .Xdefaults

	xdvi.hushStdout: true

some other useful (for me at last) settings for .Xdefaults:

	xdvi.editor: gvim --servername %f --remote-silent +%l %f

	xdvi.wheelTranslations: <Btn5Down>: forward-page()\n \
	<Btn4Down>:back-page()\n

	xdvi.mainTranslations: #override \
	Ctrl<Btn1Down>: source-special()\n \
	<Btn1Down>: do-href()drag(+)\n 
	!<Btn1Down>: magnifier(*3)\n

	xdvi.keepPosition: true

see xdvi(1) for all these cryptic settings.

happy vimming

Martin

On Fri, Nov 16, 2007 at 12:14:52PM +0100, Qiuye Wang wrote:
> Hello list,
> 
> when i press \lv or \ls in vim, ie launch the xdvi i always got the
> output info of xdvi in the line of my tex file, where the cursor were.
> It's really annoying although they just show temporary (they will
> disappear if i move the cursor down or up till they are out of the
> sight).
> 
> i know this is the issue of xdvi, but is there any way that i can
> prevent the output of appearing in my tex ie vim window?
> 
> Thank you.
> 
> Cheers
> QY

[Vim-latex-devel] output of xdvi shows in tex-file

[Qiuye W. <qi...@gm...>]

Hello list,

when i press \lv or \ls in vim, ie launch the xdvi i always got the
output info of xdvi in the line of my tex file, where the cursor were.
It's really annoying although they just show temporary (they will
disappear if i move the cursor down or up till they are out of the
sight).

i know this is the issue of xdvi, but is there any way that i can
prevent the output of appearing in my tex ie vim window?

Thank you.

Cheers
QY
-- 
VIM version: 7.1.138
Linux version 2.6.22-2-686
Debian GNU/Linux lenny/sid
  

[Vim-latex-devel] Syntax highlighting

[Peter M. <Pet...@gm...>]

Hello,

I want to customize the syntax highlighting by adding a couple of new 
commands.
I tried to adept some of the current files, but I couldn't get it working.
e.g. The content(##) of the command \review{##} should be highlight with 
texTodo.
Can anyone give me some hints?

Thanks
  Peter

Re: [Vim-latex-devel] Tex_RunLaTeX() does not compile new dvi

[David R. <dav...@gm...>]

WyQqIGluIGxhdGV4LXN1aXRlXToKT0ssIEkgbmV2ZXIgbm90aWNlZCB0aGlzIGJlZm9yZSEKCi0t
IApEYXZpZCBSaWNoZmllbGQKZV4o8GkpKzE9MAo=

Re: [Vim-latex-devel] Tex_RunLaTeX() does not compile new dvi

[Kai L. <les...@pi...>]

Hi David.

Sorry about the confusion.

I had removed part of the FAQ to keep my posting short, so when I said

> 1.What does :echo Tex_CompileRule_dvi say?
>  This works correctly, I'm getting
>    latex -interaction=3Dnonstopmode $*

I meant by "this works correctly" that "latex -interaction=3Dnonstopmade=
 $*"
is the correct answer according to the FAQ.

Thanks for your help!	Kai



>> which is different.  Why do you say that works for you?
> Because it's the fact (I'm not Kai and I have no difficulties with
> complilation of latex files)
>
> It's different, but it seems that $* is substituted by % or %:r.

Re: [Vim-latex-devel] Tex_RunLaTeX() does not compile new dvi

[Thomi D. <Th...@Fa...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
David Richfield wrote:
> On Nov 12, 2007 5:26 PM, Thomi Dammann <Th...@fa...>
> wrote:
>>
>> David Richfield wrote:
>>>> This works correctly, I'm getting latex
>>>> -interaction=nonstopmode $*
>>> If this isn't a typo, it might be your problem.
>> No, that works for me.
>
> You say that when you type
>
> :!latex -interaction=nonstopmode %
>
> it works, but when you type \ll it doesn't work, and if you say
> :echo Tex_CompileRule_dvi it says
>
> latex -interaction=nonstopmode $*
>
> which is different.  Why do you say that works for you?
Because it's the fact (I'm not Kai and I have no difficulties with
complilation of latex files)

It's different, but it seems that $* is substituted by % or %:r.

:h latex-suite.txt

uses allways '$*' as (part of) parameter for the definition of commands.

Thomi

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iD8DBQFHOWndHTFr8LvvEe4RAiT9AKC8X/BIt2gVVMaOITZyyrUEZgDYNQCaAohs
ygG4JFDAlSjyZFUeWfCnLow=
=GGly
-----END PGP SIGNATURE-----

Re: [Vim-latex-devel] Tex_RunLaTeX() does not compile new dvi

[David R. <dav...@gm...>]

T24gTm92IDEyLCAyMDA3IDU6MjYgUE0sIFRob21pIERhbW1hbm4gPFRob21pMzVAZmFtLWRhbW1h
bm4uZGU+IHdyb3RlOgo+IC0tLS0tQkVHSU4gUEdQIFNJR05FRCBNRVNTQUdFLS0tLS0KPiBIYXNo
OiBTSEExCj4KPiBEYXZpZCBSaWNoZmllbGQgc2NocmllYjoKPiA+PiBUaGlzIHdvcmtzIGNvcnJl
Y3RseSwgSSdtIGdldHRpbmcKPiA+PiAgICBsYXRleCAtaW50ZXJhY3Rpb249bm9uc3RvcG1vZGUg
JCoKPiA+Cj4gPiBJZiB0aGlzIGlzbid0IGEgdHlwbywgaXQgbWlnaHQgYmUgeW91ciBwcm9ibGVt
Lgo+IE5vLCB0aGF0IHdvcmtzIGZvciBtZS4KCllvdSBzYXkgdGhhdCB3aGVuIHlvdSB0eXBlCgo6
IWxhdGV4IC1pbnRlcmFjdGlvbj1ub25zdG9wbW9kZSAlCgppdCB3b3JrcywgYnV0IHdoZW4geW91
IHR5cGUgXGxsIGl0IGRvZXNuJ3Qgd29yaywgYW5kIGlmIHlvdSBzYXkgOmVjaG8KVGV4X0NvbXBp
bGVSdWxlX2R2aSBpdCBzYXlzCgpsYXRleCAtaW50ZXJhY3Rpb249bm9uc3RvcG1vZGUgJCoKCndo
aWNoIGlzIGRpZmZlcmVudC4gIFdoeSBkbyB5b3Ugc2F5IHRoYXQgd29ya3MgZm9yIHlvdT8KCi0t
IApEYXZpZCBSaWNoZmllbGQKZV4o8GkpKzE9MAo=

Re: [Vim-latex-devel] Tex_RunLaTeX() does not compile new dvi

[Thomi D. <Th...@Fa...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
David Richfield schrieb:
>> This works correctly, I'm getting
>>    latex -interaction=nonstopmode $*
>
> If this isn't a typo, it might be your problem.
No, that works for me.

Thomi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iD8DBQFHOHCZHTFr8LvvEe4RAp18AJ4qfURXBFYTsMxnxc+E+coJ3sNpPQCeN16q
g/HYS5fcVEFPbGAHux3TlZM=
=PUgH
-----END PGP SIGNATURE-----

Re: [Vim-latex-devel] Tex_RunLaTeX() does not compile new dvi

[Martin S. <fo...@un...>]

Do you have a file called "makefile" or "Makefile" in your working
directory? If so, do a 

:let Tex_UseMakefile=0

in vim and try again.
See :help Tex_UseMakefile

Cheers

Martin

On Mon, Nov 12, 2007 at 02:29:55PM +0100, Kai Lessmann wrote:
> Hello, I'm looking for help with invoking latex from VIM-LaTeX
> using the "\ll" shortcut.
> 
> I've tried to narrow down the problem following the FAQ on
> http://vim-latex.sourceforge.net and I'm listing my answers
> to the question asked there below in this mail.
> 
> The short story is that calling latex from within vim works
> fine (using :!latex -interaction=nonstopmode %)
> but calling :call Tex_RunLaTeX() does not work, its output is
> 
> Running 'bibtex' ...
> Ran latex 1 time(s)
> 
> but the dvi file does not change.
> 
> Thanks in advance, 	Kai

Re: [Vim-latex-devel] Tex_RunLaTeX() does not compile new dvi

[David R. <dav...@gm...>]

> This works correctly, I'm getting
>    latex -interaction=nonstopmode $*

If this isn't a typo, it might be your problem.

[Vim-latex-devel] Tex_RunLaTeX() does not compile new dvi

[Kai L. <les...@pi...>]

Hello, I'm looking for help with invoking latex from VIM-LaTeX
using the "\ll" shortcut.

I've tried to narrow down the problem following the FAQ on
http://vim-latex.sourceforge.net and I'm listing my answers
to the question asked there below in this mail.

The short story is that calling latex from within vim works
fine (using :!latex -interaction=3Dnonstopmode %)
but calling :call Tex_RunLaTeX() does not work, its output is

Running 'bibtex' ...
Ran latex 1 time(s)

but the dvi file does not change.

Thanks in advance, 	Kai




> Q: Compiling does not seem to work for me. My gvim hangs/does nothing.=
1.What does :echo Tex_CompileRule_dvi say?

This works correctly, I'm getting
   latex -interaction=3Dnonstopmode $*


> Make sure that you can get this command to execute on your operating
> system via Vim. In other words, try the following. Open a very minimal=

> .tex file, for example:
> \documentclass{article} \begin{document} This is an article. \end{docu=
ment}
>
> in Vim and type the following sequence of characters inside Vim while =
in
> normal mode: :!latex -interaction=3Dnonstopmode %

Execution using
   :!latex -interaction=3Dnonstopmode %
works for both, the toy example and the document that I'm working on.


> If this command does not work, then it might be due to one of the foll=
owing reasons:  1.You do not have any LaTeX distribution installed on yo=
ur system. Remember,
>   2.Your $PATH variable does not contain the directory in which the la=
tex
>     executable resides.
>   3.Make sure that :set makeprg? shows the same value as Tex_CompileRu=
le_dvi.

It does.

>   4.What happens when you do :call Tex_RunLaTeX() from the command lin=
e?

It *seems* to run because it returns
   Running 'bibtex' ...
   Ran latex 1 time(s)

but leaves the dvi file unchanged and also it returns too
quickly, so I suspect it didn't really run latex.


> In normal operation conditions, this should spawn a shell command whic=
h looks
> like Tex_CompileRule_dvi. The shell should call the latex compiler, wh=
ich should
> run without user intervention. If this gives any errors, g:Tex_Compile=
Rule_dvi
> has not been set properly. If the command above gives an error like  E=
117: Unknown function: Tex_RunLaTeX()
> you are using an older Latex-suite. Upgrade!

> 5.What is your operating system?

Debian GNU/Linux 4.0 (etch), Kernel 2.6.18-5-686


> 6.What version of latex are you using?

pdfeTeX using libpoppler 3.141592-1.21a-2.2 (Web2C 7.5.4)
in texlive 2005.dfsg.3-1

My VIM is version is 7.0

[Vim-latex-devel] Mac OS X menus

[John S. <js...@nd...>]

Vim-latex users,

When using gvim in Mac OS X, no subitems appear in the templates or
macros menus.  This is moderately annoying, although by no means a
showstopper.  I was wondering if anyone had any idea of why this might
be?  In addition, when using vim-latex on Linux, the key mappings for
commands are visible in the menus.  Again, this doesn't seem to be the
case in Mac OS X.  Thanks for any information.  Googling this issue
hasn't led to any interesting solutions.

I'm using Mac OS X (10.5) and the most recent vim-latex suite.

-- 
John T. Shafer, PhD
Manager, Notre Dame ICP-MS Facility
Assistant Research Professor
Dept. of Civil Eng. & Geological Sciences
University of Notre Dame
Notre Dame, IN 46556
tel. 574-631-9049

[Vim-latex-devel] Reference completion: <cr> does not add label when selected in __OUTLINE__ window

[Jannes V. <jan...@gm...>]

When trying to complete a reference with F9, I get the __OUTLINE__
window with all listed labels, but I cannot seem to select any using
<cr> (enter). Upon pressing <cr>, I get the following output error:
E172: Only one filename allowed
My project is broken down as:

[prj root]:
main.tex
main.tex.latex
chapters/chapter1.tex
chapters/chapter2.tex
figures/figure1.eps ... etc

When editing a project with a flat directory hierarchy, all works well.

Are there any modifications necessary to facilitate hierarchical projects?

Regards
PJV