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

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

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

> Isn't it better to make blah.latexmain a configuration file, so that it
> may contain

blah.latexmain is already a 'configuration file'. It gets :sourced 
whenenver it is found.

So you could already put in it something like...

let g:jobname=whatever

and have each \l* command respond to g:jobname if found. So that's 
another way it could be done.

--Ted

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

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

[Aditya M. <ad...@um...>]

On Tue, 15 Feb 2011, Ted Pavlic wrote:

> (I guess someone(?) could add a feature that looks for "blah.jobname"
> files that function similar to "blah.latexmain" but sets up the right
> jobname instead...)

Isn't it better to make blah.latexmain a configuration file, so that it 
may contain

jobname=whatever
output-directory=./tmp

Aditya

Re: [Vim-latex-devel] Multiple file latex projects, finds correct filename but doesn't compile in right directory?

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

>> Does eclim do much for you while in LaTeX? Perhaps you could setup an
>> autocmd to not load eclim when you're in a .tex file.
>>
> I've already spoken with them, they know the issue and have fixed it
> upstream, but the specific fix is not released yet. There's a workaround
> for now in .vimrc:-
>
> let g:EclimMakeLCD = 0

If it takes them a long time to fix that, then perhaps that should be 
added to an FAQ somewhere.

--Ted

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

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

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

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

> Testing this out, I notice that if I use -jobname, \lv will complain
> that a file is not found (foo.tex producing bar.dvi, of course \lv looks
> for foo.dvi). Can this be dealt with (changing the argument sent to
> g:Tex_ViewRule_dvi)?

I have a feeling you should look at:

g:Tex_ViewRuleComplete_dvi

which takes precedence over the normal ViewRule. It is exected "as-is" 
(except for replacing any $*'s).

So you could set g:Tex_ViewRuleComplete_dvi for your particular project 
to use the right jobname. Otherwise, it would be difficult for vim-latex 
to figure out the right jobname.

(I guess someone(?) could add a feature that looks for "blah.jobname" 
files that function similar to "blah.latexmain" but sets up the right 
jobname instead...)

--Ted

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

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

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

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

> *tangentially, I recall with some other apps I tried they would
> overwrite symlinks, I guess its to do with how they access the file?*

Yep. Some apps will unlink (i.e., delete) the file and re-create it. 
pdflatex does not do that; it overwrites whatever is there (and thus 
follows the symlink). Among other things, that helps to ensure that 
autorefreshing works in more PDF viewers.

--Ted


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

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

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

[Ng Oon-Ee <ng...@gm...>]

On Wed, 2011-02-16 at 11:10 +0800, Ng Oon-Ee wrote:
> On Tue, 2011-02-15 at 22:02 -0500, Ted Pavlic wrote:
> > >> ln -sf tmp/foo.pdf
> > > Yes, I did think of that, but the symlink will always exist even if the
> > > file does not =). Its plenty good enough though, so that's probably what
> > > I'll use going forward.
> > 
> > Well, if you plan on keeping that tmp directory around for more than a 
> > few builds, the symlink:
> > 
> > cd tmp
> > ln -sf ../foo.pdf
> > 
> > works just as well, but the "foo.pdf" that shows up in your main 
> > directory isn't a symlink. Maybe that's a better fit?
> > 
> > --Ted
> > 
> If it stays around a while, both ways work =). I suppose it WOULD stay
> around a while though, so not a big deal.
> 
> *tangentially, I recall with some other apps I tried they would
> overwrite symlinks, I guess its to do with how they access the file?*
> 
Testing this out, I notice that if I use -jobname, \lv will complain
that a file is not found (foo.tex producing bar.dvi, of course \lv looks
for foo.dvi). Can this be dealt with (changing the argument sent to
g:Tex_ViewRule_dvi)?

Re: [Vim-latex-devel] Multiple file latex projects, finds correct filename but doesn't compile in right directory?

[Ng Oon-Ee <ng...@gm...>]

On Tue, 2011-02-15 at 22:07 -0500, Ted Pavlic wrote:
> > However, moving away ~/.vim/eclim.vim (a file used by eclim, as I've
> > mentioned), I see correct behaviour. I'm attaching it here, 170 lines.
> > It does modify runtimepath and basedir, which I'm guessing is what could
> > be affecting the behaviour.
> 
> Well, AFAIK, eclim is a beast, isn't it? I don't have it installed, but 
> I see that that eclim.vim sources lots of other eclim files that may be 
> causing the problem.
> 
> If I had to guess, eclim is constantly sitting in the background 
> managing the current directory, and so there's the classical problem 
> with concurrency in software. It's possible that whenever vim-latex 
> changes the directory and the shells out to latex, eclim takes over and 
> resets the directory...
> 
> So you might want to talk to the eclim folks about what they might 
> suggest (perhaps they'll suggest having Eclipse do your building for 
> you...<?>).
> 
> Does eclim do much for you while in LaTeX? Perhaps you could setup an 
> autocmd to not load eclim when you're in a .tex file.
> 
> --Ted
> 
I've already spoken with them, they know the issue and have fixed it
upstream, but the specific fix is not released yet. There's a workaround
for now in .vimrc:-

let g:EclimMakeLCD = 0

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

[Ng Oon-Ee <ng...@gm...>]

On Tue, 2011-02-15 at 22:02 -0500, Ted Pavlic wrote:
> >> ln -sf tmp/foo.pdf
> > Yes, I did think of that, but the symlink will always exist even if the
> > file does not =). Its plenty good enough though, so that's probably what
> > I'll use going forward.
> 
> Well, if you plan on keeping that tmp directory around for more than a 
> few builds, the symlink:
> 
> cd tmp
> ln -sf ../foo.pdf
> 
> works just as well, but the "foo.pdf" that shows up in your main 
> directory isn't a symlink. Maybe that's a better fit?
> 
> --Ted
> 
If it stays around a while, both ways work =). I suppose it WOULD stay
around a while though, so not a big deal.

*tangentially, I recall with some other apps I tried they would
overwrite symlinks, I guess its to do with how they access the file?*

Re: [Vim-latex-devel] Multiple file latex projects, finds correct filename but doesn't compile in right directory?

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

> However, moving away ~/.vim/eclim.vim (a file used by eclim, as I've
> mentioned), I see correct behaviour. I'm attaching it here, 170 lines.
> It does modify runtimepath and basedir, which I'm guessing is what could
> be affecting the behaviour.

Well, AFAIK, eclim is a beast, isn't it? I don't have it installed, but 
I see that that eclim.vim sources lots of other eclim files that may be 
causing the problem.

If I had to guess, eclim is constantly sitting in the background 
managing the current directory, and so there's the classical problem 
with concurrency in software. It's possible that whenever vim-latex 
changes the directory and the shells out to latex, eclim takes over and 
resets the directory...

So you might want to talk to the eclim folks about what they might 
suggest (perhaps they'll suggest having Eclipse do your building for 
you...<?>).

Does eclim do much for you while in LaTeX? Perhaps you could setup an 
autocmd to not load eclim when you're in a .tex file.

--Ted

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

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

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

>> ln -sf tmp/foo.pdf
> Yes, I did think of that, but the symlink will always exist even if the
> file does not =). Its plenty good enough though, so that's probably what
> I'll use going forward.

Well, if you plan on keeping that tmp directory around for more than a 
few builds, the symlink:

cd tmp
ln -sf ../foo.pdf

works just as well, but the "foo.pdf" that shows up in your main 
directory isn't a symlink. Maybe that's a better fit?

--Ted

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

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

[Ng Oon-Ee <ng...@gm...>]

On Tue, 2011-02-15 at 21:22 -0500, Ted Pavlic wrote:
> > pdflatex -output-directory ./tmp foo.tex
> >
> > The output file (foo.pdf) would also appear there, which is where the
> > lack of a -output-filename hampers things (if such would exist, we could
> > just specify the filename to be something like ../foo)
> 
> You can always supplement with symlinks. For example, just once:
> 
> ln -sf tmp/foo.pdf
> 
> Then anytime after that:
> 
> pdflatex -output-director ./tmp foo.tex
> 
> Suddenly a "foo.pdf" will get placed within the current directory, and 
> it should get updated every time you run pdflatex again.
> 
> --Ted
> 
Yes, I did think of that, but the symlink will always exist even if the
file does not =). Its plenty good enough though, so that's probably what
I'll use going forward.

Now to figure out whether this affects include paths etc.

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

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

> pdflatex -output-directory ./tmp foo.tex
>
> The output file (foo.pdf) would also appear there, which is where the
> lack of a -output-filename hampers things (if such would exist, we could
> just specify the filename to be something like ../foo)

You can always supplement with symlinks. For example, just once:

ln -sf tmp/foo.pdf

Then anytime after that:

pdflatex -output-director ./tmp foo.tex

Suddenly a "foo.pdf" will get placed within the current directory, and 
it should get updated every time you run pdflatex again.

--Ted

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

Re: [Vim-latex-devel] Multiple file latex projects, finds correct filename but doesn't compile in right directory?

[Ng Oon-Ee <ng...@gm...>]

On Wed, 2011-02-16 at 09:11 +0800, Ng Oon-Ee wrote:
> 1115 is the latest I think. Now that you mention it, source is git,
> wonder why my packaging uses svn. Will fix that.

Same behaviour in latest git, just installed it.
> 
> > 
> > You could try something silly like:
> > 
> > :let g:Tex_CompileRule_dvi='pwd > thisdirectory'
> > 
> > and run \ll after that. Look for a "thisdirectory" file. See where it 
> > shows up (in ./chap1, in ./, or perhaps even in ../ <?>) and what its 
> > contents are. I'm sure there's a cleaner way to do debugging in vim, but 
> > I'm no vim expert.
> > 
> > --Ted
> > 
> pwd (and ls) choke because of all the additional arguments. I'll try
> some alternatives and revert.
> 
Using 'ls . > thisdirectory' I can confirm that its looking in chap1
instead of the root.

However, moving away ~/.vim/eclim.vim (a file used by eclim, as I've
mentioned), I see correct behaviour. I'm attaching it here, 170 lines.
It does modify runtimepath and basedir, which I'm guessing is what could
be affecting the behaviour.

Re: [Vim-latex-devel] Multiple file latex projects, finds correct filename but doesn't compile in right directory?

[Ng Oon-Ee <ng...@gm...>]

On Tue, 2011-02-15 at 14:49 -0500, Ted Pavlic wrote:
> > My minimal example below. Its VERY minimal:-
> 
> I meant a minimal working example. This one doesn't count because you used:
> 
> > \documentclass{article}
> 
> and then:
> 
> > \chapter{Introduction}
> 
> but chapter doesn't exist in article.cls (it does in report.cls or 
> book.cls though)

Sorry, changed it to report, however it doesn't get that far (as you can
see)
> 
> > for you (and presumably others as well), I'm wondering whether it has to
> > do with other vim plugins I have. Eclim is the big one, of course. I'm
> > attaching to this email my .vimrc if it makes a difference (maybe my
> > autocmd's are affecting things?).
> 
> I got rid of my .vimrc and .gvimrc and used your .vimrc, and everything 
> still works for me.
> 
> compiler.vim hasn't changed in a long time. You said you were using svn 
> revision 1115, which is fairly recent (3 months ago). Have you tried the 
> latest git version?

1115 is the latest I think. Now that you mention it, source is git,
wonder why my packaging uses svn. Will fix that.

> 
> You could try something silly like:
> 
> :let g:Tex_CompileRule_dvi='pwd > thisdirectory'
> 
> and run \ll after that. Look for a "thisdirectory" file. See where it 
> shows up (in ./chap1, in ./, or perhaps even in ../ <?>) and what its 
> contents are. I'm sure there's a cleaner way to do debugging in vim, but 
> I'm no vim expert.
> 
> --Ted
> 
pwd (and ls) choke because of all the additional arguments. I'll try
some alternatives and revert.

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

[Ng Oon-Ee <ng...@gm...>]

On Tue, 2011-02-15 at 12:34 -0500, Mike Richman wrote:
> On Tue, Feb 15, 2011 at 7:04 AM, Ng Oon-Ee <ng...@gm...> wrote:
> > On Mon, 2011-02-14 at 14:27 +0800, Ng Oon-Ee wrote:
> >> Hi,
> >>
> >> I'm coming from a texlipse (Eclipse plug-in) background. Been through
> >> the Latex-Suite Reference, but could not find this particular 'feature'.
> >>
> >> Would it be possible to do a compile in a specific subdirectory (by
> >> default ./tmp in texlipse). This helps prevent clutter in the main
> >> directory.
> >>
> >> I've not checked, but I believe texlipse does this using the
> >> --output-directory option of tex/pdflatex. Would changing
> >> g:Tex_CompileRule_* allow me to have this behaviour (all the temporary
> >> files like aux,bbl,blg,log,out,toc in ./tmp but the final output dvi/pdf
> >> in ./)?
> >>
> >
> > I take it this is not possible, then?
> 
> In principle, if you can determine the commands used to make it happen
> in the shell, then you can get vim-latex to do it for you as well.
> I've never tried compiling in a subdir, though.
> 
> Let us know if you can manage to do it at the command line.
> 
> -Mike Richman

Hmm, from checking more closely, it seems all texlipse does is move the
temp files out of the compilation folder after a completed (or partially
completed) compile. No point if its done that way then.

I was thinking more along the lines of how programs can be compiled in a
clean build directory, but perhaps that'd be a bit
complicated/unnecessary in this situation.

>From a bit of testing its obviously possible to do all output to a tmp
directory.

pdflatex -output-directory ./tmp foo.tex

The output file (foo.pdf) would also appear there, which is where the
lack of a -output-filename hampers things (if such would exist, we could
just specify the filename to be something like ../foo)

Re: [Vim-latex-devel] Multiple file latex projects, finds correct filename but doesn't compile in right directory?

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

> My minimal example below. Its VERY minimal:-

I meant a minimal working example. This one doesn't count because you used:

> \documentclass{article}

and then:

> \chapter{Introduction}

but chapter doesn't exist in article.cls (it does in report.cls or 
book.cls though)

Also:

> And, of course, main.tex.latexmain is a blank file. Seeing as it works

main.tex.latexmain is fine, but you can also use simply "main.latexmain" 
without the tex. That might look a little nicer (?). (I also recommend 
using \include for chapters so you can \includeonly them later in your 
writing process)

> for you (and presumably others as well), I'm wondering whether it has to
> do with other vim plugins I have. Eclim is the big one, of course. I'm
> attaching to this email my .vimrc if it makes a difference (maybe my
> autocmd's are affecting things?).

I got rid of my .vimrc and .gvimrc and used your .vimrc, and everything 
still works for me.

compiler.vim hasn't changed in a long time. You said you were using svn 
revision 1115, which is fairly recent (3 months ago). Have you tried the 
latest git version?

You could try something silly like:

:let g:Tex_CompileRule_dvi='pwd > thisdirectory'

and run \ll after that. Look for a "thisdirectory" file. See where it 
shows up (in ./chap1, in ./, or perhaps even in ../ <?>) and what its 
contents are. I'm sure there's a cleaner way to do debugging in vim, but 
I'm no vim expert.

--Ted

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

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

[Vim-latex-devel] [ vim-latex-Bugs-3182569 ] F9 completion inserts text into wrong window

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

Bugs item #3182569, was opened at 2011-02-15 19:57
Message generated for change (Tracker Item Submitted) made by yarogami
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3182569&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: Visa Putkinen (yarogami)
Assigned to: Nobody/Anonymous (nobody)
Summary: F9 completion inserts text into wrong window

Initial Comment:
(git 089726aa0662f085757c150f35cf63b624fa44f8 2011-02-14 22:27:48, Vim 7.2)

When doing ref or cite completion with F9 with multiple files open in different vim-windows, the completion might go into the wrong window. This is because Tex_CompleteWord forgets to go to the old window. The old window is saved to s:winnum at the beginning of Tex_Complete, so a simple fix is to add 

exe s:winnum.'wincmd w'

to the very beginning of Tex_CompleteWord in texviewer.vim

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

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

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

[Mike R. <ri...@um...>]

On Tue, Feb 15, 2011 at 7:04 AM, Ng Oon-Ee <ng...@gm...> wrote:
> On Mon, 2011-02-14 at 14:27 +0800, Ng Oon-Ee wrote:
>> Hi,
>>
>> I'm coming from a texlipse (Eclipse plug-in) background. Been through
>> the Latex-Suite Reference, but could not find this particular 'feature'.
>>
>> Would it be possible to do a compile in a specific subdirectory (by
>> default ./tmp in texlipse). This helps prevent clutter in the main
>> directory.
>>
>> I've not checked, but I believe texlipse does this using the
>> --output-directory option of tex/pdflatex. Would changing
>> g:Tex_CompileRule_* allow me to have this behaviour (all the temporary
>> files like aux,bbl,blg,log,out,toc in ./tmp but the final output dvi/pdf
>> in ./)?
>>
>
> I take it this is not possible, then?

In principle, if you can determine the commands used to make it happen
in the shell, then you can get vim-latex to do it for you as well.
I've never tried compiling in a subdir, though.

Let us know if you can manage to do it at the command line.

-Mike Richman

>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] [ vim-latex-Bugs-3182486 ] Changes lost on F9-complete in multifile project

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

Bugs item #3182486, was opened at 2011-02-15 18:47
Message generated for change (Tracker Item Submitted) made by yarogami
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3182486&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: Visa Putkinen (yarogami)
Assigned to: Nobody/Anonymous (nobody)
Summary: Changes lost on F9-complete in multifile project

Initial Comment:
(git 089726aa0662f085757c150f35cf63b624fa44f8 2011-02-14 22:27:48, Vim 7.2)

When doing F9-completion, changes to current file are lost when all of the following conditions are true:
1. The project has multiple .tex files
2. The F9-completion falls back to the default case (texviewer.vim:183)
3. <cword> is found in another .tex file
4. Tex_WriteBeforeCompletion is not set to 1 (It is not set by default)

The cause is that Tex_Grep (called in texviewer.vim:190) closes the current buffer without saving and opens the file where a match was found. A few possible fixes:

1. let g:Tex_WriteBeforeCompletion = 1 in texrc
2. Give a defautlt value of 1 when reading Tex_WriteBeforeCompletion in texviewer.vim:78

I didn't quite get the point of this fallback functionality, so perhaps there is a more suitable solution. Nevertheless, it is extremely frustrating to lose changes just because you press one button that shouldn't do anything bad...

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

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

[Vim-latex-devel] Documentation Typo

[Jonathan B. <jb...@jh...>]

In Section 7.2 of the vim-latex suite documentation, it describes setting
"g:TreatMacViewerAsUNIX" to execute the viewer command on a mac as a shell
command. But in the latest release, the "compliler.vim" script checks
instead for the variable set by "g:Tex_TreatMacViewerAsUNIX", on line 254.
This could be confusing for people when trying to configure vim-latex on a
mac.

best,
-j

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

[Ng Oon-Ee <ng...@gm...>]

On Mon, 2011-02-14 at 14:27 +0800, Ng Oon-Ee wrote:
> Hi,
> 
> I'm coming from a texlipse (Eclipse plug-in) background. Been through
> the Latex-Suite Reference, but could not find this particular 'feature'.
> 
> Would it be possible to do a compile in a specific subdirectory (by
> default ./tmp in texlipse). This helps prevent clutter in the main
> directory.
> 
> I've not checked, but I believe texlipse does this using the
> --output-directory option of tex/pdflatex. Would changing
> g:Tex_CompileRule_* allow me to have this behaviour (all the temporary
> files like aux,bbl,blg,log,out,toc in ./tmp but the final output dvi/pdf
> in ./)?
> 

I take it this is not possible, then?

[Vim-latex-devel] EnvMacro Customization

[Gerd W. <ger...@ma...>]

Hi,

recently, I customized the EnvMacros in my latex suite. If anyone is 
interested, I could provide the following customizations:

- I like to have a carriage return after most of the envmacros => add some 
variable like Tex_Env_AddCarriageReturn

- I like to have the \label{} right after the beginning of the environment 
=> add some variable like Tex_Env_LabelFirst

- I use some prefixes for my labels (e.g. eq: for equations, thm: for 
theorems, etc). Therefore, I added the variables 
Tex_Env_labelprefix_equation, Tex_Env_labelprefix_theorem, containing 
"eq:", "thm:" respectively. These prefixes are added in the routine 
Tex_eqnarray.

Any suggestions or comments?

Regards
Gerd

Re: [Vim-latex-devel] Multiple file latex projects, finds correct filename but doesn't compile in right directory?

[Ng Oon-Ee <ng...@gm...>]

On Mon, 2011-02-14 at 17:28 -0500, Ted Pavlic wrote:
> > main.tex
> > chap1/
> >     chap1.tex
> 
> First, I assume you are familiar with the TeX FAQ about importing bits 
> of document from subdirectories(?). There are complications that might 
> make you think twice about that sort of organization (but there are 
> packages that make it easier as well):
> 
> http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docotherdir

Thanks for the link. I was aware of issues with paths etc, but figured
I'd see what I could do about them once I got started. Not very hard to
change back to a flat layout halfway.
> 
> > When editing chap1.tex, \ll gives the following.
> >
> > || I can't find file `main.tex'. main.tex
> > || Emergency stop.
> 
> This doesn't make much sense to me. Before TeX-LaTeX starts the build, 
> it changes to the directory containing the latexmain file. The exception 
> to this is when you set the b:fragmentFile parameter, but then it 
> ignores the latexmain entirely. So it doesn't make sense that your build 
> is finding the latexmain and yet not changing to the right directory.
> 
> According to the TeX-LaTeX compiler.vim source, there used to be 
> problems on Linux machines with changing to directories with spaces in 
> their names. Do any of the directories in the /ABSOULTE/ path have 
> spaces? (e.g., are your files stored within a "My Documents" folder?) It 
> is possible that your vim is choking on the space and not changing 
> directory properly.
> 
> When I create a sample main.tex and ch1/ch1.tex, it works fine for me.
> 
> Can you post a minimal example that has this problem? (e.g., a 
> "main.tex" and a "chap1.tex" and information about the directory 
> structure) Perhaps there is something else interesting going on.
> 
> --Ted
> 
My minimal example below. Its VERY minimal:-

main.tex--------------------------
\documentclass{article}  

\begin{document}

\input{chap1/chap1.tex}

\end{document}
----------------------------------

chap1/chap1.tex-------------------
\chapter{Introduction}

\section{First section}
----------------------------------

And, of course, main.tex.latexmain is a blank file. Seeing as it works
for you (and presumably others as well), I'm wondering whether it has to
do with other vim plugins I have. Eclim is the big one, of course. I'm
attaching to this email my .vimrc if it makes a difference (maybe my
autocmd's are affecting things?).

Re: [Vim-latex-devel] Multiple file latex projects, finds correct filename but doesn't compile in right directory?

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

> main.tex
> chap1/
>     chap1.tex

First, I assume you are familiar with the TeX FAQ about importing bits 
of document from subdirectories(?). There are complications that might 
make you think twice about that sort of organization (but there are 
packages that make it easier as well):

http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docotherdir

> When editing chap1.tex, \ll gives the following.
>
> || I can't find file `main.tex'. main.tex
> || Emergency stop.

This doesn't make much sense to me. Before TeX-LaTeX starts the build, 
it changes to the directory containing the latexmain file. The exception 
to this is when you set the b:fragmentFile parameter, but then it 
ignores the latexmain entirely. So it doesn't make sense that your build 
is finding the latexmain and yet not changing to the right directory.

According to the TeX-LaTeX compiler.vim source, there used to be 
problems on Linux machines with changing to directories with spaces in 
their names. Do any of the directories in the /ABSOULTE/ path have 
spaces? (e.g., are your files stored within a "My Documents" folder?) It 
is possible that your vim is choking on the space and not changing 
directory properly.

When I create a sample main.tex and ch1/ch1.tex, it works fine for me.

Can you post a minimal example that has this problem? (e.g., a 
"main.tex" and a "chap1.tex" and information about the directory 
structure) Perhaps there is something else interesting going on.

--Ted

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

Re: [Vim-latex-devel] migration from svn to git

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

> vim-latex is now using git instead of svn. I hope the migration worked
> without major problems. If you find any irregularities, please report
> them.

	That's very exciting. Well done, Till.

	--Ted

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