On Fri, 2011-02-25 at 14:31 -0500, Ted Pavlic wrote:
Thanks Ted, but actually I don't even compile to ps =). dvi for editing,
pdf for final submissions for me.
In that case, get rid of the ps compile target. You'll never need it.
(interesting that you never have to worry about the latex
On Wed, 2011-02-23 at 08:12 +0100, Gerd Wachsmuth wrote:
INSTRUCTIONS:-
Test 1-
1. edit chap1/chap1.tex
2. Type \cite{ then press F9
3. Should show up as 0 results.
4. Run :edit ../main.tex
5. Type \cite{ then press F9
6. Results show. Undo everything, then :edit chap1/chap1.tex
On Wed, 2011-02-23 at 18:39 -0500, Ted Pavlic wrote:
let g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi'
On an unrelated subject, you should probably add -G0 after the -Ppdf...
dvips -Ppdf -G0 -o $*.ps $*.dvi
That will help prevent any problems when converting from CMR fonts to
In a previous thread I mentioned that using main.latexmain breaks F9
completion, where main.tex.latexmain fixes it.
Having used this more in actual writing, I've come across buggy
behaviour while editing subfiles (chap1/chap1.tex for example), where
F9 would give an empty list.
Here's the
On Tue, 2011-02-22 at 11:49 +0100, Gerd Wachsmuth wrote:
Sorry for being unclear, I was referring in the first paragraph to a
bug with using main.latexmain, which I fixed by using
main.tex.latexmain.
My primary question (the rest of the email) was about a bug I
experienced when using
2011/2/16 Ted Pavlic t...@tedpavlic.com:
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
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 byF9 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?
On Wed, 2011-02-16 at 14:16 +0800, Ng Oon-Ee wrote:
On Wed, 2011-02-16 at 01:11 -0500, Ted Pavlic wrote:
:let g:Tex_ViewRuleComplete_dvi='your view rule with jobname included'
inside your latexmain file. The latexmain files get sourced. If you
What would a 'view rule with jobname
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
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
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
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
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
On Tue, 2011-02-15 at 23:28 -0500, Ted Pavlic wrote:
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.
Connecting this with the response I just sent, you can of
On Wed, 2011-02-16 at 13:11 +0800, Ng Oon-Ee wrote:
On Tue, 2011-02-15 at 23:28 -0500, Ted Pavlic wrote:
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
On Wed, 2011-02-16 at 01:11 -0500, Ted Pavlic wrote:
:let g:Tex_ViewRuleComplete_dvi='your view rule with jobname included'
inside your latexmain file. The latexmain files get sourced. If you
What would a 'view rule with jobname included' look like?
My current view rule is simple
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 `main.tex
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
Hi all, regarding the above:-
https://facwiki.cs.byu.edu/nlp/index.php/Vim%2BLaTeX_on_Linux
seems to be the only good resource I can find on this. Can't seem to get
it working with okular though. pdflatex runs with -synctex=1 and
generates main.synctex.gz, but \ls just opens the pdf without going
On Sat, 2011-02-05 at 18:19 +0800, Ng Oon-Ee wrote:
Hi all, regarding the above:-
https://facwiki.cs.byu.edu/nlp/index.php/Vim%2BLaTeX_on_Linux
seems to be the only good resource I can find on this. Can't seem to get
it working with okular though. pdflatex runs with -synctex=1 and
generates
On Sat, 2011-02-05 at 11:35 +0100, Mario Santagiuliana wrote:
In data 5/2/2011 11:19:21, Ng Oon-Ee ha scritto:
Hi all, regarding the above:-
https://facwiki.cs.byu.edu/nlp/index.php/Vim%2BLaTeX_on_Linux
seems to be the only good resource I can find on this. Can't seem to get
it working
21 matches
Mail list logo
