Sorry, I meant the vim manual. getcwd () is the function that determines
the current directory and my guess is also what directory the Makefile
should be in. What is the 'after directory'?


On 04/13/2010 02:26 PM, Yan Zhou wrote:
> They are not documented in the manual. The manual is rather incomplete, it's 
> a user manual and one has to check the source code to find the problem.
>
> However, I have used the after directory to overrule the vim-latex suite 
> behaviour.
>
> On 13 Apr 2010, at 08:47, LAG Grimminck wrote:
>
>   
>> Dear Yan,
>>
>> .. put your TESTED Makefile in the directory where you let your
>> vim-latex compile? Otherwise maybe you should check what vim-latex uses
>> as current working directory internally, check the manual for that I think.
>>
>> cheers,
>>
>> Dennis
>>
>> On 04/12/2010 08:06 PM, Yan Zhou wrote:
>>     
>>> Dear all,
>>>
>>> I have a question about the Tex_UseMakefile. Whatever value I set it, 
>>> either 1 or 0. The latex suite always define makeprg to whatever is defined 
>>> by the g:Tex_CompileRule_target setting. How can I disable this behaviour 
>>> and forbid latex suite to set the makeprg option?
>>>
>>> Many thanks in advance.
>>>
>>> Yan,
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Vim-latex-devel mailing list
>>> Vim-latex-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>>
>>>       
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim-latex-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>     
>   


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Reply via email to