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

Re: [Vim-latex-devel] quickfix does not jump to the error

[Dan M. O. H. <dm...@st...>]

Den 4. juni 2010 kl. 17.21 skrev Sébastien Barthélemy:

> Hello again,
> 
> now that the compilation occurs, I get a problem with the QuickList.
> When I press enter in the QuickList, the preview window hides itself,
> but the cursor does not jump to the document window (it stays in the
> QuickFix window).

This question has been asked several times, and I guess it should also be incorporated into the FAQ?

See 

http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html

for more details. In short, you have to run a post-process script that sanitizes the error messages into a format that Vim likes, but the solution is not fool-proof. You should read the comments section as well. For example it is mentioned there that the solution will not work if the output contains for example overfull hbox warnings. In this case you can use the -file-line-error switch, but this only works for errors, not warnings. There is no one single perfect solution I think.

Dan Michael

Re: [Vim-latex-devel] when \ll does not work, I cannot see the error window

[Dan M. O. H. <dm...@st...>]

Den 4. juni 2010 kl. 16.26 skrev Sébastien Barthélemy:

> Hello,
> 
> I'm trying out vim-latex and I get a problem when compiling a (any) document.
> 
> With MacVim 7.2, when I hit \ll a buffer with errors appears and then
> disappears too
> fast for me to read them.
> 
> With VIM 7.2 in a terminal, I get the same problem, but the buffer
> disappears a little bit later.
> 
> Is it normal for this buffer to disappear? If yes, how can I read it?
> 
> I eventually understood that it was not compiling because of a
> Makefile that was lying around. Maybe that could be mentioned in the
> FAQ [1]?
> 
> [1] http://vim-latex.sourceforge.net/index.php?subject=faq&title=FAQ#faq-compiling

I guess what you see is the stdout, which is not really a buffer. In general, setting
:let g:Tex_Debug=1
before you compile, and running
:call Tex_PrintDebug()
afterwards may give some hints. I'm not sure if there is a way to retrieve the 
stdout afterwards without modifying vim-latex, but there probably is :)

Makefiles can be disabled by setting Tex_UseMakefile to 0:
http://vim-latex.sourceforge.net/documentation/latex-suite/customizing-compiling.html#Tex_UseMakefile

But I also think the FAQ could warn about makefiles, since it's a potential pitfall one might not be aware of.

Dan Michael

[Vim-latex-devel] quickfix does not jump to the error

[Sébastien B. <bar...@cr...>]

Hello again,

now that the compilation occurs, I get a problem with the QuickList.
When I press enter in the QuickList, the preview window hides itself,
but the cursor does not jump to the document window (it stays in the
QuickFix window).

Any idea about this problem? It happens whenever the latex error is in
a folded section or not.

I use MacVim 7.2 and vim-latex 1.8.23. My setup is a little bit
particular: I compile my latex document using scons. And I run scons
with a trivial Makefile:

pdf:
    scons

The eventual command is:
pdflatex -interaction=nonstopmode -recorder 00-manuscrit.tex

Should I modify it to help vim parse the log? How could I debug this?

Thanks for any help !

[Vim-latex-devel] when \ll does not work, I cannot see the error window

[Sébastien B. <bar...@cr...>]

Hello,

I'm trying out vim-latex and I get a problem when compiling a (any) document.

With MacVim 7.2, when I hit \ll a buffer with errors appears and then
disappears too
fast for me to read them.

With VIM 7.2 in a terminal, I get the same problem, but the buffer
disappears a little bit later.

Is it normal for this buffer to disappear? If yes, how can I read it?

I eventually understood that it was not compiling because of a
Makefile that was lying around. Maybe that could be mentioned in the
FAQ [1]?

[1] http://vim-latex.sourceforge.net/index.php?subject=faq&title=FAQ#faq-compiling

[Vim-latex-devel] [ vim-latex-Patches-3004833 ] Add okular search forward support

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

Patches item #3004833, was opened at 2010-05-20 20:20
Message generated for change (Tracker Item Submitted) made by marionline
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3004833&group_id=52322

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mario Santagiuliana (marionline)
Assigned to: Nobody/Anonymous (nobody)
Summary: Add okular search forward support

Initial Comment:
Add support to search forward in okular with just this example configuration in vimrc:
let g:Tex_CompileRule_dvi='latex -src-specials -interaction=nonstopmode $*'
let g:Tex_ViewRule_dvi = 'okular'

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3004833&group_id=52322

[Vim-latex-devel] [ vim-latex-Patches-3004790 ] Remove some default error formats (solves bug with revtex4)

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

Patches item #3004790, was opened at 2010-05-20 18:09
Message generated for change (Tracker Item Submitted) made by johfel
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3004790&group_id=52322

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: johfel (johfel)
Assigned to: Nobody/Anonymous (nobody)
Summary: Remove some default error formats (solves bug with revtex4)

Initial Comment:
Using revtex4, the version line in the log file is matched by the default error formats of vim. This leads to confusing error messages. 
The attached patch solve this (and comparable problems) by removing the responsible error formats.
The vim-latex code adds comparable, but less error-prone error formats, so that the default error formats are not necessary.

Description: Remove some default error formats.
 The default error patterns, that are removed by this patch, match wrongly version
 messages (for example of revtex4).
 The comparable error formats in compiler/tex.vim are less error-prone.
Author: Johann Felix Soden <jo...@gm...>
Bug-Debian: http://bugs.debian.org/582100

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3004790&group_id=52322

Re: [Vim-latex-devel] Macvim 7.2 errors on \lv

[Dan M. O. H. <dm...@st...>]

In Vim, just type :echo("hasunix") and :echo("hasmacunix") to check the value of these settings. The Mac OS X bundled Vim declares itself only as unix, while MacVim declares itself as both unix and macunix. MacVim is also compiled with more options, like ruby support, and it provides a GUI (the VimLatex menus can be handy) and better OS integration (like simple copy/paste between Vim and other apps). But make sure to use the latest snapshot on Snow Leopard, as the stable is not stable :)

Generally, its better to set options in .vimrc (in your home folder) than modifying vim-latex itself, since that makes updating vim-latex easier. Just put

let g:Tex_ViewRule_pdf = 'open -a Preview.app' 

in your $HOME/.vimrc (~/.vimrc that is). If you need to detect mac (say you want to sync the .vimrc between different computers), don't rely on has("macunix"), but use something like this:

if has("unix") && match(system("uname"),'Darwin') != -1
    " It's a Mac!
    let g:Tex_ViewRule_pdf = 'open -a Preview.app' 
endif      

Dan Michael

Den 16. mai 2010 kl. 07.53 skrev Bayard Randel:

> I ended up resolving this issue by uncommenting
> 
> 	TexLet g:Tex_TreatMacViewerAsUNIX = 1
> 
> and setting the following explicitly:
> 	
> TexLet g:Tex_ViewRule_pdf = 'open -a Preview'
> 
> I tried Gianluca's solution, but the problem continued to persist. 
> 
> Hope that helps anyone that has been stuck getting the latex suite working in OS X.
> 
> thanks
> 
> On 16 May 2010 15:24, David Reed <dav...@gm...> wrote:
> I was hopeful that this would solve the problem.  I have been able to compile but this was with some combination of files in certain locations that I cannot figure out.  
> 
> I appreciate the help though.  
> 
> On Sat, May 15, 2010 at 8:48 PM, Gianluca Meneghello <gia...@gm...> wrote:
> I had the same problem, but I'm not an expert so I'm not sure this is
> the correct solution.
> 
> In the texrc file (probably in your
> $HOME/.vim/ftplugin/latex-suite/texrc) there are a couple of
> "has:('macunix')" entries, one for the viewer and one for the
> compiler.
> 
> I solved the problem by replacing it with "has:('unix')".
> 
> It seems vim on Mac OS X declares itself as unix and not macunix (I
> suppose macunix was on some older Mac OSs, but I'm not at all sure
> about that).
> 
> If someone has a better explanation for this I'm really curious to know!
> 
> Hope it can be useful
> 
> Gianlu
> 
> PS: I've seen there are some "macunix" also in compiler.vim
> ($HOME/.vim/ftplugin/latex-suite/compiler.vim). So far I did not touch
> them, but I think it can be something similar.
> 
> On 16 May 2010 01:58, Bayard Randel <ki...@no...> wrote:
> > The \lv command returns the following error on a clean install of
> > latex-suite on OS X 10.6.3:
> >
> > Error detected while processing function Tex_ViewLaTeX:
> > line   34:
> > E121: Undefined variable: s:viewer
> > E116: Invalid arguments for function strlen(s:viewer)
> > E15: Invalid expression: strlen(s:viewer)
> >
> > Any help would be appreciated, thanks.
> > ------------------------------------------------------------------------------
> >

Re: [Vim-latex-devel] Macvim 7.2 errors on \lv

[Bayard R. <ki...@no...>]

I ended up resolving this issue by uncommenting

TexLet g:Tex_TreatMacViewerAsUNIX = 1

and setting the following explicitly:

TexLet g:Tex_ViewRule_pdf = 'open -a Preview'


I tried Gianluca's solution, but the problem continued to persist.

Hope that helps anyone that has been stuck getting the latex suite working
in OS X.

thanks

On 16 May 2010 15:24, David Reed <dav...@gm...> wrote:

> I was hopeful that this would solve the problem.  I have been able to
> compile but this was with some combination of files in certain locations
> that I cannot figure out.
>
> I appreciate the help though.
>
> On Sat, May 15, 2010 at 8:48 PM, Gianluca Meneghello <gia...@gm...>wrote:
>
>> I had the same problem, but I'm not an expert so I'm not sure this is
>> the correct solution.
>>
>> In the texrc file (probably in your
>> $HOME/.vim/ftplugin/latex-suite/texrc) there are a couple of
>> "has:('macunix')" entries, one for the viewer and one for the
>> compiler.
>>
>> I solved the problem by replacing it with "has:('unix')".
>>
>> It seems vim on Mac OS X declares itself as unix and not macunix (I
>> suppose macunix was on some older Mac OSs, but I'm not at all sure
>> about that).
>>
>> If someone has a better explanation for this I'm really curious to know!
>>
>> Hope it can be useful
>>
>> Gianlu
>>
>> PS: I've seen there are some "macunix" also in compiler.vim
>> ($HOME/.vim/ftplugin/latex-suite/compiler.vim). So far I did not touch
>> them, but I think it can be something similar.
>>
>> On 16 May 2010 01:58, Bayard Randel <ki...@no...> wrote:
>> > The \lv command returns the following error on a clean install of
>> > latex-suite on OS X 10.6.3:
>> >
>> > Error detected while processing function Tex_ViewLaTeX:
>> > line   34:
>> > E121: Undefined variable: s:viewer
>> > E116: Invalid arguments for function strlen(s:viewer)
>> > E15: Invalid expression: strlen(s:viewer)
>> >
>> > Any help would be appreciated, thanks.
>> >
>> ------------------------------------------------------------------------------
>> >
>> >
>> > _______________________________________________
>> > Vim-latex-devel mailing list
>> > Vim...@li...
>> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>> >
>> >
>>
>>
>>
>> --
>> www.itabeta.org
>>
>> First published in September 1843 to take part in "a severe contest
>> between intelligence, which presses forward, and an unworthy, timid
>> ignorance obstructing our progress"
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>
>
>

Re: [Vim-latex-devel] Errors with getting Latex going

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

Hi Gary,

I figured it out.  I still had the downloaded files and directories within
the vim72 directory under ftplugin, I removed all those and now just have
all the files under ./vim/vimfiles.  It compiles beautifully, now I just
need to get better at LaTeX, but I should have more fun now with all the new
features that are available to me.

Thanks for all the help.

-Dave

On Fri, May 14, 2010 at 9:12 PM, Gary Johnson <gar...@sp...> wrote:

> On 2010-05-14, David Reed wrote:
> > Thanks for such a fast reply.  I am not sure the picture is going to make
> it
> > through due to some limitations on size of file.  Actually this is a
> great
> > opportunity to use my newly acquire paste command from vim:
> >
> >
> ----------------------------------------------------------------------------------------------------------------
> > Error detected while processing function Tex_RunLaTeX:
> > line    7:
> > E121: Undefined variable: s:target
> > E15: Invalid expression: s:target
> > line   10:
> > E121: Undefined variable: s:target
> > E116: Invalid arguments for function Tex_Debug
> > line   12:
> > E121: Undefined variable: s:target
> > E116: Invalid arguments for function Tex_GetVarValue
> > ('Tex_FormatDependency_'.s:target) !=
> > ''
> > E15: Invalid expression:
> Tex_GetVarValue('Tex_FormatDependency_'.s:target) !=
> > ''
> > line   21:
> > E121: Undefined variable: dependency
> > E116: Invalid arguments for function Tex_Debug
> > line   25:
> > E121: Undefined variable: dependency
> > E116: Invalid arguments for function Tex_Strntok(dependency, ',', i) !=
> ''
> > E15: Invalid expression: Tex_Strntok(dependency, ',', i) != ''
> > line   51:
> > E121: Undefined variable: initTarget
> > E15: Invalid expression: initTarget
> >
> ----------------------------------------------------------------------------------------------------------------
>
> That worked well.
>
> > I hope you can help me out with whats going on here.
>
> I'll try.  I have to leave shortly, but I'll check back later
> tonight or tomorrow.
>
> Looking at the code, which is in ftplugin/latex-suite/compiler.vim,
> it appears that s:target is supposed to be defined by the function
> Tex_SetTeXCompilerTarget().  Apparently that's not working, which
> is leaving s:target undefined.  It's not immediately obvious to me
> why that's failing, so I'm going to leave it for now.
>
> > I also get some errors that flash as I open a .tex file but they are too
> quick
> > for me to figure out.
>
> Depending on the source of those errors, you should be able to
> recall them by executing
>
>    :messages
>
> That may give us a better clue to what's going on.
>
> If that doesn't help, you might try starting Vim with the -V option
> (see ":help -V") which will show you the details of Vim's startup
> sequence.  That could be a lot to wade through, but if you turn the
> verbosity up to 15 (see ":help 'verbose'") and send the output to a
> file, you could open that file later with Vim and just search for
> "Tex_SetTeXCompilerTarget", then follow the execution of that
> function to find out why s:target isn't being set.
>
> Regards,
> Gary
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] Macvim 7.2 errors on \lv

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

I was hopeful that this would solve the problem.  I have been able to
compile but this was with some combination of files in certain locations
that I cannot figure out.

I appreciate the help though.

On Sat, May 15, 2010 at 8:48 PM, Gianluca Meneghello <gia...@gm...>wrote:

> I had the same problem, but I'm not an expert so I'm not sure this is
> the correct solution.
>
> In the texrc file (probably in your
> $HOME/.vim/ftplugin/latex-suite/texrc) there are a couple of
> "has:('macunix')" entries, one for the viewer and one for the
> compiler.
>
> I solved the problem by replacing it with "has:('unix')".
>
> It seems vim on Mac OS X declares itself as unix and not macunix (I
> suppose macunix was on some older Mac OSs, but I'm not at all sure
> about that).
>
> If someone has a better explanation for this I'm really curious to know!
>
> Hope it can be useful
>
> Gianlu
>
> PS: I've seen there are some "macunix" also in compiler.vim
> ($HOME/.vim/ftplugin/latex-suite/compiler.vim). So far I did not touch
> them, but I think it can be something similar.
>
> On 16 May 2010 01:58, Bayard Randel <ki...@no...> wrote:
> > The \lv command returns the following error on a clean install of
> > latex-suite on OS X 10.6.3:
> >
> > Error detected while processing function Tex_ViewLaTeX:
> > line   34:
> > E121: Undefined variable: s:viewer
> > E116: Invalid arguments for function strlen(s:viewer)
> > E15: Invalid expression: strlen(s:viewer)
> >
> > Any help would be appreciated, thanks.
> >
> ------------------------------------------------------------------------------
> >
> >
> > _______________________________________________
> > Vim-latex-devel mailing list
> > Vim...@li...
> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> >
> >
>
>
>
> --
> www.itabeta.org
>
> First published in September 1843 to take part in "a severe contest
> between intelligence, which presses forward, and an unworthy, timid
> ignorance obstructing our progress"
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] Macvim 7.2 errors on \lv

[Gianluca M. <gia...@gm...>]

I had the same problem, but I'm not an expert so I'm not sure this is
the correct solution.

In the texrc file (probably in your
$HOME/.vim/ftplugin/latex-suite/texrc) there are a couple of
"has:('macunix')" entries, one for the viewer and one for the
compiler.

I solved the problem by replacing it with "has:('unix')".

It seems vim on Mac OS X declares itself as unix and not macunix (I
suppose macunix was on some older Mac OSs, but I'm not at all sure
about that).

If someone has a better explanation for this I'm really curious to know!

Hope it can be useful

Gianlu

PS: I've seen there are some "macunix" also in compiler.vim
($HOME/.vim/ftplugin/latex-suite/compiler.vim). So far I did not touch
them, but I think it can be something similar.

On 16 May 2010 01:58, Bayard Randel <ki...@no...> wrote:
> The \lv command returns the following error on a clean install of
> latex-suite on OS X 10.6.3:
>
> Error detected while processing function Tex_ViewLaTeX:
> line   34:
> E121: Undefined variable: s:viewer
> E116: Invalid arguments for function strlen(s:viewer)
> E15: Invalid expression: strlen(s:viewer)
>
> Any help would be appreciated, thanks.
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>



-- 
www.itabeta.org

First published in September 1843 to take part in "a severe contest
between intelligence, which presses forward, and an unworthy, timid
ignorance obstructing our progress"

[Vim-latex-devel] Macvim 7.2 errors on \lv

[Bayard R. <ki...@no...>]

The \lv command returns the following error on a clean install of
latex-suite on OS X 10.6.3:

Error detected while processing function Tex_ViewLaTeX:
line   34:
E121: Undefined variable: s:viewer
E116: Invalid arguments for function strlen(s:viewer)
E15: Invalid expression: strlen(s:viewer)


Any help would be appreciated, thanks.

Re: [Vim-latex-devel] Errors with getting Latex going

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

I really appreciate all the help, I'm trying hard on my end to understand
whats going on here.

-Dave

On Fri, May 14, 2010 at 9:12 PM, Gary Johnson <gar...@sp...> wrote:

> On 2010-05-14, David Reed wrote:
> > Thanks for such a fast reply.  I am not sure the picture is going to make
> it
> > through due to some limitations on size of file.  Actually this is a
> great
> > opportunity to use my newly acquire paste command from vim:
> >
> >
> ----------------------------------------------------------------------------------------------------------------
> > Error detected while processing function Tex_RunLaTeX:
> > line    7:
> > E121: Undefined variable: s:target
> > E15: Invalid expression: s:target
> > line   10:
> > E121: Undefined variable: s:target
> > E116: Invalid arguments for function Tex_Debug
> > line   12:
> > E121: Undefined variable: s:target
> > E116: Invalid arguments for function Tex_GetVarValue
> > ('Tex_FormatDependency_'.s:target) !=
> > ''
> > E15: Invalid expression:
> Tex_GetVarValue('Tex_FormatDependency_'.s:target) !=
> > ''
> > line   21:
> > E121: Undefined variable: dependency
> > E116: Invalid arguments for function Tex_Debug
> > line   25:
> > E121: Undefined variable: dependency
> > E116: Invalid arguments for function Tex_Strntok(dependency, ',', i) !=
> ''
> > E15: Invalid expression: Tex_Strntok(dependency, ',', i) != ''
> > line   51:
> > E121: Undefined variable: initTarget
> > E15: Invalid expression: initTarget
> >
> ----------------------------------------------------------------------------------------------------------------
>
> That worked well.
>
> > I hope you can help me out with whats going on here.
>
> I'll try.  I have to leave shortly, but I'll check back later
> tonight or tomorrow.
>
> Looking at the code, which is in ftplugin/latex-suite/compiler.vim,
> it appears that s:target is supposed to be defined by the function
> Tex_SetTeXCompilerTarget().  Apparently that's not working, which
> is leaving s:target undefined.  It's not immediately obvious to me
> why that's failing, so I'm going to leave it for now.
>
> > I also get some errors that flash as I open a .tex file but they are too
> quick
> > for me to figure out.
>
> Depending on the source of those errors, you should be able to
> recall them by executing
>
>    :messages
>
> That may give us a better clue to what's going on.
>
> If that doesn't help, you might try starting Vim with the -V option
> (see ":help -V") which will show you the details of Vim's startup
> sequence.  That could be a lot to wade through, but if you turn the
> verbosity up to 15 (see ":help 'verbose'") and send the output to a
> file, you could open that file later with Vim and just search for
> "Tex_SetTeXCompilerTarget", then follow the execution of that
> function to find out why s:target isn't being set.
>
> Regards,
> Gary
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] Errors with getting Latex going

[Gary J. <gar...@sp...>]

On 2010-05-14, David Reed wrote:
> Thanks for such a fast reply.  I am not sure the picture is going to make it
> through due to some limitations on size of file.  Actually this is a great
> opportunity to use my newly acquire paste command from vim:
> 
> ----------------------------------------------------------------------------------------------------------------
> Error detected while processing function Tex_RunLaTeX:
> line    7:
> E121: Undefined variable: s:target
> E15: Invalid expression: s:target
> line   10:
> E121: Undefined variable: s:target
> E116: Invalid arguments for function Tex_Debug
> line   12:
> E121: Undefined variable: s:target
> E116: Invalid arguments for function Tex_GetVarValue
> ('Tex_FormatDependency_'.s:target) !=
> ''
> E15: Invalid expression: Tex_GetVarValue('Tex_FormatDependency_'.s:target) !=
> ''
> line   21:
> E121: Undefined variable: dependency
> E116: Invalid arguments for function Tex_Debug
> line   25:
> E121: Undefined variable: dependency
> E116: Invalid arguments for function Tex_Strntok(dependency, ',', i) != ''
> E15: Invalid expression: Tex_Strntok(dependency, ',', i) != ''
> line   51:
> E121: Undefined variable: initTarget
> E15: Invalid expression: initTarget
> ----------------------------------------------------------------------------------------------------------------

That worked well.

> I hope you can help me out with whats going on here. 

I'll try.  I have to leave shortly, but I'll check back later
tonight or tomorrow.

Looking at the code, which is in ftplugin/latex-suite/compiler.vim,
it appears that s:target is supposed to be defined by the function
Tex_SetTeXCompilerTarget().  Apparently that's not working, which
is leaving s:target undefined.  It's not immediately obvious to me
why that's failing, so I'm going to leave it for now.

> I also get some errors that flash as I open a .tex file but they are too quick
> for me to figure out. 

Depending on the source of those errors, you should be able to
recall them by executing

    :messages

That may give us a better clue to what's going on.

If that doesn't help, you might try starting Vim with the -V option
(see ":help -V") which will show you the details of Vim's startup
sequence.  That could be a lot to wade through, but if you turn the
verbosity up to 15 (see ":help 'verbose'") and send the output to a
file, you could open that file later with Vim and just search for
"Tex_SetTeXCompilerTarget", then follow the execution of that
function to find out why s:target isn't being set.

Regards,
Gary

Re: [Vim-latex-devel] Errors with getting Latex going

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

Thanks for such a fast reply.  I am not sure the picture is going to make it
through due to some limitations on size of file.  Actually this is a great
opportunity to use my newly acquire paste command from vim:

----------------------------------------------------------------------------------------------------------------
Error detected while processing function Tex_RunLaTeX:
line    7:
E121: Undefined variable: s:target
E15: Invalid expression: s:target
line   10:
E121: Undefined variable: s:target
E116: Invalid arguments for function Tex_Debug
line   12:
E121: Undefined variable: s:target
E116: Invalid arguments for function
Tex_GetVarValue('Tex_FormatDependency_'.s:target) !=
''
E15: Invalid expression: Tex_GetVarValue('Tex_FormatDependency_'.s:target)
!= ''
line   21:
E121: Undefined variable: dependency
E116: Invalid arguments for function Tex_Debug
line   25:
E121: Undefined variable: dependency
E116: Invalid arguments for function Tex_Strntok(dependency, ',', i) != ''
E15: Invalid expression: Tex_Strntok(dependency, ',', i) != ''
line   51:
E121: Undefined variable: initTarget
E15: Invalid expression: initTarget
----------------------------------------------------------------------------------------------------------------

I hope you can help me out with whats going on here.

I also get some errors that flash as I open a .tex file but they are too
quick for me to figure out.

Thanks again.

-Dave

Re: [Vim-latex-devel] Errors with getting Latex going

[Gary J. <gar...@sp...>]

On 2010-05-14, David Reed <dav...@gm...> wrote:
> Hi,
> 
> Thanks for the help so far.  So taking your advice, I decided to
> delete the ~ /.vim directory and have run into another set of
> errors.

Whether you put the latex-suite files in /usr/share/vim/vimfiles or
in ~/.vim is pretty much up to you and whether or not you want them
available to other users.  I avoided discussing ~/.vim because I'm
not familiar with Macs and don't know how much of what works on
other Unixes works on OS X.

> I have seen this before, but am really not sure I solved it.  I
> have include a screenshot of the list of errors. 

Apparently the attachment didn't survive.

> Another question is when I put files in the vimfiles, do I just leave
> everything as it was unzipped?  So it will look something like:
> 
> /usr/share/vim/vimfiles/compiler
> /usr/share/vim/vimfiles/doc
> /usr/share/vim/vimfiles/ftplugin
> /usr/share/vim/vimfiles/indent
> /usr/share/vim/vimfiles/plugin
> 
> as well as the other files that come with the download?

Yes.

> If so, since I currently do not have a folder named vimfiles in
> this directory, how do I add it to the search path?

It doesn't need to be your shell's search path; it needs to be in
Vim's 'runtimepath', and it should already be there.  If you execute

    :set rtp?

the result should look something like this:

    runtimepath=~/.vim,/usr/share/vim/vimfiles,/usr/share/vim/vim70,/usr/share/vim/vimfiles/after,~/.vim/after

That came from a system running Aurora SPARC Linux, but from what
you've written so far, I would expect it to look similar on OS X.
The 'runtimepath' option tells Vim where to look for plugins just as
PATH tells the shell where to look for executables.  See

    :help rtp

One other thing.  You said you deleted ~/.vim.  Do you still have a
~/.vimrc?  Without that file, Vim may start in 'compatible' mode,
which causes it to behave more like vi than like vim.

> Thanks for the help

You're welcome.

Regards,
Gary

Re: [Vim-latex-devel] Errors with getting Latex going

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

Hi,

Thanks for the help so far.  So taking your advice, I decided to delete the
~/.vim directory and have run into another set of errors.

I have seen this before, but am really not sure I solved it.  I have include
a screenshot of the list of errors.

Another question is when I put files in the vimfiles, do I just leave
everything as it was unzipped?  So it will look something like:

/usr/share/vim/vimfiles/compiler
/usr/share/vim/vimfiles/doc
/usr/share/vim/vimfiles/ftplugin
/usr/share/vim/vimfiles/indent
/usr/share/vim/vimfiles/plugin

as well as the other files that come with the download?

If so, since I currently do not have a folder named vimfiles in this
directory, how do I add it to the search path?

Thanks for the help

-Dave

Re: [Vim-latex-devel] Errors with getting Latex going

[Gary J. <gar...@sp...>]

On 2010-05-14, Mario Santagiuliana <ma...@ma...> wrote:

> In data 14/5/2010 16:06:36, David Reed ha scritto:
> > I apologize if this is not the place for help, but if it is here is my
> > question...
> > 
> > I'm really new to vim and I would say the only reason I would like to use
> > it currently is to make writing latex a little more pleasurable.  I spend
> > most of my time in Mac OSX, and would like to get this going there.
> > 
> > To start on this road I downloaded MacVim.  I then found out MacOSX already
> > comes with Vim pre-installed and so ditched the MacVim effort for this one.
> > 
> > 
> > The first place where I am getting confused is that many places say that
> > there should be vim directory at '~/.vim'.  I didn't have one there so I
> > created one.
> > 
> > I then created a vimrc file there too and added all the files from the
> > latex-suite download there as well.
> > 
> > I then found there is also a vim folder at usr/share/vim, with two
> > sub-directories: vim70 and vim72.  I am not sure where the latex-suite
> > addons should go.
> > 
> > I'll end this first round of questioning here, thanks for any help.
> > 
> > -Dave

> Put your latex-suite files in your vim user folder.  If you have
> other users in your mac and you want to add latex-suite to this
> users you should put latex-suite files in your vim72 directory.

Don't put them in your vim72 directory.  That directory is for the
files that come with the Vim package you or your OS vendor installs.
The contents will be overwritten by any subsequent install of Vim in
that series and will be ignored by the Vim of any other series.

If you want to make latex-suite available to other users, put it in
/usr/share/vim/vimfiles.

You can read a little more about this here:

    :help vimfiles

Regards,
Gary

Re: [Vim-latex-devel] Errors with getting Latex going

[Mario S. <ma...@ma...>]

Put your latex-suite files in your vim user folder.
If you have other users in your mac and you want to add latex-suite to this users you should put 
latex-suite files in your vim72 directory.
vim70 is for vim version 7.0. vim72 is for vim 7.2 series.

In data 14/5/2010 16:06:36, David Reed ha scritto:
> I apologize if this is not the place for help, but if it is here is my
> question...
> 
> I'm really new to vim and I would say the only reason I would like to use
> it currently is to make writing latex a little more pleasurable.  I spend
> most of my time in Mac OSX, and would like to get this going there.
> 
> To start on this road I downloaded MacVim.  I then found out MacOSX already
> comes with Vim pre-installed and so ditched the MacVim effort for this one.
> 
> 
> The first place where I am getting confused is that many places say that
> there should be vim directory at '~/.vim'.  I didn't have one there so I
> created one.
> 
> I then created a vimrc file there too and added all the files from the
> latex-suite download there as well.
> 
> I then found there is also a vim folder at usr/share/vim, with two
> sub-directories: vim70 and vim72.  I am not sure where the latex-suite
> addons should go.
> 
> I'll end this first round of questioning here, thanks for any help.
> 
> -Dave
-- 
Mario Santagiuliana
www.marionline.it

[Vim-latex-devel] Errors with getting Latex going

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

I apologize if this is not the place for help, but if it is here is my
question...

I'm really new to vim and I would say the only reason I would like to use it
currently is to make writing latex a little more pleasurable.  I spend most
of my time in Mac OSX, and would like to get this going there.

To start on this road I downloaded MacVim.  I then found out MacOSX already
comes with Vim pre-installed and so ditched the MacVim effort for this one.


The first place where I am getting confused is that many places say that
there should be vim directory at '~/.vim'.  I didn't have one there so I
created one.

I then created a vimrc file there too and added all the files from the
latex-suite download there as well.

I then found there is also a vim folder at usr/share/vim, with two
sub-directories: vim70 and vim72.  I am not sure where the latex-suite
addons should go.

I'll end this first round of questioning here, thanks for any help.

-Dave

Re: [Vim-latex-devel] Strange symbols apprear instead of \

[Udo H. <udo...@we...>]

On Wed, May 12, 2010 at 11:36:30PM +0200, Mario Santagiuliana wrote:
> Vim and gvim version?
> I will look for this problem.

ii  vim            2:7.2.330-1    Vi IMproved - enhanced vi editor
ii  vim-gnome      2:7.2.330-1    Vi IMproved - enhanced vi editor - with GNOM
ii  vim-gtk        2:7.2.330-1    Vi IMproved - enhanced vi editor - with GTK2

On my system /usr/bin/gvim points to /etc/alternatives/gvim, which again points to /usr/bin/vim.gnome.

Thank you for your help. If you need any further information, please let me
know.

Btw: I also have some packages installed for Japanese language support. I am
not exactly sure, but maybe there is a relation to them.

Re: [Vim-latex-devel] Strange symbols apprear instead of \

[Mario S. <ma...@ma...>]

Vim and gvim version?
I will look for this problem.

In data 12/5/2010 04:45:15, Udo Hortian ha scritto:
> On Tue, May 11, 2010 at 07:33:39PM +0200, Mario Santagiuliana wrote:
> > Have you got a special vim or gvim configuration?
> 
> I replaced my .vimrc and .gvimrc with empty files and the same happens,
> but only after I turn on syntax highlighting. Without syntax
> highlighting this does not occur.
> 
> ---------------------------------------------------------------------------
> ---
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
-- 
Mario Santagiuliana
www.marionline.it

Re: [Vim-latex-devel] Strange symbols apprear instead of \

[Udo H. <udo...@we...>]

On Tue, May 11, 2010 at 07:33:39PM +0200, Mario Santagiuliana wrote:
> Have you got a special vim or gvim configuration?
I replaced my .vimrc and .gvimrc with empty files and the same happens,
but only after I turn on syntax highlighting. Without syntax
highlighting this does not occur.

Re: [Vim-latex-devel] Strange symbols apprear instead of \

[Mario S. <ma...@ma...>]

Have you got a special vim or gvim configuration?

In data 11/5/2010 03:11:23, Udo Hortian ha scritto:
> Dear vim-latexsuite developers and users,
> 
> I am happily using vim-latexsuite for quite a while and like it very
> much, although there are still a few things I would like to improve.
> 
> One thing that is annoying me recently is the following: Instead of "\"
> sometimes a strange symbol is shown. But it is just displayed as this
> and when I copy it, it appears as normal "\", so I took a screenshot
> that you can find here:
> 
> http://img3.imageshack.us/img3/2669/vimstrangesymbols.png
> 
> Sometimes also this appears:
> 
> http://img526.imageshack.us/img526/2873/vimstrangesymbols2.png
> 
> It appears only when I start gvim with a latex document. When I use vim
> this does not happen.
> 
> Also it does not happen all the time and changes depending on the
> position of my cursor. Sometimes I see the symbol from the first picture
> just if the cursor is located over this "\".
> 
> Do you have any hints what might cause this?
> 
> Best,
> Udo
> 
> ---------------------------------------------------------------------------
> ---
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
-- 
Mario Santagiuliana
www.marionline.it

Re: [Vim-latex-devel] Open files in \input

[Gary J. <gar...@sp...>]

On 2010-05-11, Udo Hortian <udo...@we...> wrote:
> Hello,
> 
> it would be convenient if one could easily open a file that is included
> in another using \input. Since the file one is editing may be located in
> a folder "far away" from the current one, this might be very convenient.
> Is there any way to do this using vim-latexsuite?

Have you looked at using Vim's gf and ^Wf commands?  They recognize
strings that represent file names and use the 'path' option to find
files in other directories.  See

    :help 22.3
    :help gf
    :help CTRL-W_f
    :help 'isfname'
    :help 'path'

HTH,
Gary