Thread: [Vim-latex-devel] Errors with getting Latex going
Brought to you by:
srinathava,
tmaas
Menu
▾
▴
vim-latex-devel
|
From: David R. <dav...@gm...> - 2010-05-14 14:07:04
|
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 |
|
From: Mario S. <ma...@ma...> - 2010-05-14 15:44:10
|
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 |
|
From: Gary J. <gar...@sp...> - 2010-05-14 16:22:19
|
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
|
|
From: David R. <dav...@gm...> - 2010-05-14 23:08:34
|
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 |
|
From: Gary J. <gar...@sp...> - 2010-05-14 23:48:24
|
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
|
|
From: David R. <dav...@gm...> - 2010-05-15 00:38:28
|
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
|
|
From: Gary J. <gar...@sp...> - 2010-05-15 01:12:43
|
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
|
|
From: David R. <dav...@gm...> - 2010-05-15 01:22:41
|
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
>
|
|
From: David R. <dav...@gm...> - 2010-05-16 03:35:32
|
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
>
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X