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

[Vim-latex-devel] Using option -sourceposition with xdvi

[Jens M. <jen...@gm...>]

Hi,

I found a little problem when viewing dvi files using \ls. You only run
into this problem if your tex file starts with a digit.
>From the xdvi manpage (under -sourceposition):
"The  space  before  filename is only needed if the filename starts with
a digit. When the space is used, the argument needs to be encosed in
quotes to prevent the shell from misinterpreting the space as argument
separator."

That's why I think we should change
-sourceposition '.line('.').expand("%").' '
to
-sourceposition "'.line('.').' '.expand("%").'" '
in ftplugin/latex-suite/compiler.vim

Regards,
Jens

[Vim-latex-devel] tex indentation and commented lines

[Laurent G. <se...@gm...>]

Hi,
I use vim-latex-suite, and sometimes the indent is going wrong, I think it's
due to the way that commented line are used.

for this example :

\begin{itemize}
\item ldsfkjlfj
\item dsflkjqlfj
% fsdqlkjflsdjql lfdskjfljsd
\end{itemize}

the indentation of \end{itemize} is wrong (with the default indent/tex.vim
from latex-suite we get :
 \begin{itemize}
    \item ldsfkjlfj
    \item dsflkjqlfj
% fsdqlkjflsdjql lfdskjfljsd
\end{itemize}

so here is a little patch for indent/tex.vim that will provide the right
solution I think :
which is in this case :

\begin{itemize}
    \item ldsfkjlfj
    \item dsflkjqlfj
% fsdqlkjflsdjql lfdskjfljsd
\end{itemize}

(the comment line is indent more because of g_tex_indent_items, and I like
it)

so the patch is adding this after line 81 of indent/tex.vim :
while lnum > 0 && getline(lnum) =~ '^\s*%'
    let lnum = prevnonblank(lnum-1)
  endwhile

it's extracted from tex.vim by charles campbell:
  " if the current line doesn't begin with a '%', use its indent
  " (ie. skip over preceding comment lines)

hope this help, and hope this will be in the next latex-suite version :D.

NB: the form here :
http://vim-latex.sourceforge.net/index.php?subject=contact&title=Contactdoesn't
seems to work anymore.. (with google-chrome it doesn't works..)
- setog

Re: [Vim-latex-devel] Lots of "E117: Unknown function: IMAP" errors

[Tim M. <ti...@ti...>]

Alright issue resolved. Turned out some files failed to extract from the
archive without me noticing. Seems to be working flawlessly now. Sweet.

Thanks to Nicholas for helping me out.

Cheers,
TIm


--
http://timmolendijk.nl • http://twitter.com/timmolendijk


2010/1/10 Tim Molendijk <ti...@ti...>

> Hello,
>
> I tried installing Latex-Suite: vim-latex-1.8.23-20091230-r1079 with Vim
> 2:7.2.245-2ubuntu2.
>
> When starting up Vim with a .tex file, I get the following huge error
> listing. Then when I ignore these and continue, the file does have no syntax
> highlighting (until I manually set it via set ft=tex). Latex-Suite file
> menus in GVim are present. Configuration set according to
> http://vim-latex.sourceforge.net/documentation/latex-suite/recommended-settings.html
> .
>
> Don't have the slightest clue what might be causing all this. Don't know
> which features are working and which aren't (apart from what I already
> described in previous paragraph).
>
> Error detected while processing
> /home/tim/.vim/ftplugin/latex-suite/main.vim:
> line   50:
> E117: Unknown function: IMAP
> Error detected while processing function <SNR>35_Tex_SpecialMacros:
> line   23:
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> Error detected while processing function <SNR>35_Tex_EnvMacros:
> line   22:
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> Error detected while processing function <SNR>35_Tex_SpecialMacros:
> line   23:
> E117: Unknown function: IMAP
> Error detected while processing function <SNR>35_Tex_EnvMacros:
> line   22:
> E117: Unknown function: IMAP
> Error detected while processing function <SNR>35_Tex_SpecialMacros:
> line   23:
> E117: Unknown function: IMAP
> Error detected while processing function <SNR>35_Tex_EnvMacros:
> line   22:
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> Error detected while processing function <SNR>35_Tex_SpecialMacros:
> line   23:
> E117: Unknown function: IMAP
> Error detected while processing function <SNR>35_Tex_EnvMacros:
> line   22:
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> Error detected while processing function <SNR>35_Tex_SectionMacros:
> line    7:
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> Error detected while processing function <SNR>35_Tex_SpecialMacros:
> line   23:
> E117: Unknown function: IMAP
> Error detected while processing function <SNR>35_Tex_EnvMacros:
> line   22:
> E117: Unknown function: IMAP
> Error detected while processing function <SNR>35_Tex_SpecialMacros:
> line   23:
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> Error detected while processing function <SNR>37_Tex_FontFamily:
> line    7:
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> E117: Unknown function: IMAP
> Error detected while processing
> /home/tim/.vim/ftplugin/latex-suite/elementmacro
> s.vim:
> line  125:
> E117: Unknown function: IMAP
> Error detected while processing
> /home/tim/.vim/ftplugin/latex-suite/bibtex.vim:
> line  128:
> E117: Unknown function: IMAP
> line  129:
> E117: Unknown function: IMAP
> line  130:
> E117: Unknown function: IMAP
> line  131:
> E117: Unknown function: IMAP
>
> --
> http://timmolendijk.nl • http://twitter.com/timmolendijk
>

[Vim-latex-devel] Lots of "E117: Unknown function: IMAP" errors

[Tim M. <ti...@ti...>]

Hello,

I tried installing Latex-Suite: vim-latex-1.8.23-20091230-r1079 with Vim
2:7.2.245-2ubuntu2.

When starting up Vim with a .tex file, I get the following huge error
listing. Then when I ignore these and continue, the file does have no syntax
highlighting (until I manually set it via set ft=tex). Latex-Suite file
menus in GVim are present. Configuration set according to
http://vim-latex.sourceforge.net/documentation/latex-suite/recommended-settings.html
.

Don't have the slightest clue what might be causing all this. Don't know
which features are working and which aren't (apart from what I already
described in previous paragraph).

Error detected while processing
/home/tim/.vim/ftplugin/latex-suite/main.vim:
line   50:
E117: Unknown function: IMAP
Error detected while processing function <SNR>35_Tex_SpecialMacros:
line   23:
E117: Unknown function: IMAP
E117: Unknown function: IMAP
Error detected while processing function <SNR>35_Tex_EnvMacros:
line   22:
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
Error detected while processing function <SNR>35_Tex_SpecialMacros:
line   23:
E117: Unknown function: IMAP
Error detected while processing function <SNR>35_Tex_EnvMacros:
line   22:
E117: Unknown function: IMAP
Error detected while processing function <SNR>35_Tex_SpecialMacros:
line   23:
E117: Unknown function: IMAP
Error detected while processing function <SNR>35_Tex_EnvMacros:
line   22:
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
Error detected while processing function <SNR>35_Tex_SpecialMacros:
line   23:
E117: Unknown function: IMAP
Error detected while processing function <SNR>35_Tex_EnvMacros:
line   22:
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
Error detected while processing function <SNR>35_Tex_SectionMacros:
line    7:
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
Error detected while processing function <SNR>35_Tex_SpecialMacros:
line   23:
E117: Unknown function: IMAP
Error detected while processing function <SNR>35_Tex_EnvMacros:
line   22:
E117: Unknown function: IMAP
Error detected while processing function <SNR>35_Tex_SpecialMacros:
line   23:
E117: Unknown function: IMAP
E117: Unknown function: IMAP
Error detected while processing function <SNR>37_Tex_FontFamily:
line    7:
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
E117: Unknown function: IMAP
Error detected while processing
/home/tim/.vim/ftplugin/latex-suite/elementmacro
s.vim:
line  125:
E117: Unknown function: IMAP
Error detected while processing
/home/tim/.vim/ftplugin/latex-suite/bibtex.vim:
line  128:
E117: Unknown function: IMAP
line  129:
E117: Unknown function: IMAP
line  130:
E117: Unknown function: IMAP
line  131:
E117: Unknown function: IMAP

--
http://timmolendijk.nl • http://twitter.com/timmolendijk

Re: [Vim-latex-devel] Compiler failed to locate the source code.

[Ted P. <te...@te...>]

> for a likely explanation and some solutions. Because you're using
> Windows, solutions will be more difficult to implement. In your case,

Actually, if you want to give a shot, the "vimlatex.py" that is linked 
from that page may not be too difficult to get up and running in Windows 
if you have Python installed.

--Ted

-- 
Ted Pavlic <te...@te...>

   Please visit my 2009 d'Feet ALS walk page:
         http://web.alsa.org/goto/tedp
   My family appreciates your support in the fight to defeat ALS.

Re: [Vim-latex-devel] Compiler failed to locate the source code.

[Ted P. <te...@te...>]

Feng --

> I am newer to latex-suite, and I appreciate a lot for your help.!
> The version of the software I am using: Winxp SP3, gVim ver7.2, latest
> late-suite and MiTex 2.7
...
> My tex contains multiple files, root, cover, chap1, chap2,... I
> compile the root file.
> As expected, \ll runs well, 'Quickfix List window' appears after the
> compiling, and it locates the root.log when I click the error, but it
> does not locate the tex source file correctly.

	See:

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

for a likely explanation and some solutions. Because you're using 
Windows, solutions will be more difficult to implement. In your case, 
the easiest thing would be to consult the two links in the second 
"UPDATE" on that page. That is, see the note...

=====
UPDATE: Most recent implementations of LaTeX can be told to generate 
sanitized error (but not warning!!) messages automatically. See

"a description of how to modify Vim-LaTeX to use this feature"
http://linuxwisdom.blogspot.com/2007/08/fixing-latex-suites-jump-to-error.html

"a more general fix for Vim and LaTeX" (in "Comments" section of the link)
http://vim.wikia.com/wiki/A_better_interfacing_of_(La)TeX_with_the_quickfix_mode
=====

The downside of that fix is that it won't handle warning messages for you...

Alternatively, you could check out the subject of the first update -- 
"rubber." You should probably be able to get rubber working on your 
system. You could have Vim-LaTeX call rubber instead, and rubber should 
generate sanitized error (and warning?) messages that Vim can handle...


--Ted

-- 
Ted Pavlic <te...@te...>

   Please visit my 2009 d'Feet ALS walk page:
         http://web.alsa.org/goto/tedp
   My family appreciates your support in the fight to defeat ALS.

[Vim-latex-devel] Compiler failed to locate the source code.

[Xu, F. <fe...@uc...>]

Hi,

I am newer to latex-suite, and I appreciate a lot for your help.!
The version of the software I am using: Winxp SP3, gVim ver7.2, latest
late-suite and MiTex 2.7

My question is about the compiler in the the latex-suite, as mentioned
in the manual:

If you are using commonly used LaTeX tools, then you should be all set
as soon as you download and install Latex-Suite. In order to compile a
LaTeX file, simply press \ll while editing the file. This runs latex
on the current file and displays the errors in a |quickfix-window|
below the file being edited. You can then scroll through the errors
and press <enter> to be taken to the location of the corresponding
error.

My tex contains multiple files, root, cover, chap1, chap2,... I
compile the root file.
As expected, \ll runs well, 'Quickfix List window' appears after the
compiling, and it locates the root.log when I click the error, but it
does not locate the tex source file correctly.

Do I miss any setting for this?

And another wierd thing in the Quickfix List:
cover.tex|221 error| File `eps/acq-trad.eps' not found.
Actually, my cover.tex only has 26 lines.

Thanks a lot.

Feng

Re: [Vim-latex-devel] [PATCH] Fix sourcing of the .latexmain file

[Till M. <ope...@ti...>]

On Wed, Dec 16, 2009 at 02:59:27AM +0100, Björn Steinbrink wrote:
> There was a misplaced concatenation operator that broke the code. Should
> be in front of the function call, not inside the parentheses.

Thank you, the patch has been applied in changeset 1077.

Regards
Till

Re: [Vim-latex-devel] Shouldn't this list be on Vim.org's third party lists list?

[Till M. <ope...@ti...>]

Sorry for the noise, but I mistyped the vimonline support address in the
other mail, but I sent it again to the right address. I just wanted to
let you know in case you wonder.

Regards
Till

Re: [Vim-latex-devel] Shouldn't this list be on Vim.org's third party lists list?

[Till M. <ope...@ti...>]

Dear vimonline support,

On Wed, Dec 16, 2009 at 02:01:27PM -0500, Ted Pavlic wrote:
> http://www.vim.org/maillist.php
> 
> At the bottom of the page -- under "third party" lists. Shouldn't this 
> list be there too?

please add the vim-latex-devel mailing list to above mentioned list, if
you think it qualifies. The mailman info page is available here:

https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Btw. it would also be nice, if you could emphasize more that vim-latex
releases can be obtained from the SF.net dowload page instead of
downloading the stale versions attached to this page:
http://www.vim.org/scripts/script.php?script_id=475

There was at least one user that was confused about the page not being
updated any more.

Thank you
Till

Re: [Vim-latex-devel] Shouldn't this list be on Vim.org's third party lists list?

[Christian E. <bla...@gm...>]

* Ted Pavlic on Wednesday, December 16, 2009 at 14:01:27 -0500
> http://www.vim.org/maillist.php
> 
> At the bottom of the page -- under "third party" lists. Shouldn't this 
> list be there too?

Indeed it should!

c
-- 
_B A U S T E L L E N_ lesen! --->> http://www.blacktrash.org/baustellen/

[Vim-latex-devel] Shouldn't this list be on Vim.org's third party lists list?

[Ted P. <te...@te...>]

http://www.vim.org/maillist.php

At the bottom of the page -- under "third party" lists. Shouldn't this 
list be there too?

-- 
Ted Pavlic <te...@te...>

   Please visit my 2009 d'Feet ALS walk page:
         http://web.alsa.org/goto/tedp
   My family appreciates your support in the fight to defeat ALS.

[Vim-latex-devel] [PATCH] Fix sourcing of the .latexmain file

[Björn S. <B.S...@gm...>]

There was a misplaced concatenation operator that broke the code. Should
be in front of the function call, not inside the parentheses.
---
 vimfiles/ftplugin/latex-suite/texproject.vim |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/vimfiles/ftplugin/latex-suite/texproject.vim b/vimfiles/ftplugin/latex-suite/texproject.vim
index 3d9e9b9..5bc14a0 100644
--- a/vimfiles/ftplugin/latex-suite/texproject.vim
+++ b/vimfiles/ftplugin/latex-suite/texproject.vim
@@ -39,7 +39,7 @@ function! Tex_ProjectLoad()
 
 	if glob(Tex_GetMainFileName(':p').'.latexmain') != ''
 		call Tex_Debug("Tex_ProjectLoad: sourcing [".Tex_GetMainFileName().".latexmain]", "proj")
-		exec 'source 'fnameescape(.Tex_GetMainFileName().'.latexmain')
+		exec 'source '.fnameescape(Tex_GetMainFileName().'.latexmain')
 	endif
 	
 	exe 'cd '.s:origdir
-- 
1.6.6.rc2.6.g20b8b

[Vim-latex-devel] macros customization

[peng s. <sha...@gm...>]

Hi everyone. I met a little problem to customize the macros
"eqnarray*". I followed the instructions on the documentation

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

to paste

let g:Tex_Env_{'eqnarray*'} =
        \ "\\begin{eqnarray*}\<CR><++> &=& <++>\<CR>\\end{eqnarray*}<++>"

into my .vimrc. However when I start the vim I got the following error messages

Error detected while processing /home/shaopeng/.vimrc:
line  106:
E461: Illegal variable name: Tex_Env_eqnarray*
Press ENTER or type command to continue

Is there anything wrong? Thanks. :)

Peng

Re: [Vim-latex-devel] help for this latex project

[Ted P. <te...@te...>]

You most likely need not worry about that error. Those errors occur when 
you (for example) try to generate a font shape with macros like \emph{} 
and \textbf{} in a context where those modifiers don't exist. For 
example, your dissertation class might use a fancy font for the section 
titles. That fancy font may not include shapes for italics (\textit{} or 
\emph{}) or teletype typewritter (\texttt{}), and so if you try to use 
them in the section title, LaTeX will complain and will probably end up 
using the unmodified text.

The log will also tell you which file and which line is generating the 
error. (the line number will be near the error, but you may have to 
scroll up in the log to figure out which TeX file is causing the error) 
If you can find the line, you should be able to determine where the 
problem is. Just look for things like...

\section{This is some \texttt{text} and some other \emph{text} and some 
$math$ in a section title}

Those different font shapes (generated from \textit, \emph, and $..$ 
might be incompatible with the font used for your dissertation's section 
title.

--Ted



On 12/7/09 5:58 AM, YueJun Yin wrote:
> Thanks a lot.
> I have no idea with makefile. I just delete it from the folder and it
> works now. Yet I have warning:
> Font shape `U/lasy/m/n' in size<5.47603>  not available
> Font shape `U/lasy/m/n' in size<4.44003>  not available
> Any idea?
>
> On 12/07/2009 03:57 AM, Cédric Boutillier wrote:
>> Hi!
>>
>> I tried the files you indicated.
>> I also got no result by typing \ll from vim. But then I noticed in the
>> terminal the following message:
>>
>> make: *** No rule to make target `dvi'.  Stop.
>>
>> It seems that vim-latex detects the presence of the Makefile, and looks
>> for a rule "dvi" whenever it is asked to produce a dvi file. And there
>> is no such rule in your Makefile.
>>
>> However, changing the TTarget from dvi to pdf, and then typing \ll
>> produces a compiled pdf version of your document.
>>
>> So you could either modify the Makefile to add a "dvi" rule, or change
>> the variable TTarget from dvi to pdf.
>>
>> Best regards,
>>
>> 	Cedric
>>
>> On Sun, Dec 06, 2009 at 08:07:06PM -0600, yuejun yin wrote:
>>
>>> Well,
>>> MyDissertation.tex.latexmain is in the folder. No problem.
>>>
>>
>>> :!which latex returns /usr/bin/latex indicating it works well. I tested a
>>> simple multi-file latex projects. Everything runs perfectly.
>>>
>>
>>> \include is used in the main tex file (MyDissertation.tex).
>>>
>>
>>> Could you please try out the package and figure out the reason? Here is the
>>> link:
>>>
>>
>>> http://sgowtham.net/blog/files/20070329/MTUPhDTemplate_Linux.zip
>>>
>>
>>> This is very confusing problem. Thank you all.
>>>
>>
>>> On Sun, Dec 6, 2009 at 6:15 PM, Ted Pavlic<te...@te...>   wrote:
>>>
>>
>>>> Yue-Jun --
>>>>
>>>> [ on a slightly unrelated note, make sure your latexmain file is named
>>>> MyDissertation.latexmain ]
>>>>
>>>>          I suspect that LaTeX is not being run at all because it is not
>>>> located in a place where vim-latex expects it. Inside vim, try typing:
>>>>
>>>> :!which latex
>>>>
>>>> If latex is found in your PATH, then you should see the full path to your
>>>> latex executable. Otherwise, you'll see something like a blank line and then
>>>> "shell returned 1". If that occurs, verify that you have LaTeX installed on
>>>> your system. It is not packaged with vim-latex. It appears like you are
>>>> running on a Linux system; you should be able to install LaTeX with the
>>>> package manager that corresponds to your system.
>>>>
>>>>          Regarding those other files, your MyDissertation.tex should have
>>>> \input or \include lines that pull in your other tex files. When latex runs
>>>> on MyDissertation.tex, LaTeX will automatically pull those files in as
>>>> needed. LaTeX doesn't need to run on each file; it only runs on the main
>>>> file.
>>>>
>>>>          vim-latex will try to detect the circumstances when LaTeX needs to
>>>> run more than once. For example, if you have a table of contents in your
>>>> dissertation LaTeX won't be able to populate it on a single run. Instead, it
>>>> will record which sections are on which pages during the first run. During a
>>>> second run, those pages will be placed on the table of contents. If the
>>>> table of contents is very long, it will change those numbers, and so LaTeX
>>>> will run again to update the table of contents with the final page numbers.
>>>> Again, vim-latex will try to detect when to re-run LaTeX for this case.
>>>> Notice that it is not re-running LaTeX to handle the additional files. It's
>>>> re-running LaTeX because latex is designed to be a one-pass parsing engine.
>>>>
>>>>          Good luck! --
>>>>          Ted
>>>>
>>>>
>>>> On 12/6/09 6:30 PM, YueJun Yin wrote:
>>>>
>>>>
>>>>> Hi all
>>>>> I download a thesis template that contains more than one tex files. The
>>>>> included Make file works well. I added a latexmain file to the folder
>>>>> and tried to run \ll on the MyDissertation.tex in vim latex. It just
>>>>> says run 1 time. No dvi or log file was created. Could you please walk
>>>>> me through this? Thank you very much.
>>>>>
>>>>>
>>>>>
>>>> --
>>>> Ted Pavlic<te...@te...>
>>>>
>>>>    Please visit my 2009 d'Feet ALS walk page:
>>>>          http://web.alsa.org/goto/tedp
>>>>    My family appreciates your support in the fight to defeat ALS.
>>>>
>>>>
>>
>>> ------------------------------------------------------------------------------
>>> Join us December 9, 2009 for the Red Hat Virtual Experience,
>>> a free event focused on virtualization and cloud computing.
>>> Attend in-depth sessions from your desk. Your couch. Anywhere.
>>> http://p.sf.net/sfu/redhat-sfdev2dev
>>>
>>
>>> _______________________________________________
>>> Vim-latex-devel mailing list
>>> Vim...@li...
>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>>
>>
>>
>

-- 
Ted Pavlic <te...@te...>

   Please visit my 2009 d'Feet ALS walk page:
         http://web.alsa.org/goto/tedp
   My family appreciates your support in the fight to defeat ALS.

Re: [Vim-latex-devel] help for this latex project

[Cédric B. <ced...@gm...>]

On Mon, Dec 07, 2009 at 04:58:50AM -0600, YueJun Yin wrote:
> Yet I have warning:
> Font shape `U/lasy/m/n' in size <5.47603> not available
> Font shape `U/lasy/m/n' in size <4.44003> not available
> Any idea?

Maybe 
	http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontunavail
will give you more information about what is going on.

with best regards,

	Cedric.

Re: [Vim-latex-devel] help for this latex project

[YueJun Y. <yj...@gm...>]

Thanks a lot.
I have no idea with makefile. I just delete it from the folder and it 
works now. Yet I have warning:
Font shape `U/lasy/m/n' in size <5.47603> not available
Font shape `U/lasy/m/n' in size <4.44003> not available
Any idea?

On 12/07/2009 03:57 AM, Cédric Boutillier wrote:
> Hi!
>
> I tried the files you indicated.
> I also got no result by typing \ll from vim. But then I noticed in the
> terminal the following message:
>
> make: *** No rule to make target `dvi'.  Stop.
>
> It seems that vim-latex detects the presence of the Makefile, and looks
> for a rule "dvi" whenever it is asked to produce a dvi file. And there
> is no such rule in your Makefile.
>
> However, changing the TTarget from dvi to pdf, and then typing \ll
> produces a compiled pdf version of your document.
>
> So you could either modify the Makefile to add a "dvi" rule, or change
> the variable TTarget from dvi to pdf.
>
> Best regards,
>
> 	Cedric
>
> On Sun, Dec 06, 2009 at 08:07:06PM -0600, yuejun yin wrote:
>    
>> Well,
>> MyDissertation.tex.latexmain is in the folder. No problem.
>>      
>    
>> :!which latex returns /usr/bin/latex indicating it works well. I tested a
>> simple multi-file latex projects. Everything runs perfectly.
>>      
>    
>> \include is used in the main tex file (MyDissertation.tex).
>>      
>    
>> Could you please try out the package and figure out the reason? Here is the
>> link:
>>      
>    
>> http://sgowtham.net/blog/files/20070329/MTUPhDTemplate_Linux.zip
>>      
>    
>> This is very confusing problem. Thank you all.
>>      
>    
>> On Sun, Dec 6, 2009 at 6:15 PM, Ted Pavlic<te...@te...>  wrote:
>>      
>    
>>> Yue-Jun --
>>>
>>> [ on a slightly unrelated note, make sure your latexmain file is named
>>> MyDissertation.latexmain ]
>>>
>>>         I suspect that LaTeX is not being run at all because it is not
>>> located in a place where vim-latex expects it. Inside vim, try typing:
>>>
>>> :!which latex
>>>
>>> If latex is found in your PATH, then you should see the full path to your
>>> latex executable. Otherwise, you'll see something like a blank line and then
>>> "shell returned 1". If that occurs, verify that you have LaTeX installed on
>>> your system. It is not packaged with vim-latex. It appears like you are
>>> running on a Linux system; you should be able to install LaTeX with the
>>> package manager that corresponds to your system.
>>>
>>>         Regarding those other files, your MyDissertation.tex should have
>>> \input or \include lines that pull in your other tex files. When latex runs
>>> on MyDissertation.tex, LaTeX will automatically pull those files in as
>>> needed. LaTeX doesn't need to run on each file; it only runs on the main
>>> file.
>>>
>>>         vim-latex will try to detect the circumstances when LaTeX needs to
>>> run more than once. For example, if you have a table of contents in your
>>> dissertation LaTeX won't be able to populate it on a single run. Instead, it
>>> will record which sections are on which pages during the first run. During a
>>> second run, those pages will be placed on the table of contents. If the
>>> table of contents is very long, it will change those numbers, and so LaTeX
>>> will run again to update the table of contents with the final page numbers.
>>> Again, vim-latex will try to detect when to re-run LaTeX for this case.
>>> Notice that it is not re-running LaTeX to handle the additional files. It's
>>> re-running LaTeX because latex is designed to be a one-pass parsing engine.
>>>
>>>         Good luck! --
>>>         Ted
>>>
>>>
>>> On 12/6/09 6:30 PM, YueJun Yin wrote:
>>>
>>>        
>>>> Hi all
>>>> I download a thesis template that contains more than one tex files. The
>>>> included Make file works well. I added a latexmain file to the folder
>>>> and tried to run \ll on the MyDissertation.tex in vim latex. It just
>>>> says run 1 time. No dvi or log file was created. Could you please walk
>>>> me through this? Thank you very much.
>>>>
>>>>
>>>>          
>>> --
>>> Ted Pavlic<te...@te...>
>>>
>>>   Please visit my 2009 d'Feet ALS walk page:
>>>         http://web.alsa.org/goto/tedp
>>>   My family appreciates your support in the fight to defeat ALS.
>>>
>>>        
>    
>> ------------------------------------------------------------------------------
>> Join us December 9, 2009 for the Red Hat Virtual Experience,
>> a free event focused on virtualization and cloud computing.
>> Attend in-depth sessions from your desk. Your couch. Anywhere.
>> http://p.sf.net/sfu/redhat-sfdev2dev
>>      
>    
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>      
>
>    

-- 
Yue-Jun Yin (Eugene)
PhD Candidate
Civil&  Environmental Engineering Dept.
Michigan Tech University
1400 Townsend Dr.
Houghton, MI 49931 USA
http://www.cee.mtu.edu/~yuejuny/

Re: [Vim-latex-devel] help for this latex project

[Cédric B. <ced...@gm...>]

Hi!

I tried the files you indicated.
I also got no result by typing \ll from vim. But then I noticed in the
terminal the following message:

make: *** No rule to make target `dvi'.  Stop.

It seems that vim-latex detects the presence of the Makefile, and looks
for a rule "dvi" whenever it is asked to produce a dvi file. And there
is no such rule in your Makefile.

However, changing the TTarget from dvi to pdf, and then typing \ll
produces a compiled pdf version of your document.

So you could either modify the Makefile to add a "dvi" rule, or change
the variable TTarget from dvi to pdf.

Best regards,

	Cedric

On Sun, Dec 06, 2009 at 08:07:06PM -0600, yuejun yin wrote:
> Well,
> MyDissertation.tex.latexmain is in the folder. No problem.

> :!which latex returns /usr/bin/latex indicating it works well. I tested a
> simple multi-file latex projects. Everything runs perfectly.

> \include is used in the main tex file (MyDissertation.tex).

> Could you please try out the package and figure out the reason? Here is the
> link:

> http://sgowtham.net/blog/files/20070329/MTUPhDTemplate_Linux.zip

> This is very confusing problem. Thank you all.

> On Sun, Dec 6, 2009 at 6:15 PM, Ted Pavlic <te...@te...> wrote:

> > Yue-Jun --
> >
> > [ on a slightly unrelated note, make sure your latexmain file is named
> > MyDissertation.latexmain ]
> >
> >        I suspect that LaTeX is not being run at all because it is not
> > located in a place where vim-latex expects it. Inside vim, try typing:
> >
> > :!which latex
> >
> > If latex is found in your PATH, then you should see the full path to your
> > latex executable. Otherwise, you'll see something like a blank line and then
> > "shell returned 1". If that occurs, verify that you have LaTeX installed on
> > your system. It is not packaged with vim-latex. It appears like you are
> > running on a Linux system; you should be able to install LaTeX with the
> > package manager that corresponds to your system.
> >
> >        Regarding those other files, your MyDissertation.tex should have
> > \input or \include lines that pull in your other tex files. When latex runs
> > on MyDissertation.tex, LaTeX will automatically pull those files in as
> > needed. LaTeX doesn't need to run on each file; it only runs on the main
> > file.
> >
> >        vim-latex will try to detect the circumstances when LaTeX needs to
> > run more than once. For example, if you have a table of contents in your
> > dissertation LaTeX won't be able to populate it on a single run. Instead, it
> > will record which sections are on which pages during the first run. During a
> > second run, those pages will be placed on the table of contents. If the
> > table of contents is very long, it will change those numbers, and so LaTeX
> > will run again to update the table of contents with the final page numbers.
> > Again, vim-latex will try to detect when to re-run LaTeX for this case.
> > Notice that it is not re-running LaTeX to handle the additional files. It's
> > re-running LaTeX because latex is designed to be a one-pass parsing engine.
> >
> >        Good luck! --
> >        Ted
> >
> >
> > On 12/6/09 6:30 PM, YueJun Yin wrote:
> >
> >> Hi all
> >> I download a thesis template that contains more than one tex files. The
> >> included Make file works well. I added a latexmain file to the folder
> >> and tried to run \ll on the MyDissertation.tex in vim latex. It just
> >> says run 1 time. No dvi or log file was created. Could you please walk
> >> me through this? Thank you very much.
> >>
> >>
> > --
> > Ted Pavlic <te...@te...>
> >
> >  Please visit my 2009 d'Feet ALS walk page:
> >        http://web.alsa.org/goto/tedp
> >  My family appreciates your support in the fight to defeat ALS.
> >

> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing. 
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev

> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel


-- 
Cédric Boutillier
Maître de conférences
LPMA - Université Pierre et Marie Curie

Re: [Vim-latex-devel] help for this latex project

[YueJun Y. <yj...@gm...>]

Mike
Thank you. It is awesome. It remove Makefile from the folder and found 
\ll works. Got the same problems as what you got.

As I mentioned in the original email, Makefile works well in the shell.
On 12/06/2009 10:06 PM, Mike Richman wrote:
> Yue-Jun,
>
> I don't know if this will be very helpful, but I downloaded the
> template and added MyDissertation.tex.latexmain.  With no further
> changes, it compiles with only this warning: "Index.tex|| LaTeX Font
> Warning: Size substitutions with differences".
>
> What Ted said about vim-latex trying to detect the number and order of
> runs is correct; however, in the presence of a Makefile, vim-latex
> will defer to that for the compilation rules.  On my system, with the
> Makefile from the template still in place, vim-latex says it only is
> doing one run because it is just running make.  If I rename or delete
> Makefile, vim-latex correctly runs all the compilation steps and
> builds the final pdf (with exactly the same warning message at the
> end).
>
> Have you tried simply running "make" from the shell?
>
> -Mike
>
> On Sun, Dec 6, 2009 at 9:07 PM, yuejun yin<yj...@gm...>  wrote:
>    
>> Well,
>> MyDissertation.tex.latexmain is in the folder. No problem.
>>
>> :!which latex returns /usr/bin/latex indicating it works well. I tested a
>> simple multi-file latex projects. Everything runs perfectly.
>>
>> \include is used in the main tex file (MyDissertation.tex).
>>
>> Could you please try out the package and figure out the reason? Here is the
>> link:
>>
>> http://sgowtham.net/blog/files/20070329/MTUPhDTemplate_Linux.zip
>>
>> This is very confusing problem. Thank you all.
>>
>> On Sun, Dec 6, 2009 at 6:15 PM, Ted Pavlic<te...@te...>  wrote:
>>      
>>> Yue-Jun --
>>>
>>> [ on a slightly unrelated note, make sure your latexmain file is named
>>> MyDissertation.latexmain ]
>>>
>>>         I suspect that LaTeX is not being run at all because it is not
>>> located in a place where vim-latex expects it. Inside vim, try typing:
>>>
>>> :!which latex
>>>
>>> If latex is found in your PATH, then you should see the full path to your
>>> latex executable. Otherwise, you'll see something like a blank line and then
>>> "shell returned 1". If that occurs, verify that you have LaTeX installed on
>>> your system. It is not packaged with vim-latex. It appears like you are
>>> running on a Linux system; you should be able to install LaTeX with the
>>> package manager that corresponds to your system.
>>>
>>>         Regarding those other files, your MyDissertation.tex should have
>>> \input or \include lines that pull in your other tex files. When latex runs
>>> on MyDissertation.tex, LaTeX will automatically pull those files in as
>>> needed. LaTeX doesn't need to run on each file; it only runs on the main
>>> file.
>>>
>>>         vim-latex will try to detect the circumstances when LaTeX needs to
>>> run more than once. For example, if you have a table of contents in your
>>> dissertation LaTeX won't be able to populate it on a single run. Instead, it
>>> will record which sections are on which pages during the first run. During a
>>> second run, those pages will be placed on the table of contents. If the
>>> table of contents is very long, it will change those numbers, and so LaTeX
>>> will run again to update the table of contents with the final page numbers.
>>> Again, vim-latex will try to detect when to re-run LaTeX for this case.
>>> Notice that it is not re-running LaTeX to handle the additional files. It's
>>> re-running LaTeX because latex is designed to be a one-pass parsing engine.
>>>
>>>         Good luck! --
>>>         Ted
>>>
>>> On 12/6/09 6:30 PM, YueJun Yin wrote:
>>>        
>>>> Hi all
>>>> I download a thesis template that contains more than one tex files. The
>>>> included Make file works well. I added a latexmain file to the folder
>>>> and tried to run \ll on the MyDissertation.tex in vim latex. It just
>>>> says run 1 time. No dvi or log file was created. Could you please walk
>>>> me through this? Thank you very much.
>>>>
>>>>          
>>> --
>>> Ted Pavlic<te...@te...>
>>>
>>>   Please visit my 2009 d'Feet ALS walk page:
>>>         http://web.alsa.org/goto/tedp
>>>   My family appreciates your support in the fight to defeat ALS.
>>>        
>>
>> ------------------------------------------------------------------------------
>> Join us December 9, 2009 for the Red Hat Virtual Experience,
>> a free event focused on virtualization and cloud computing.
>> Attend in-depth sessions from your desk. Your couch. Anywhere.
>> http://p.sf.net/sfu/redhat-sfdev2dev
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>
>>
>>      

-- 
Yue-Jun Yin (Eugene)
PhD Candidate
Civil&  Environmental Engineering Dept.
Michigan Tech University
1400 Townsend Dr.
Houghton, MI 49931 USA
http://www.cee.mtu.edu/~yuejuny/

Re: [Vim-latex-devel] help for this latex project

[yuejun y. <yj...@gm...>]

Well,
MyDissertation.tex.latexmain is in the folder. No problem.

:!which latex returns /usr/bin/latex indicating it works well. I tested a
simple multi-file latex projects. Everything runs perfectly.

\include is used in the main tex file (MyDissertation.tex).

Could you please try out the package and figure out the reason? Here is the
link:

http://sgowtham.net/blog/files/20070329/MTUPhDTemplate_Linux.zip

This is very confusing problem. Thank you all.

On Sun, Dec 6, 2009 at 6:15 PM, Ted Pavlic <te...@te...> wrote:

> Yue-Jun --
>
> [ on a slightly unrelated note, make sure your latexmain file is named
> MyDissertation.latexmain ]
>
>        I suspect that LaTeX is not being run at all because it is not
> located in a place where vim-latex expects it. Inside vim, try typing:
>
> :!which latex
>
> If latex is found in your PATH, then you should see the full path to your
> latex executable. Otherwise, you'll see something like a blank line and then
> "shell returned 1". If that occurs, verify that you have LaTeX installed on
> your system. It is not packaged with vim-latex. It appears like you are
> running on a Linux system; you should be able to install LaTeX with the
> package manager that corresponds to your system.
>
>        Regarding those other files, your MyDissertation.tex should have
> \input or \include lines that pull in your other tex files. When latex runs
> on MyDissertation.tex, LaTeX will automatically pull those files in as
> needed. LaTeX doesn't need to run on each file; it only runs on the main
> file.
>
>        vim-latex will try to detect the circumstances when LaTeX needs to
> run more than once. For example, if you have a table of contents in your
> dissertation LaTeX won't be able to populate it on a single run. Instead, it
> will record which sections are on which pages during the first run. During a
> second run, those pages will be placed on the table of contents. If the
> table of contents is very long, it will change those numbers, and so LaTeX
> will run again to update the table of contents with the final page numbers.
> Again, vim-latex will try to detect when to re-run LaTeX for this case.
> Notice that it is not re-running LaTeX to handle the additional files. It's
> re-running LaTeX because latex is designed to be a one-pass parsing engine.
>
>        Good luck! --
>        Ted
>
>
> On 12/6/09 6:30 PM, YueJun Yin wrote:
>
>> Hi all
>> I download a thesis template that contains more than one tex files. The
>> included Make file works well. I added a latexmain file to the folder
>> and tried to run \ll on the MyDissertation.tex in vim latex. It just
>> says run 1 time. No dvi or log file was created. Could you please walk
>> me through this? Thank you very much.
>>
>>
> --
> Ted Pavlic <te...@te...>
>
>  Please visit my 2009 d'Feet ALS walk page:
>        http://web.alsa.org/goto/tedp
>  My family appreciates your support in the fight to defeat ALS.
>

Re: [Vim-latex-devel] help for this latex project

[Ted P. <te...@te...>]

Yue-Jun --

[ on a slightly unrelated note, make sure your latexmain file is named 
MyDissertation.latexmain ]

	I suspect that LaTeX is not being run at all because it is not located 
in a place where vim-latex expects it. Inside vim, try typing:

:!which latex

If latex is found in your PATH, then you should see the full path to 
your latex executable. Otherwise, you'll see something like a blank line 
and then "shell returned 1". If that occurs, verify that you have LaTeX 
installed on your system. It is not packaged with vim-latex. It appears 
like you are running on a Linux system; you should be able to install 
LaTeX with the package manager that corresponds to your system.

	Regarding those other files, your MyDissertation.tex should have \input 
or \include lines that pull in your other tex files. When latex runs on 
MyDissertation.tex, LaTeX will automatically pull those files in as 
needed. LaTeX doesn't need to run on each file; it only runs on the main 
file.

	vim-latex will try to detect the circumstances when LaTeX needs to run 
more than once. For example, if you have a table of contents in your 
dissertation LaTeX won't be able to populate it on a single run. 
Instead, it will record which sections are on which pages during the 
first run. During a second run, those pages will be placed on the table 
of contents. If the table of contents is very long, it will change those 
numbers, and so LaTeX will run again to update the table of contents 
with the final page numbers. Again, vim-latex will try to detect when to 
re-run LaTeX for this case. Notice that it is not re-running LaTeX to 
handle the additional files. It's re-running LaTeX because latex is 
designed to be a one-pass parsing engine.

	Good luck! --
	Ted

On 12/6/09 6:30 PM, YueJun Yin wrote:
> Hi all
> I download a thesis template that contains more than one tex files. The
> included Make file works well. I added a latexmain file to the folder
> and tried to run \ll on the MyDissertation.tex in vim latex. It just
> says run 1 time. No dvi or log file was created. Could you please walk
> me through this? Thank you very much.
>

-- 
Ted Pavlic <te...@te...>

   Please visit my 2009 d'Feet ALS walk page:
         http://web.alsa.org/goto/tedp
   My family appreciates your support in the fight to defeat ALS.

[Vim-latex-devel] help for this latex project

[YueJun Y. <yj...@gm...>]

Hi all
I download a thesis template that contains more than one tex files. The 
included Make file works well. I added a latexmain file to the folder 
and tried to run \ll on the MyDissertation.tex in vim latex. It just 
says run 1 time. No dvi or log file was created. Could you please walk 
me through this? Thank you very much.

-- 
Yue-Jun Yin (Eugene)
PhD Candidate
Civil&  Environmental Engineering Dept.
Michigan Tech University
1400 Townsend Dr.
Houghton, MI 49931 USA
http://www.cee.mtu.edu/~yuejuny/

Re: [Vim-latex-devel] Auto-complete error-list for citations

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

Hi,

I think I have a problem that can be related to this. I inscribed at
the mailing list yesterday, I hope I'm in the right place!

In my case the \cite autocompletion does open the correct window with
the bibliography list, but once an entry is selected, pressing enter
does not fill the \cite command. On the contrary, for \ref the same
method is working.

I'm using MacOSX Snow Leopard, Vim 7.2 and the latest build of latex
suite (1.5-20091002-r1074).
The same problem arises with all versions (r1060,r1068,r1069) and I
think the first time it appeared was after updating to Snow Leopard,
but I'm not sure about this.

I also noticed that

has('macunix')

has to be modified into

has('unix')

but then it conflicts with the unix version (ex: xdvi instead of
Preview as a pdf viewer).

Thanks for any suggestion.

Gianluca

2009/12/1 John Healy <ex...@ya...>:
> Hi there,
>
> I am having an auto-complete problem that I don't think has been mentioned
> before (or at least I couldn't find it in the archives).
>
> The problem is that when pressing <F9> for citations, the user is presented
> with an error list as opposed to the outline windows you would expect.  The
> error list indicates that the problem is caused by the first line of each
> bibliographic entry in the .bib file.  I am confident that is not an syntax
> error in the .bib file as I have used colleagues' files that are known to
> work.  It might also be useful to point out that it work corrects for \ref
> completion.
>
> I am using CentOS 4.8, with Vim 6.3.  Also, I am using the latest build of
> the latex suite (1.5-20091002-r1074).
>
> Apologies if this has been addressed before.
>
> John
>
>
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing.
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>



-- 
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] Auto-complete error-list for citations

[John H. <ex...@ya...>]

Hi there,

I am having an auto-complete problem that I don't think has been mentioned
before (or at least I couldn't find it in the archives).

The problem is that when pressing <F9> for citations, the user is presented
with an error list as opposed to the outline windows you would expect.  The
error list indicates that the problem is caused by the first line of each
bibliographic entry in the .bib file.  I am confident that is not an syntax
error in the .bib file as I have used colleagues' files that are known to
work.  It might also be useful to point out that it work corrects for \ref
completion.

I am using CentOS 4.8, with Vim 6.3.  Also, I am using the latest build of
the latex suite (1.5-20091002-r1074).

Apologies if this has been addressed before.

John

Re: [Vim-latex-devel] [Question] Bibtex compiling

[Ted P. <te...@te...>]

There is intelligence in the build scripts inside vim-latex that will 
cause it to call BibTeX as needed. So, for most builds, \ll should be 
all you need.

--Ted

On 11/26/09 12:24 PM, Hao Wen wrote:
> Hi there:
>
> I am trying to compile *.bib file in latex-suite. The normal procedure
> in latex is:
> latex filename ->  bibtex filename ->  latex filename ->  latex filename
>
> I know I can use \ll for the "latex filename" operation, but what is it
> for the "bibtex filename" ?
>
> Thanks!
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

-- 
Ted Pavlic <te...@te...>

   Please visit my 2009 d'Feet ALS walk page:
         http://web.alsa.org/goto/tedp
   My family appreciates your support in the fight to defeat ALS.