> 1. After compiling my main.tex in dvi format using \ll I can not
> visualize the corresponding dvi file using the \lv command. There is
> a ":call Tex_View Latex()" message that appears in the command-line
> window but nothing happen. I did not change any default settings and
> I am using svn version 1050 of latex-suite. Note that this problem
> only occurs in gvim. The \lv command works great in plain vim.

What operating system? That's key.

You may need to put a

        setsid

in front of your g:Tex_ViewRule_dvi command. I bet your viewer is 
getting killed immediately after executing.

> 2. Following suggestions in latex-suite.txt I set up a directory tree
> to split my project in several input'ed files. In my
> main.tex.latexmain file I wrote: let g:Tex_BIBINPUTS = '~/thesis'
> since my main.tex and bibli.bib files are located there and I want
> the \cite completion command (F9) to work when I am editing, say,
> something in a subdirectory of 'thesis'. For example, this works fine
> if I start editing a file likewise "vim intro/intro.tex" but will not
> work if I am already in 'intro' and do "vim intro.tex". How can I fix
> that?

I wouldn't hold my breath for this feature. LaTeX itself must be used 
with caution when you are editing files in subdirectories (in 
particular, \input and \include may not work how you expect when they're 
used in a file within a subdirectory).

The BIBINPUTS and TEXINPUTS variables are meant to be used in cases 
where you are including from sources outside of the current project 
(e.g., in some central custom place where you store a master 
bibliography database or some custom packages you use everywhere). 
They're not meant to point toward an individual project's files.

THAT BEING SAID, what happens when you issue an \ll in that 
subdirectory? Does it build on the main file (which is down a directory) 
or does it build on the file you're editing? That is, does it appear 
like LaTeX's build process can find the "latexmain" file even though the 
other processes cannot? If the build process can find it, then it's 
reasonable to believe that the other processes can be easily patched to 
behave as expected.

--Ted

-- 
Ted Pavlic <t...@tedpavlic.com>

   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.

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects
_______________________________________________
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Reply via email to