Ted Pavlic tedpavlic.com> writes:
>
> >> 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.
Sorry for digging out this old thread.
But I'm experiencing the same problem. I didn't have eclim installed.
--
> Additionally \citep, \citet, \citeauthor, etc... Not sure if they would
> match whatever pattern triggers the F9 completion... But I never use
> \cite (in favor of the natbib variaties) and almost never use \ref (in
> favor of hyperref's \autoref), and so F9 is potentially unhelpful.
Moreover, d
> Okay, the only reason I brought it up is that you recommended
> main.latexmain =). Was quite surprised to see that it broke completion,
> would think its quite unusable in that case (how do you use latex
> without citing, after all).
F9 is too far away from the home row. It's much faster to avoi
On Mon, 2011-02-21 at 11:12 -0500, Ted Pavlic wrote:
> > Just to comment on this, when using main.latexmain compilation works
> > but auto-completion by does not. main.tex.latexmain works fine
> > for both compilation and auto-completion.
> >
> > I'm pretty sure this is a (minor) bug, should I rep
> Just to comment on this, when using main.latexmain compilation works
> but auto-completion by does not. main.tex.latexmain works fine
> for both compilation and auto-completion.
>
> I'm pretty sure this is a (minor) bug, should I report it?
I don't think that's necessary. It doesn't seem like a
2011/2/16 Ted Pavlic :
>> 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 \includeonl
>> 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:
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
> 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
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_CompileR
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 articl
> 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,
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 organizatio
> 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://ww
On Mon, 2011-02-14 at 15:13 +0800, Ng Oon-Ee wrote:
> I've got the following setup (simplified)
>
> .
> ..
> main.tex
> chap1/
>chap1.tex
>
> When editing main.tex, \ll works fine, everything comes out correct.
>
> When editing chap1.tex, \ll gives the following.
>
> || I can't find file `m
It looks that gvim version 7.1.56 causes problems
preventing latexing a multiple file project. I
compiled gvim version 6.4 from source today and have
no problem using it for a multiple file project. It
looks that vim-latex suite doesn't keep up pace with
newer version of vims.
Regards,
Ahmet
Hello Again,
I have no problem latexing "main.latex" inside the
"thesis" directory. I paste the "main.log" file.
->
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
(format=latex 2007.8.4) 30 AUG 2007 21:04
entering extended mode
%&-line parsing ena
On Thu, 30 Aug 2007, ahmet nurlu wrote:
> Hi,
>
> "main.tex.mainlatex" was just a typo. The correct of
> it is "main.tex.latexmain".
>
> I post the texput.log file below:
>
> ->
>
> This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
> (format=latex
Hi,
"main.tex.mainlatex" was just a typo. The correct of
it is "main.tex.latexmain".
I post the texput.log file below:
->
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
(format=latex 2007.8.4) 30 AUG 2007 17:20
entering extended mode
Sourc
On Wed, 29 Aug 2007, ahmet nurlu wrote:
> I recently have a problem with multiple file latex
> projects. It was not happening before and has appeared
> suddenly. My directory layout such as the following:
>
> thesis/
>main.tex
>main.tex.mainlatex
20 matches
Mail list logo
