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

Re: [Vim-latex-devel] PATCH: Fold all %%fake, not just %%fakesection

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

Okay. I'll buy that.

Either way, I'd be excited to see this merged into the devel branch
ASAP. I currently have my old version (which deferred to the nested
behavior that I do agree is annoying) mocked up in my ~/.vim
directory. I'll be very happy when the %%fake... support is built into
the devel version.

Thanks --
Ted

On Wed, Aug 11, 2010 at 2:00 AM, Gerd Wachsmuth
<ger...@ma...> wrote:
> Hi,
>
> maybe for compatibility reasons? If someone has added some %%fake.. already
> to the FoldedSections, the latex-suite will not look for %%fake%%fake... But
> maybe the first branch should simply ignore the %%fake..s contained in the
> FoldedSections...
>
> Regards
> Gerd
>
>
> On Tue, 10 Aug 2010, Ted Pavlic wrote:
>
>> Gerd --
>>
>> That's an excellent point. However, in your patch...
>>
>>> ===================================================================
>>> --- ftplugin/latex-suite/folding.vim    (revision 1106)
>>> +++ ftplugin/latex-suite/folding.vim    (working copy)
>>> @@ -54,7 +54,7 @@
>>>        if s =~ '%%fakesection'
>>>                let s = '^\s*' . s
>>>        else
>>> -               let s = '^\s*\\' . s . '\W'
>>> +               let s = '^\s*\\' . s . '\W\|^\s*%%fake' . s
>>
>> ...why do you leave the first part of the branch there? Doesn't your
>> addition mitigate the need for special "fake" cases? Can't we just use your
>> addition exclusively?
>>
>>        Thanks --
>>        Ted
>>
>> On 08/10/2010 04:50 AM, Gerd Wachsmuth wrote:
>>>
>>> Hi,
>>>
>>> at least for me, there is one problem with the folding of %%fakesection:
>>> They are nested in sections (see attached test.tex). Imho they should be
>>> at the same level as section.
>>>
>>> The attached patch automatically adds %%fakepart, %%fakechapter,... as
>>> folded sections and they are folded at the same level as their non-fake
>>> counterparts.
>>>
>>> Regards
>>> Gerd
>>>
>>> On Wed, 24 Mar 2010, Ted Pavlic wrote:
>>>
>>>> vim-latex documents the use of %%fakesection to create new folds at
>>>> the same level as \section folds. To organize my preamble and
>>>> backmatter, I use similar sections like %%fakepart, %%fakechapter,
>>>> %%fakesubsection, etc.
>>>>
>>>> The attached one-line patch modifies the section of folding.vim so
>>>> that it looks for %%fake and not just %%fakesection. That lets me
>>>> update g:Tex_FoldedSections to include all of my other %%fake...
>>>> sections.
>>>>
>>>> --Ted
>>
>>
>
>



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

Re: [Vim-latex-devel] PATCH: Fold all %%fake, not just %%fakesection

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

Hi,

maybe for compatibility reasons? If someone has added some %%fake.. 
already to the FoldedSections, the latex-suite will not look for 
%%fake%%fake... But maybe the first branch should simply ignore the 
%%fake..s contained in the FoldedSections...

Regards
Gerd


On Tue, 10 Aug 2010, Ted Pavlic wrote:

> Gerd --
>
> That's an excellent point. However, in your patch...
>
>> ===================================================================
>> --- ftplugin/latex-suite/folding.vim	(revision 1106)
>> +++ ftplugin/latex-suite/folding.vim	(working copy)
>> @@ -54,7 +54,7 @@
>>  	if s =~ '%%fakesection'
>>  		let s = '^\s*' . s
>>  	else
>> -		let s = '^\s*\\' . s . '\W'
>> +		let s = '^\s*\\' . s . '\W\|^\s*%%fake' . s
>
> ...why do you leave the first part of the branch there? Doesn't your addition 
> mitigate the need for special "fake" cases? Can't we just use your addition 
> exclusively?
>
> 	Thanks --
> 	Ted
>
> On 08/10/2010 04:50 AM, Gerd Wachsmuth wrote:
>> Hi,
>> 
>> at least for me, there is one problem with the folding of %%fakesection:
>> They are nested in sections (see attached test.tex). Imho they should be
>> at the same level as section.
>> 
>> The attached patch automatically adds %%fakepart, %%fakechapter,... as
>> folded sections and they are folded at the same level as their non-fake
>> counterparts.
>> 
>> Regards
>> Gerd
>> 
>> On Wed, 24 Mar 2010, Ted Pavlic wrote:
>> 
>>> vim-latex documents the use of %%fakesection to create new folds at
>>> the same level as \section folds. To organize my preamble and
>>> backmatter, I use similar sections like %%fakepart, %%fakechapter,
>>> %%fakesubsection, etc.
>>> 
>>> The attached one-line patch modifies the section of folding.vim so
>>> that it looks for %%fake and not just %%fakesection. That lets me
>>> update g:Tex_FoldedSections to include all of my other %%fake...
>>> sections.
>>> 
>>> --Ted
>
>

Re: [Vim-latex-devel] PATCH: Fold all %%fake, not just %%fakesection

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

Gerd --

That's an excellent point. However, in your patch...

 > ===================================================================
 > --- ftplugin/latex-suite/folding.vim	(revision 1106)
 > +++ ftplugin/latex-suite/folding.vim	(working copy)
 > @@ -54,7 +54,7 @@
 >  	if s =~ '%%fakesection'
 >  		let s = '^\s*' . s
 >  	else
 > -		let s = '^\s*\\' . s . '\W'
 > +		let s = '^\s*\\' . s . '\W\|^\s*%%fake' . s

...why do you leave the first part of the branch there? Doesn't your 
addition mitigate the need for special "fake" cases? Can't we just use 
your addition exclusively?

	Thanks --
	Ted

On 08/10/2010 04:50 AM, Gerd Wachsmuth wrote:
> Hi,
>
> at least for me, there is one problem with the folding of %%fakesection:
> They are nested in sections (see attached test.tex). Imho they should be
> at the same level as section.
>
> The attached patch automatically adds %%fakepart, %%fakechapter,... as
> folded sections and they are folded at the same level as their non-fake
> counterparts.
>
> Regards
> Gerd
>
> On Wed, 24 Mar 2010, Ted Pavlic wrote:
>
>> vim-latex documents the use of %%fakesection to create new folds at
>> the same level as \section folds. To organize my preamble and
>> backmatter, I use similar sections like %%fakepart, %%fakechapter,
>> %%fakesubsection, etc.
>>
>> The attached one-line patch modifies the section of folding.vim so
>> that it looks for %%fake and not just %%fakesection. That lets me
>> update g:Tex_FoldedSections to include all of my other %%fake...
>> sections.
>>
>> --Ted

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

   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.

Re: [Vim-latex-devel] PATCH: Fold all %%fake, not just %%fakesection

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

Hi,

at least for me, there is one problem with the folding of %%fakesection: 
They are nested in sections (see attached test.tex). Imho they should be 
at the same level as section.

The attached patch automatically adds %%fakepart, %%fakechapter,... as 
folded sections and they are folded at the same level as their non-fake 
counterparts.

Regards
Gerd

On Wed, 24 Mar 2010, Ted Pavlic wrote:

> vim-latex documents the use of %%fakesection to create new folds at the same 
> level as \section folds. To organize my preamble and backmatter, I use 
> similar sections like %%fakepart, %%fakechapter, %%fakesubsection, etc.
>
> The attached one-line patch modifies the section of folding.vim so that it 
> looks for %%fake and not just %%fakesection. That lets me update 
> g:Tex_FoldedSections to include all of my other %%fake... sections.
>
> --Ted

Re: [Vim-latex-devel] ref and cite completion in windows, once again

[Patrick <pa...@st...>]

Hi,

It seems the problem was the python version I use. On my windows pc at 
my office I have python 2.6 and in virtualbox 2.7. When trying :python 
print "test", I received an error that said python24.dll could not be 
found. I just tried installing vim 7.3d beta in vbox, and it seems to 
works fine with python 2.7.

I tested the autocompletion with vim 7.3d with a single tex file and a 
project and in both cases it worked for cite as well as ref commands.

Cheers,
Patrick



On 08/07/2010 04:10 PM, Patrick wrote:
> Hi,
>
> I recently started using Vim-LaTeX, but ran in some problems with
> autocompletion of references and citations  in windows xp.
>
> When I enter F9 after typing \cite{ the window my bibtex entries
> opens as it should. However, when I press enter, the window just closes
> without filling in the reference. When I use F9 with \ref I get an
> error window saying "''C:' is not recognized as an internal or external
> command," This behaviour occurs for single file tex documents as well
> as projects using a latexmain file. Here are some things I have tried
> so far,
>
> I have set grepprg=grep\ -nH\ $* in my _vimrc and also tried to use the
> internal grep to no avail.
>
> I searched around and found earlier mentions of this problem, also on
> this mailing list.
>
> http://www.mail-archive.com/vim...@li.../msg00486.html
> http://www.mail-archive.com/vim...@li.../msg00118.html
>
> In the first, a patch is mentioned, which was incorporated in changeset
> 1047. Since I use the latest vim-latex version from sourceforge
> (29/01/2010) I assume I have a patched version.
>
> Following the second mail thread I installed GnuWin32 grep in
> C:\GnuWin32 and Vim7.2 in C:\vim to prevent problems with spaces.
> My python installation resides in C:\python26. Also I made sure the
> path to the tex files does not contain any spaces. This did not do the
> trick.
>
> Just as a test, I installed vim, vim-latex and miktex 2.8 in a
> guest winXP in virtualbox with ubuntu lucid as the host. Again all
> installations, including MiKTeX, were done using folders without
> spaces. To prevent interference from other vim plugins I did not
> install any. In this setup I have exactly the same problem as in the
> regular winXP.
>
> So all in all I wasn't very succesful with my solutions. In ubuntu
> itself everything worked pretty much out of the box, but in xp it seems
> a bit more tricky. Does anyone have any more suggestions on how to
> fix this?
>
> Regards,
> Patrick
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>    

[Vim-latex-devel] ref and cite completion in windows, once again

[Patrick <pa...@st...>]

Hi,

I recently started using Vim-LaTeX, but ran in some problems with
autocompletion of references and citations  in windows xp.

When I enter F9 after typing \cite{ the window my bibtex entries
opens as it should. However, when I press enter, the window just closes
without filling in the reference. When I use F9 with \ref I get an
error window saying "''C:' is not recognized as an internal or external
command," This behaviour occurs for single file tex documents as well
as projects using a latexmain file. Here are some things I have tried
so far,

I have set grepprg=grep\ -nH\ $* in my _vimrc and also tried to use the
internal grep to no avail.

I searched around and found earlier mentions of this problem, also on
this mailing list.

http://www.mail-archive.com/vim...@li.../msg00486.html
http://www.mail-archive.com/vim...@li.../msg00118.html

In the first, a patch is mentioned, which was incorporated in changeset
1047. Since I use the latest vim-latex version from sourceforge
(29/01/2010) I assume I have a patched version.

Following the second mail thread I installed GnuWin32 grep in
C:\GnuWin32 and Vim7.2 in C:\vim to prevent problems with spaces.
My python installation resides in C:\python26. Also I made sure the
path to the tex files does not contain any spaces. This did not do the
trick.

Just as a test, I installed vim, vim-latex and miktex 2.8 in a
guest winXP in virtualbox with ubuntu lucid as the host. Again all
installations, including MiKTeX, were done using folders without
spaces. To prevent interference from other vim plugins I did not
install any. In this setup I have exactly the same problem as in the
regular winXP.

So all in all I wasn't very succesful with my solutions. In ubuntu
itself everything worked pretty much out of the box, but in xp it seems
a bit more tricky. Does anyone have any more suggestions on how to
fix this?

Regards,
Patrick

Re: [Vim-latex-devel] ref completion with multiple files

[Francis Turgeon-B. <fra...@gm...>]

It seems there is already a patch submitted by Kay Smarczewski in the
tracker on sourceforge which should work.

Francis

2010/8/4 Francis Turgeon-Boutin <fra...@gm...>
>
> Hi,
> I'm having a problem with ref completion with multiple files project. It seems it doesn't find \input file if the \input command is not a the beginning of a line (if it is indented or there is a space before). By changing outline.py like this (removing ^ from the regex), it seems to fix the problem :
>
>      # TODO what are all the ways in which a tex file can include another?
> -    pat = re.compile(r'^\\(@?)(include|input){(.*?)}', re.M)
> +    pat = re.compile(r'\\(@?)(include|input){(.*?)}', re.M)
>      contents = re.sub(pat, getFileContents, contents)
> I have included the diff and a minimal example.
> thx !
> Francis

[Vim-latex-devel] ref completion with multiple files

[Francis Turgeon-B. <fra...@gm...>]

Hi,

I'm having a problem with ref completion with multiple files project. It
seems it doesn't find \input file if the \input command is not a the
beginning of a line (if it is indented or there is a space before). By
changing outline.py like this (removing ^ from the regex), it seems to fix
the problem :

     # TODO what are all the ways in which a tex file can include another?
-    pat = re.compile(r'^\\(@?)(include|input){(.*?)}', re.M)
+    pat = re.compile(r'\\(@?)(include|input){(.*?)}', re.M)
     contents = re.sub(pat, getFileContents, contents)

I have included the diff and a minimal example.

thx !
Francis

[Vim-latex-devel] fixes for citation completion

[Robin <ro...@gm...>]

Hi,

I have had some problems with citation completion which I just got
around to fixing.

The first is that when using taglist latex-suite attempts to complete
in the (unmodifiable) taglist window. I found a simple fix in the vim
wiki:
http://vim.wikia.com/wiki/Use_Taglist_with_LaTeX_files
which is to add the following as the first line Tex_CompleteWord in
texviewer.vim
exe s:winnum.' wincmd w'

The second was that when field names in the bib file are capitalised
(ie Author vs author) as BibDesk seems to do they weren't being
extracted and displayed in the completion window (only the cite key
was visible).
This is fixed by the following addition of .lower() to the field name:
===================================================================
--- bibtools.py (revision 48)
+++ bibtools.py (working copy)
@@ -43,7 +43,7 @@
             if not m:
                 break

-            field = m.group(1)
+            field = m.group(1).lower()

             body = body[(m.start(2)+1):]
             if m.group(2) == '{':

Finally, an unrelated thing that was needed to stop taglist displaying
everything twice was the patch in this message to use latex-suite
ctags definitions rather than the latex ones that ship with newer
versions of ctags.
http://www.mail-archive.com/vim...@li.../msg00682.html

I wonder if theres any chance of getting these changes comitted to
latex-suite? I don't think they should mess anything up and I don't
think it is a particularly obscure usecase (using bibdesk + taglist +
latexsuite).

Thanks

Robin

[Vim-latex-devel] filetype not set on latexmain file

[Robin <ro...@gm...>]

Hi,

I am using the .latexmain file feature for a document that includes
multiple source files.

If I open one of the included files it helpfully includes the main
file as well - but I can't get the filetype on this automatically
opened file to be set. I have tried adding it in a modeline but it
doesn't work.

I guess the workaround is to always explicitly open the main document
first (or reload the file - but I just noticed it is also opened
readonly).

Is there a better way around this (ie change so thats opened as a normal file).

Cheers

Robin

Re: [Vim-latex-devel] how to disable latex folding

[Simon Q. <sim...@gm...>]

Hm, I should have looked more closely: type
:let g:Tex_Folding=0
to turn off LaTeX folding by vim-latex usin a global switch.
You may want to put this line (w/o :) into your ~/.vim/ftplugin/tex.vim

Hope it works.
Simon

Am 28.07.2010 11:54, schrieb Simon Quittek:
> Hi Sai,
>
> maybe the zA command of vim (which unfolds every subfolding recursively)
> help you to make life easier.
> If you want to turn off folding at all, try to rename
> $VIM/ftplugin/latex-suite/folding.vim
> and replace it by an empty file.
>
> Regards
> Simon
>
> Am 28.07.2010 11:34, schrieb Sai Duan:
>>     Dear vim-latex-devel:
>>
>>        I have installed the vim-latex-suite and very happy to use it.
>> However, I don't want to fold my tex file. How to disable this function?
>>
>> Best regards.
>>
>> Sai Duan
>> Theoretical Chemistry, Royal Institute of Technology
>> Stockholm 10691, Sweden
>> 07/28/2010
>>
>> ------------------------------------------------------------------------------
>> The Palm PDK Hot Apps Program offers developers who use the
>> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
>> of $1 Million in cash or HP Products. Visit us here for more details:
>> http://ad.doubleclick.net/clk;226879339;13503038;l?
>> http://clk.atdmt.com/CRS/go/247765532/direct/01/
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://ad.doubleclick.net/clk;226879339;13503038;l?
> http://clk.atdmt.com/CRS/go/247765532/direct/01/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] how to disable latex folding

[Simon Q. <sim...@gm...>]

Hi Sai,

maybe the zA command of vim (which unfolds every subfolding recursively) 
help you to make life easier.
If you want to turn off folding at all, try to rename
$VIM/ftplugin/latex-suite/folding.vim
and replace it by an empty file.

Regards
Simon

Am 28.07.2010 11:34, schrieb Sai Duan:
>    Dear vim-latex-devel:
>
>       I have installed the vim-latex-suite and very happy to use it.
> However, I don't want to fold my tex file. How to disable this function?
>
> Best regards.
>
> Sai Duan
> Theoretical Chemistry, Royal Institute of Technology
> Stockholm 10691, Sweden
> 07/28/2010
>
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://ad.doubleclick.net/clk;226879339;13503038;l?
> http://clk.atdmt.com/CRS/go/247765532/direct/01/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

[Vim-latex-devel] how to disable latex folding

[Sai D. <du...@gm...>]

  Dear vim-latex-devel:

     I have installed the vim-latex-suite and very happy to use it. 
However, I don't want to fold my tex file. How to disable this function?

Best regards.

Sai Duan
Theoretical Chemistry, Royal Institute of Technology
Stockholm 10691, Sweden
07/28/2010

Re: [Vim-latex-devel] Compiler Problem

[N. L. F. <per...@ce...>]

I am not a developer, but it is my understanding that latex reads the  
saved file when it compiles the dvi.  I would expect it to be necessary to  
save your buffer to disk with :w in order to compile it into a new dvi.   
Personally, I like this design choice since it forces me to save my work  
frequently.

I do not know about the other issue.

On Wed, 21 Jul 2010 11:30:46 -0500, Helge Liebert  
<hl....@go...> wrote:

> hey,
>
> im using vim 7.2 at work and would like to also use latex-suite. ive
> added everything to my vimfiles directory and made the recommended
> changes to the _virmrc, and latex suite is recognized. however, when i
> compile files that already exist after ive made changes to the
> original tex file, they are not overwritten. it only works if i save
> the file first and then compile or delete the dvi that should be
> overwritten. also, if i try to make changes to the default ouput
> format and other options it doesnt seem to have any effect, they
> remain unchanged.
>
> i would greatly appreciate it if anybody could help.
>
> best regards,
>
> Helge
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel


-- 
Nicholas Laszlo Frazer
per...@ce...
nlf@u.northwestern.edu

1516 Hinman #510
Evanston, IL 60201
(773)634-9638

[Vim-latex-devel] Compiler Problem

[Helge L. <hl....@go...>]

hey,

im using vim 7.2 at work and would like to also use latex-suite. ive
added everything to my vimfiles directory and made the recommended
changes to the _virmrc, and latex suite is recognized. however, when i
compile files that already exist after ive made changes to the
original tex file, they are not overwritten. it only works if i save
the file first and then compile or delete the dvi that should be
overwritten. also, if i try to make changes to the default ouput
format and other options it doesnt seem to have any effect, they
remain unchanged.

i would greatly appreciate it if anybody could help.

best regards,

Helge

Re: [Vim-latex-devel] IMAP with multibyte lhs

[<com...@fr...>]

Hello!                                                                                              

> Message de Bodo Graumann: Sat 10/07/10, 13:42:51 +0200
> First of all thx a lot to LuX, that patch works wonderfully for my current
> use.

Good news. :-)

> I think saving my texsources as utf8 is good enough.
> Even if I would try to save it as plain ASCII, I would end up with your
> problem, LuX
> and I don't think converting those tex commands to their unicode
> representation in vim would be a good thing.
> If you need to give the file to someone without utf8 capabilities, you could
> still write a small filter,
> that replaces all the unicode-characters with the latex commands...

I do like to use this feature of automatic conversion between LaTeX
macros and unicode characters. Note that it is an improvement of an
existing vim script which has been downloaded 1430 times or so, hence
I guess that other people could appreciate it too:
http://www.vim.org/scripts/script.php?script_id=284
But of course this is a question of taste. Thank you for the feed back
anyway. 

However I still don't know the answer to my initial question: 

---> Is there a chance that IMAP (the official IMAP, shipped with
imaps.vim, not my own variant of course) will accept multibyte
(unicode) characters in lhs strings in the future? 

If anyone knows the answer, I would be pleased to hear about it. 

Thanks, 
LuX. 

Re: [Vim-latex-devel] IMAP with multibyte lhs

[Bodo G. <ma...@bo...>]

Hi,

Just wanted to send some note on my progress.
First of all thx a lot to LuX, that patch works wonderfully for my current
use.
Also I have succeeded in using unicode-characters in math mode by defining:
\catcode`\Σ=\active \defΣ{\sum}
for the characters I want to use (those that are available on my neo
keyboard layout)
ucs didn't work for me — might be because I use xelatex
I think saving my texsources as utf8 is good enough.
Even if I would try to save it as plain ASCII, I would end up with your
problem, LuX
and I don't think converting those tex commands to their unicode
representation in vim would be a good thing.
If you need to give the file to someone without utf8 capabilities, you could
still write a small filter,
that replaces all the unicode-characters with the latex commands...

best regards
Bodo

On Tue, Jun 29, 2010 at 9:22 PM, Kay Smarczewski <
kay...@ma...> wrote:

> On Mon, Jun 28, 2010 at 11:11:44PM +0200, com...@fr... wrote:
> > I do not have such keys in my keyboard, I have a plane qwerty keyboard.
> > What I wanted is an easy access to mathematical unicode symbols from
> > my keyboard, not necessarily for LaTeX, but for mail, plain text,
> > whatever. For example I can type in this mail: ∀ ε ≤ 1, ∃ ζ ∈ ℂ… and
> > so on. (Apparently these characters are displayed properly on
> > the web site, I hope it is the same for your mail viewer.)
> Have you tried snipMate? I use it to map some of my ALT Gr + xx keys
> to special unicode characters.
>
> > What I really wanted actually was that when I open a tex file all the
> > LaTeX macros that it contains for mathematical symbols are converted
> > to UTF8 glyphs which represent them, and when I save the file the UTF8
> > characters are converted back. So that I have a more "wysiwyg" LaTeX
> > editor, with much more compact and readable formulas, but still have
> > plain ascii LaTeX file, which latex can compile without problem.
> I use the ucs (mathletters) package in LaTex. So LaTex can compile
> UTF-8 characters. This is just a workaround for missing unicode
> support. But it works for me.
>
> Kind regards,
>
> Kay
>
> --
> Kay Smarczewski
> Web: http://www.smarti.info
> Jabber: ka...@ja...
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>



-- 
NOTHING IS REAL

Re: [Vim-latex-devel] [Question] Bibtex compiling

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

Pgf/TikZ was meant to fill the gap created when moving from latex to 
pdflatex. However, because Pgf/TikZ does not natively use EPS, the 
mathematics it can do are severely limited. For example, you may be able 
to repeat an operation a finite number of times (e.g., automatically 
generating several instances of a graphic), but you will be unable to 
specify the shape of a curve using a function. Of course, you can give 
it a set of points generated by another program (e.g., gnuplot); you 
just can't do such things on the fly.

Additionally, PSTricks already has a wide set of support packages 
available for different application areas (e.g., electronic circuits, 
flow charts, 3D, etc.). Having said that, Pgf/TikZ has a growing and 
contributing audience, and so it is catching up.

My biggest frustration with Pgf/TikZ is that it creates unneeded 
segmentation in the LaTeX audience. PSTricks and EPS graphics provide a 
rich set of tools that Pgf/TikZ will always lag behind. Unfortunately, 
because of the complications involved in converting from EPS-friendly 
graphics to PDF-friendly graphics (and vice versa), there are a lot of 
people who just want a PDF-native LaTeX solution. That's how Pgf/TikZ 
got started. I can't really blame them and their audience. After all, 
the people responsible for the classical LaTeX methods can sometimes be 
mean and stubborn; it's no surprise that side efforts to smooth out 
LaTeX rough edges become very popular with a wider LaTeX audience.

So, I guess I'm saying that you should use whatever you're most 
comfortable with. Your graphics will never be as integrated with 
Pgf/TikZ as they could be with PSTricks; however, you won't have to 
worry about converting back and forth between the EPS world and the PDF 
world.

--Ted


On 07/06/2010 03:03 AM, Gianluca Meneghello wrote:
> Thanks Ted for your comments... I'm learning tikz and pgf: they seem
> to work fine with pdflatex and, to my opinion, produces very nice
> graphics. But I have no idea on whether it can solve differential
> equations on the fly --- but I know it uses gnuplot in order to do the
> math, and then import the data. Any comment on how does it compare
> with PStricks?
>
> Thanks again
>
> gianluca
>
> On 5 July 2010 17:48, Ted Pavlic<te...@te...>  wrote:
>>> That's good because as far as I know compiling in dvi does not allow
>>> to use \includefigures using pdf files, right? So it was not an
>>> option!
>>
>> Using latex (as opposed to pdflatex) means all of your graphics have
>> to be EPS files. You can use pdflatex to include PDF, PNG, JPG, or
>> GIF, but pdflatex will not include EPS files. A major downside of not
>> being able to use EPS natively is that you lose out on all of the
>> great features of EPS. For example, PSTricks (a LaTeX drawing package)
>> can do very advanced things because it leverages the power of EPS. In
>> particular, PSTricks can do math within graphics that lets you (for
>> example) solve differential equations during the compilation of your
>> document.
>>
>> [ Personally, I hate including MATLAB figures within a nicely
>> formatted LaTeX document. Even though MATLAB has some crude
>> LaTeX/Computer-Modern-font support that you can put into figs, the
>> figures always make a nice document look worse. An old officemate of
>> mine would use the psfrag package (which also requires using EPS) to
>> solve this problem. MATLAB puts dummy symbols throughout the fig, and
>> psfrag can replace them on-the-fly with text rendered from the
>> document. However, the graphics themselves still lack the smooth look
>> that LaTeX provides. So I don't even generate figs from MATLAB; I have
>> MATLAB export data and use PSTricks to plot that data natively within
>> LaTeX. The result is a document without seems. ]
>>
>> There are several packages that allow you to include pdflatex-friendly
>> files in latex (and probably vice versa). They essentially run a small
>> pass of pdflatex or a converter program to generate EPS files from the
>> PDF's you want to include. The packages can actually do this fairly
>> automatically. I take a different route because I eschew using
>> pdflatex. I have Makefiles that will automatically generate EPS's from
>> any other file type as needed (e.g., if I use \includegraphics{blah}
>> and there is a blah.gif in the directory, the Makefile will convert
>> blah.gif to blah.eps before running LaTeX). IIRC, there are similar
>> automatic conversion facilities built into some of the most
>> sophisticated LaTeX build scripts (e.g., "rubber").
>>
>> Anyway, I'm glad you're both up and running. And I'm glad that now I
>> know about that configuration parameter -- it was something I took for
>> granted before you're issue was posted!
>>
>> Best --
>> Ted
>>
>> --
>> Ted Pavlic<te...@te...>
>>
>
>
>

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

   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.

Re: [Vim-latex-devel] [Question] Bibtex compiling

[Gianluca M. <gia...@gm...>]

Thanks Ted for your comments... I'm learning tikz and pgf: they seem
to work fine with pdflatex and, to my opinion, produces very nice
graphics. But I have no idea on whether it can solve differential
equations on the fly --- but I know it uses gnuplot in order to do the
math, and then import the data. Any comment on how does it compare
with PStricks?

Thanks again

gianluca

On 5 July 2010 17:48, Ted Pavlic <te...@te...> wrote:
>> That's good because as far as I know compiling in dvi does not allow
>> to use \includefigures using pdf files, right? So it was not an
>> option!
>
> Using latex (as opposed to pdflatex) means all of your graphics have
> to be EPS files. You can use pdflatex to include PDF, PNG, JPG, or
> GIF, but pdflatex will not include EPS files. A major downside of not
> being able to use EPS natively is that you lose out on all of the
> great features of EPS. For example, PSTricks (a LaTeX drawing package)
> can do very advanced things because it leverages the power of EPS. In
> particular, PSTricks can do math within graphics that lets you (for
> example) solve differential equations during the compilation of your
> document.
>
> [ Personally, I hate including MATLAB figures within a nicely
> formatted LaTeX document. Even though MATLAB has some crude
> LaTeX/Computer-Modern-font support that you can put into figs, the
> figures always make a nice document look worse. An old officemate of
> mine would use the psfrag package (which also requires using EPS) to
> solve this problem. MATLAB puts dummy symbols throughout the fig, and
> psfrag can replace them on-the-fly with text rendered from the
> document. However, the graphics themselves still lack the smooth look
> that LaTeX provides. So I don't even generate figs from MATLAB; I have
> MATLAB export data and use PSTricks to plot that data natively within
> LaTeX. The result is a document without seems. ]
>
> There are several packages that allow you to include pdflatex-friendly
> files in latex (and probably vice versa). They essentially run a small
> pass of pdflatex or a converter program to generate EPS files from the
> PDF's you want to include. The packages can actually do this fairly
> automatically. I take a different route because I eschew using
> pdflatex. I have Makefiles that will automatically generate EPS's from
> any other file type as needed (e.g., if I use \includegraphics{blah}
> and there is a blah.gif in the directory, the Makefile will convert
> blah.gif to blah.eps before running LaTeX). IIRC, there are similar
> automatic conversion facilities built into some of the most
> sophisticated LaTeX build scripts (e.g., "rubber").
>
> Anyway, I'm glad you're both up and running. And I'm glad that now I
> know about that configuration parameter -- it was something I took for
> granted before you're issue was posted!
>
> Best --
> Ted
>
> --
> Ted Pavlic <te...@te...>
>



-- 
www.itabeta.org

First published in September 1843 to take part in "a severe contest
between intelligence, which presses forward, and an unworthy, timid
ignorance obstructing our progress"

Re: [Vim-latex-devel] [Question] Bibtex compiling

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

> That's good because as far as I know compiling in dvi does not allow
> to use \includefigures using pdf files, right? So it was not an
> option!

Using latex (as opposed to pdflatex) means all of your graphics have
to be EPS files. You can use pdflatex to include PDF, PNG, JPG, or
GIF, but pdflatex will not include EPS files. A major downside of not
being able to use EPS natively is that you lose out on all of the
great features of EPS. For example, PSTricks (a LaTeX drawing package)
can do very advanced things because it leverages the power of EPS. In
particular, PSTricks can do math within graphics that lets you (for
example) solve differential equations during the compilation of your
document.

[ Personally, I hate including MATLAB figures within a nicely
formatted LaTeX document. Even though MATLAB has some crude
LaTeX/Computer-Modern-font support that you can put into figs, the
figures always make a nice document look worse. An old officemate of
mine would use the psfrag package (which also requires using EPS) to
solve this problem. MATLAB puts dummy symbols throughout the fig, and
psfrag can replace them on-the-fly with text rendered from the
document. However, the graphics themselves still lack the smooth look
that LaTeX provides. So I don't even generate figs from MATLAB; I have
MATLAB export data and use PSTricks to plot that data natively within
LaTeX. The result is a document without seems. ]

There are several packages that allow you to include pdflatex-friendly
files in latex (and probably vice versa). They essentially run a small
pass of pdflatex or a converter program to generate EPS files from the
PDF's you want to include. The packages can actually do this fairly
automatically. I take a different route because I eschew using
pdflatex. I have Makefiles that will automatically generate EPS's from
any other file type as needed (e.g., if I use \includegraphics{blah}
and there is a blah.gif in the directory, the Makefile will convert
blah.gif to blah.eps before running LaTeX). IIRC, there are similar
automatic conversion facilities built into some of the most
sophisticated LaTeX build scripts (e.g., "rubber").

Anyway, I'm glad you're both up and running. And I'm glad that now I
know about that configuration parameter -- it was something I took for
granted before you're issue was posted!

Best --
Ted

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

[Vim-latex-devel] Bug: Tex_MakeMap remaps <F1> key

[ZyX <zy...@np...>]

The problem is caused by hasmapto() function which does not accept special keys 
in «<Key>» form. The attached patch fixes this (replaces hasmapto() with 
<unique>).

Re: [Vim-latex-devel] [Question] Bibtex compiling

[Gianluca M. <gia...@gm...>]

Hi,

just added

let g:Tex_MultipleCompileFormats = 'pdf'

to my ~/.vimrc and everything works fine.

That's good because as far as I know compiling in dvi does not allow
to use \includefigures using pdf files, right? So it was not an
option!

Also replaced Preview with Skim!

Thanks for the suggestions

Gianluca

Re: [Vim-latex-devel] [Question] Bibtex compiling

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

That's interesting. I have a feeling the view rule is not doing it -- 
can you comment out just the DefaultTargetFormat (i.e., leave the 
ViewRule uncommented) to see if the problem goes away?

[ additionally, have you looked at Skim as a replacement for Preview? 
Skim has lots of LaTeX friendly features (although Preview certainly got 
better in 10.5 and 10.6). Back when I used a Mac, it was hands down the 
best PDF viewer available for any operating system; Skim was actually 
the primary reason I kept my Mac for so long ]

Back when I used Vim-LaTeX to build PDF's, I still wanted to use latex 
because of my reliance on PSTricks. Hence, I just set Vim-LaTeX's target 
to "dvi" and then manually edited the build lines to also call dvips and 
ps2pdf. However, I am pretty sure I had little trouble getting bibtex to 
run even with the PDF target. Regardless, if setting the target to "dvi" 
fixes the problem, then I advise you to do something similar -- just set 
your target to dvi, but then manually set the DVI build rule to be the 
PDF build rule.

An old officemate of mine used to use Vim-LaTeX to build PDF's. Instead 
of doing it the ugly way I did it, he actually used the Vim-LaTeX 
dependency setup. Look at the latex-suite help. You can tell LaTeX to 
build a pdf but have the pdf target depend on the dvi target. 
Consequently, it will stabilize the dvi before converting to pdf. This 
is probably the "sanctioned" way of fixing your problem if it is the pdf 
target that is causing it.

--Ted

On 07/02/2010 12:26 PM, Gianluca Meneghello wrote:
> Hi there,
>
> I have the same problem and maybe I have found a reason for it, if not
> the solution!
>
> I'm on Mac OS X 10.6.4, vim 7.2.108 (the one shipped with the OS).
>
> Because vim-latex was compiling as dvi instead of pdf, I added this
> two lines at the end of ~/.vimrc
>
> let g:Tex_DefaultTargetFormat = 'pdf'
> let g:Tex_ViewRule_pdf = 'open -a Preview.app'
>
> so that now it does compile a pdf, but does not call bibtex or
> recompile in case of label changing (e.g. inserting a new table). In
> the last case it gives the following warning
>
> pippo.tex|| LaTeX Warning: Label(s) may have changed. Rerun to get
> cross-references right.
>
> If I comment out the two lines in ~/.vimrc vimlatex calls biblatex and
> recompile all the necessary times correctly.
>
> Hope this can somehow help... and if there is a solution I would be
> happy to know!!
>
> gianlu
>
> On 2 July 2010 18:06, Ted Pavlic<te...@te...>  wrote:
>> Abbie --
>>
>> One last thing to look for... Do you have any ".latexmain" files in your
>> project? I haven't tested it, but if you have a latexmain that has a
>> different name than your project, then maybe Vim-LaTeX wouldn't be able
>> to find it... (I would think this might break the entire latex build
>> though...) I'm just throwing spaghetti at the refrigerator here.
>>
>> An alternative approach is to just use one of the many LaTeX build
>> scripts out there (e.g., "rubber" is a popular one as is "latexmk").
>> These scripts automatically figure out what needs to be done (as
>> Vim-LaTeX is supposed to) when you execute them once. You can then
>> configure Vim-LaTeX to call them on \ll, or you can tell Vim to use them
>> as your "make" program and execute them as you would a compiler within
>> Vim. Moreover, if Vim-LaTeX finds a "Makefile" in your project
>> directory, it will use it rather than its own build rules (e.g., it
>> calls "make pdf" intsead of "pdflatex ..." and counts on your Makefile
>> knowing what to do). There are several "LaTeX Makefiles" out there as
>> well (but few of them have the features of, say, rubber).
>>
>> That approach is actually similar to what I do in my own projects. I
>> find that most of these latex build scripts aren't as full featured as I
>> need. For example, I want to put a MATLAB script "myfigure.m" in my
>> project directory and have the build script automatically call MATLAB to
>> run it if "myfigure.eps" doesn't exist and then automatically convert
>> "myfigure.eps" to "myfigure.png" if needed (e.g., if I'm using pdflatex
>> instead of latex). The build scripts can usually do some of that, and
>> they can be extended, but eventually it becomes easier for me to just
>> write my own. So I did my best to build a very full featured Makefile
>> (the only downside is that "make" takes a lot longer to run than, say,
>> perl or python). It does everything *I* need and doesn't take much
>> longer to run than Vim-LaTeX cycling through latex/bibtex/etc. Plus,
>> it's easy for me to call it from the command line ("make doc" does
>> everything, and "make dvi" or "make pdf" does things that make Vim-LaTeX
>> happy).
>>
>> If you're interested, check out the "document_template" set of Makefiles
>> that I use for my publications (articles, slides, etc.):
>>
>> http://hg.tedpavlic.com/templates/document_template/
>>
>> (that's a Mercurial repository; if you want an unversioned snapshot of
>> the repo, click on "files" and then click on "bz2" "zip" or "gz" to get
>> your archive of choice)
>>
>> You can find some sample docs constructed with that template at:
>>
>> http://hg.tedpavlic.com/docs/
>>
>> and at:
>>
>> http://pubs.tedpavlic.com/hg/
>>
>> (although the "Pavlic07" link was constructed using a different
>> approach; the rest use document_template as a base... and there will be
>> some additional publications there soon once they go from being
>> "accepted" to being in print)
>>
>> So maybe that will give you some ideas...<?>  Good luck --
>> Ted
>>
>> On 07/01/2010 05:25 PM, Abbie Kressner wrote:
>>> ":!bibtex %:r" successfully runs.
>>>
>>> I fixed the $PATH issue, so ":!which bibtex" now yields
>>> "/usr/texbin/bibtex".
>>>
>>> I installed the latest /stable/ version of MacVim (Version 7.2 stable
>>> 1.2 (33.3) in place of Snapshot 52), and the "Launch Vim processes in a
>>> login shell" option appeared in the General tab of the preferences.  I
>>> checked that.
>>>
>>> However, \ll still does not successfully call bibtex.  I'm not sure what
>>> is causing the problem, but I think I will just accept it as is right now.
>>>
>>> Thanks again for all of your help!
>>>
>>> On Thu, Jul 1, 2010 at 4:33 PM, Ted Pavlic<te...@te...
>>> <mailto:te...@te...>>  wrote:
>>>
>>>          I found some good information here:
>>>          http://phaseportrait.blogspot.com/2007/12/file-associations-and-path-with-macvim.html
>>>
>>>
>>>      I wrote that a long time ago (back when I used to run a PowerPC Mac
>>>      on OS X 10.4; I'm not on a Mac anymore now, and so I can't verify).
>>>      Maybe they've removed that preference... Type:
>>>
>>>      :h macvim-login-shell
>>>
>>>      inside Vim to see if that help page still exists. If it does, it
>>>      should tell you where to find the preference. That help page existed
>>>      in April of 2010, and so I'm guessing it should still exist now.
>>>
>>>
>>>      (either way, I'm starting to suspect the problem has less to do with
>>>      Vim-LaTeX and more to do with your Vim environment)
>>>
>>>      The vim-mac mailing list (where MacVim discussions go on) can be
>>>      accessed via Google Groups at:
>>>
>>>      http://groups.google.com/group/vim_mac?pli=1
>>>
>>>      If you search for "login shell" and sort by date, you'll find recent
>>>      messages discussing the preference. I get the impression that it is
>>>      now turned on by default. If it is, you could try turning it off. I
>>>      don't remember, but I *THINK* using (at a Terminal prompt)
>>>
>>>      defaults write org.vim.MacVim MMLoginShell 0
>>>
>>>      will turn it off (but maybe that was a hidden setting for something
>>>      else). There used to be a checkbox in the MacVim preferences that
>>>      let you control the pref... Maybe they made it all hidden now (via
>>>      the "MMLoginShell" hidden pref)... The details should be in that ":h
>>>      macvim-login-shell"
>>>
>>>      --Ted
>>>
>>>
>>>
>>>
>>>          <http://phaseportrait.blogspot.com/2007/12/file-associations-and-path-with-macvim.html>However,
>>>          I don't see the preference pane you mention that allows you to
>>>          "launch
>>>          Vim processes in a login shell."  I am at Snapshot 52 of MacVim,
>>>          and I
>>>          believe that is the latest version.  Am I incorrect?
>>>
>>>          On Thu, Jul 1, 2010 at 4:01 PM, Abbie Kressner
>>>          <abb...@gm...<mailto:abb...@gm...>
>>>          <mailto:abb...@gm...
>>>          <mailto:abb...@gm...>>>  wrote:
>>>
>>>              I am using MacVim, and :!which bibtex produces the following:
>>>
>>>              /usr/texbin//bibtex
>>>
>>>              This looks to be my problem since I think it should be
>>>              /usr/texbin/bibtex.  How would I go about changing that to
>>>          be correct?
>>>
>>>              // Abbie
>>>
>>>
>>>              On Thu, Jul 1, 2010 at 3:56 PM, Ted Pavlic
>>>          <te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>  wrote:
>>>
>>>                  Abbie --
>>>
>>>                          It works fine for me -- \ll runs LaTeX and
>>>          BibTeX and
>>>                  generates the BBL properly. (however, there was one
>>>          \end{figure}
>>>                  that wasn't commented out in the TeX you sent, but you
>>>          said you
>>>                  just now commented those out, and so that wouldn't be
>>>          the source
>>>                  of the problem)
>>>
>>>                          I'm starting to suspect that vim isn't picking
>>>          up your
>>>                  path the way it should (though I'm not sure why it's not
>>>          having
>>>                  trouble running latex). Are you using vim, gvim, or
>>>          MacVim? I
>>>                  know you're running a Mac, and there are lots of
>>>          different ways
>>>                  to run vim on a Mac.
>>>
>>>                          Inside vim (however you run it), can you type
>>>
>>>                  :!which bibtex
>>>
>>>                  That is, the "colon" puts you into command mode, then the
>>>                  exclamation point will cause vim to run "which bibtex". You
>>>                  should see something like...
>>>
>>>                  /usr/bin/bibtex
>>>
>>>                  and then be prompted to press ENTER to continue. If you
>>>          instead
>>>                  see something like "which: no bibtex in (...)", then vim
>>>          isn't
>>>                  importing your path properly (in MacVim, you have to
>>>          turn on a
>>>                  special option use login shells so that commands run
>>>          from vim
>>>                  are setup with your path).
>>>
>>>                          --Ted
>>>
>>>
>>>                  On 07/01/2010 03:12 PM, Abbie Kressner wrote:
>>>
>>>                      I have attached a tex file where I have commented
>>>          out the
>>>                      figures
>>>                      sections.  I have also attached a bib file that I just
>>>                      created that only
>>>                      contains the references that I use (there are
>>>          currently just
>>>                      two).
>>>
>>>                      I am not sure what you mean by "status line in Vim".
>>>            I see
>>>                      a bunch of
>>>                      information flash across the window when I compile,
>>>          and then
>>>                      it all
>>>                      disappears when there is no "process-stopping"
>>>          error.  It
>>>                      goes pretty
>>>                      fast, so I don't have a chance to see what it says.  I
>>>                      looked at the log
>>>                      file, but couldn't find anywhere that it
>>>          specifically says
>>>                      it compiled
>>>                      bibtex.  The following is the only relevant
>>>          information I
>>>                      could find...
>>>
>>>                          ]
>>>                          No file *.bbl.
>>>                          [14
>>>
>>>
>>>                      where * is the actual base filename.
>>>
>>>                      I just recently downloaded Vim-Latex in the last
>>>          week or so,
>>>                      so it would
>>>                      be strange if it was out-dated.  I found the
>>>          following in
>>>                      compiler.vim
>>>                      that I believe you were referring to.
>>>
>>>          " The first time we see if we need to run bibtex and if the
>>>                      .bbl file
>>>
>>>          " changes, we will rerun latex.
>>>                      if runCount == 0&&  Tex_IsPresentInFile('\\bibdata',
>>>                      mainFileName_root.'.aux')
>>>                      let bibFileName = mainFileName_root.'.bbl'
>>>
>>>                      let biblinesBefore = Tex_CatFile(bibFileName)
>>>
>>>                      echomsg "Running
>>>          '".Tex_GetVarValue('Tex_BibtexFlavor')."' ..."
>>>                      let temp_mp =&mp | let&mp =
>>>                      Tex_GetVarValue('Tex_BibtexFlavor')
>>>                      exec 'silent! make '.mainFileName_root
>>>                      let&mp = temp_mp
>>>
>>>                      let biblinesAfter = Tex_CatFile(bibFileName)
>>>
>>>          " If the .bbl file changed after running bibtex, we need to
>>>          " latex again.
>>>                      if biblinesAfter != biblinesBefore
>>>                      echomsg 'Need to rerun because bibliography file
>>>          changed...'
>>>                      call Tex_Debug('Tex_CompileMultipleTimes: Need to
>>>          rerun because
>>>                      bibliography file changed...', 'comp')
>>>                      let needToRerun = 1
>>>                      endif
>>>                      endif
>>>
>>>                      Does anything seem to be wrong?
>>>
>>>                      Once again, thank you so much for taking the time to
>>>          help me!!
>>>
>>>
>>>                      On Thu, Jul 1, 2010 at 2:36 PM, Ted Pavlic
>>>          <te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>>  wrote:
>>>
>>>                          Hm. All of that works for me. \ll runs LaTeX
>>>          three times
>>>                      with
>>>                          relevant runs of bibtex in between to build the BBL.
>>>
>>>                          Could you send a complete minimal non-working
>>>          example?
>>>                      Something
>>>                          that can be immediately opened in Vim (perhaps
>>>          even with
>>>                      a minimal
>>>                          bib, but I don't think the bib will matter; I
>>>          can sub my
>>>                      own bib in)
>>>                          that causes you problems when you \ll it.
>>>
>>>                          After you run \ll, what does the status line in
>>>          Vim say? For
>>>                          example, mine says "Run latex 3 time(s)" right now.
>>>                      Also, while \ll
>>>                          is running, can you catch a glimpse of some of
>>>          the other
>>>                      status
>>>                          messages? It should report if/when it tries to
>>>          run bibtex.
>>>
>>>                          Also, if you look where Vim-LaTeX is installed
>>>          (e.g., in
>>>                      your
>>>                          .vim/ftplugin/latex-suite/ or in
>>>                          /usr/share/vim/vimfiles/ftplugin/latex-suite/ or
>>>          similar
>>>                      on your
>>>                          system), you should find a "compiler.vim" that
>>>          has the
>>>                      Vim script
>>>                          that implements \ll. Is it possible that you
>>>          have a very
>>>                      very old
>>>                          version of Vim-LaTeX that doesn't yet run
>>>          bibtex? Search
>>>                      through
>>>                          that file for "bibdata" -- you should find the
>>>          relevant
>>>                      section of
>>>                          code that checks the AUX file for bibdata and runs
>>>                      bibtex as needed.
>>>                          You will also notice it references configuration
>>>                      variables that can
>>>                          be changed by the user. It's possible that your
>>>          defaults
>>>                      are either
>>>                          set wrong or have been changed (?).
>>>
>>>                          --Ted
>>>
>>>
>>>                          On 07/01/2010 01:24 PM, Abbie Kressner wrote:
>>>
>>>                              As far as I can tell, there are no errors.  I
>>>                      deleted all the files
>>>                              except the tex file and reran the \ll compile
>>>                      command.  The aux file
>>>                              contains the following lines.
>>>
>>>                                  \bibstyle{IEEEtran}
>>>
>>>            \bibdata{/Users/abbiekre/Documents/_Papers/_Papers}
>>>
>>>
>>>                              Also, here are the relevant lines in my
>>>          beamer tex file.
>>>
>>>                                  \appendix
>>>                                  \begin{frame}[allowframebreaks]
>>>
>>>                                      \textbf{References}
>>>
>>>                                      \bibliographystyle{IEEEtran}
>>>
>>>                                  \bibliography{_Papers}
>>>                                  \end{frame}
>>>
>>>
>>>                              Do you see any blaring errors?  Any other
>>>          ideas if not?
>>>
>>>                              Thanks!
>>>
>>>                              // Abbie
>>>
>>>                              Thanks in advance for anymore help!
>>>            Hopefully I'll
>>>                      find a solution
>>>                              eventually.
>>>
>>>                              On Thu, Jul 1, 2010 at 12:38 PM, Ted Pavlic
>>>          <te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>>>  wrote:
>>>
>>>                                  Abbie --
>>>
>>>                                  Are you sure your LaTeX run isn't
>>>          causing an error?
>>>                              Vim-LaTeX will
>>>                                  cease processing on an error. There may be a
>>>                      subtle LaTeX error
>>>                                  causing the Vim-LaTeX compiler to halt early
>>>                      (although that
>>>                              usually
>>>                                  would cause Vim-LaTeX to report an error).
>>>
>>>                                  After LaTeX is run (by Vim-LaTeX), an
>>>          "AUX" file
>>>                      should be
>>>                              created.
>>>                                  That "AUX" file should have a line in it
>>>          that
>>>                      has "\bibdata"
>>>                              in it.
>>>                                  It is that line that causes Vim-LaTeX to
>>>          call
>>>                      bibtex.
>>>
>>>                                  Are there other details that might be
>>>          confusing
>>>                      Vim-LaTeX?
>>>                              (e.g.,
>>>                                  spaces in file names, etc.?)
>>>
>>>                                  --Ted
>>>
>>>
>>>                                  On 07/01/2010 12:33 PM, Abbie Kressner
>>>          wrote:
>>>
>>>                                      Thank you, Ted!
>>>
>>>                                      I still haven't been able to get the \ll
>>>                      compiler command to
>>>                                      successful
>>>                                      compile a .bbl file.  Any help would be
>>>                      greatly appreciated!
>>>
>>>                                      My current workaround is to call bibtex
>>>                      manually from
>>>                              Terminal.
>>>                                        Then
>>>                                      when I compile with \ll in MATLAB,
>>>          the citations
>>>                              correctly turn
>>>                                      from "?"
>>>                                      to numbers, and my reference page
>>>          displays
>>>                      correctly (rather
>>>                                      than being
>>>                                      blank).  Removing the extra steps
>>>          involved
>>>                      in compiling
>>>                              would be
>>>                                      fantastic though!
>>>
>>>                                      On Thu, Jul 1, 2010 at 12:14 PM, Ted
>>>          Pavlic
>>>          <te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>>>>  wrote:
>>>
>>>                                          Abbie --
>>>
>>>
>>>                                          On 06/30/2010 04:46 PM, Abbie
>>>          Kressner
>>>                      wrote:
>>>
>>>                                              Do you happen to know what
>>>          to do if
>>>                      \ll does not
>>>                              call
>>>                                      bibtex?
>>>
>>>
>>>                                                  I'm responding to this
>>>          message
>>>                      via the
>>>                                      vim-latex-devel list.
>>>                                          I've BCC'd you, but I advise you to
>>>                      continue this
>>>                              thread on
>>>                                      the list
>>>                                          where others can help too.
>>>
>>>                                                  So long as your LaTeX
>>>          file has a
>>>                      \bibliography{}
>>>                                      line in it,
>>>                                          the \ll compiler command will issue
>>>                      bibtex sa needed. If
>>>                                      your LaTeX
>>>                                          file only has a \bibliography style
>>>                      command but no
>>>                              \bibliography
>>>                                          command, then Vim-LaTeX won't
>>>          know to
>>>                      run bibtex. In
>>>                              fact,
>>>                                      in these
>>>                                          cases where there is no
>>>          \bibliography
>>>                      command, if
>>>                              you try to run
>>>                                          bibtex manually it will give you
>>>          an error.
>>>
>>>                                                  Of course, there is more
>>>          than
>>>                      one way to
>>>                              skin a cat.
>>>                                          However, I'm confident that if your
>>>                      LaTeX document is
>>>                                      properly setup
>>>                                          for including a BibTeX bibliogrpahy,
>>>                      then Vim-LaTeX will
>>>                                      make the
>>>                                          appropriate calls for you (using
>>>          \ll).
>>>
>>>
>>>                                                  Best --
>>>                                                  Ted
>>>
>>>                                          --
>>>                                          Ted Pavlic<te...@te...
>>>          <mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>>>>
>>>
>>>
>>>
>>>                                            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.
>>>
>>>
>>>
>>>                                  --
>>>                                  Ted Pavlic<te...@te...
>>>          <mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>>>
>>>
>>>                                    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.
>>>
>>>
>>>
>>>                          --
>>>                          Ted Pavlic<te...@te...
>>>          <mailto:te...@te...>  <mailto:te...@te...
>>>          <mailto:te...@te...>>
>>>          <mailto:te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>>
>>>
>>>                            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.
>>>
>>>
>>>
>>>                  --
>>>                  Ted Pavlic<te...@te...<mailto:te...@te...>
>>>          <mailto:te...@te...<mailto:te...@te...>>>
>>>
>>>                    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.
>>>
>>>
>>>
>>>
>>>      --
>>>      Ted Pavlic<te...@te...<mailto:te...@te...>>
>>>
>>>        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.
>>>
>>>
>>
>> --
>> Ted Pavlic<te...@te...>
>>
>>    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.
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Sprint
>> What will you do first with EVO, the first 4G phone?
>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>
>
>
>

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

   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.

Re: [Vim-latex-devel] [Question] Bibtex compiling

[Gianluca M. <gia...@gm...>]

Hi there,

I have the same problem and maybe I have found a reason for it, if not
the solution!

I'm on Mac OS X 10.6.4, vim 7.2.108 (the one shipped with the OS).

Because vim-latex was compiling as dvi instead of pdf, I added this
two lines at the end of ~/.vimrc

let g:Tex_DefaultTargetFormat = 'pdf'
let g:Tex_ViewRule_pdf = 'open -a Preview.app'

so that now it does compile a pdf, but does not call bibtex or
recompile in case of label changing (e.g. inserting a new table). In
the last case it gives the following warning

pippo.tex|| LaTeX Warning: Label(s) may have changed. Rerun to get
cross-references right.

If I comment out the two lines in ~/.vimrc vimlatex calls biblatex and
recompile all the necessary times correctly.

Hope this can somehow help... and if there is a solution I would be
happy to know!!

gianlu

On 2 July 2010 18:06, Ted Pavlic <te...@te...> wrote:
> Abbie --
>
> One last thing to look for... Do you have any ".latexmain" files in your
> project? I haven't tested it, but if you have a latexmain that has a
> different name than your project, then maybe Vim-LaTeX wouldn't be able
> to find it... (I would think this might break the entire latex build
> though...) I'm just throwing spaghetti at the refrigerator here.
>
> An alternative approach is to just use one of the many LaTeX build
> scripts out there (e.g., "rubber" is a popular one as is "latexmk").
> These scripts automatically figure out what needs to be done (as
> Vim-LaTeX is supposed to) when you execute them once. You can then
> configure Vim-LaTeX to call them on \ll, or you can tell Vim to use them
> as your "make" program and execute them as you would a compiler within
> Vim. Moreover, if Vim-LaTeX finds a "Makefile" in your project
> directory, it will use it rather than its own build rules (e.g., it
> calls "make pdf" intsead of "pdflatex ..." and counts on your Makefile
> knowing what to do). There are several "LaTeX Makefiles" out there as
> well (but few of them have the features of, say, rubber).
>
> That approach is actually similar to what I do in my own projects. I
> find that most of these latex build scripts aren't as full featured as I
> need. For example, I want to put a MATLAB script "myfigure.m" in my
> project directory and have the build script automatically call MATLAB to
> run it if "myfigure.eps" doesn't exist and then automatically convert
> "myfigure.eps" to "myfigure.png" if needed (e.g., if I'm using pdflatex
> instead of latex). The build scripts can usually do some of that, and
> they can be extended, but eventually it becomes easier for me to just
> write my own. So I did my best to build a very full featured Makefile
> (the only downside is that "make" takes a lot longer to run than, say,
> perl or python). It does everything *I* need and doesn't take much
> longer to run than Vim-LaTeX cycling through latex/bibtex/etc. Plus,
> it's easy for me to call it from the command line ("make doc" does
> everything, and "make dvi" or "make pdf" does things that make Vim-LaTeX
> happy).
>
> If you're interested, check out the "document_template" set of Makefiles
> that I use for my publications (articles, slides, etc.):
>
> http://hg.tedpavlic.com/templates/document_template/
>
> (that's a Mercurial repository; if you want an unversioned snapshot of
> the repo, click on "files" and then click on "bz2" "zip" or "gz" to get
> your archive of choice)
>
> You can find some sample docs constructed with that template at:
>
> http://hg.tedpavlic.com/docs/
>
> and at:
>
> http://pubs.tedpavlic.com/hg/
>
> (although the "Pavlic07" link was constructed using a different
> approach; the rest use document_template as a base... and there will be
> some additional publications there soon once they go from being
> "accepted" to being in print)
>
> So maybe that will give you some ideas... <?> Good luck --
> Ted
>
> On 07/01/2010 05:25 PM, Abbie Kressner wrote:
>> ":!bibtex %:r" successfully runs.
>>
>> I fixed the $PATH issue, so ":!which bibtex" now yields
>> "/usr/texbin/bibtex".
>>
>> I installed the latest /stable/ version of MacVim (Version 7.2 stable
>> 1.2 (33.3) in place of Snapshot 52), and the "Launch Vim processes in a
>> login shell" option appeared in the General tab of the preferences.  I
>> checked that.
>>
>> However, \ll still does not successfully call bibtex.  I'm not sure what
>> is causing the problem, but I think I will just accept it as is right now.
>>
>> Thanks again for all of your help!
>>
>> On Thu, Jul 1, 2010 at 4:33 PM, Ted Pavlic <te...@te...
>> <mailto:te...@te...>> wrote:
>>
>>         I found some good information here:
>>         http://phaseportrait.blogspot.com/2007/12/file-associations-and-path-with-macvim.html
>>
>>
>>     I wrote that a long time ago (back when I used to run a PowerPC Mac
>>     on OS X 10.4; I'm not on a Mac anymore now, and so I can't verify).
>>     Maybe they've removed that preference... Type:
>>
>>     :h macvim-login-shell
>>
>>     inside Vim to see if that help page still exists. If it does, it
>>     should tell you where to find the preference. That help page existed
>>     in April of 2010, and so I'm guessing it should still exist now.
>>
>>
>>     (either way, I'm starting to suspect the problem has less to do with
>>     Vim-LaTeX and more to do with your Vim environment)
>>
>>     The vim-mac mailing list (where MacVim discussions go on) can be
>>     accessed via Google Groups at:
>>
>>     http://groups.google.com/group/vim_mac?pli=1
>>
>>     If you search for "login shell" and sort by date, you'll find recent
>>     messages discussing the preference. I get the impression that it is
>>     now turned on by default. If it is, you could try turning it off. I
>>     don't remember, but I *THINK* using (at a Terminal prompt)
>>
>>     defaults write org.vim.MacVim MMLoginShell 0
>>
>>     will turn it off (but maybe that was a hidden setting for something
>>     else). There used to be a checkbox in the MacVim preferences that
>>     let you control the pref... Maybe they made it all hidden now (via
>>     the "MMLoginShell" hidden pref)... The details should be in that ":h
>>     macvim-login-shell"
>>
>>     --Ted
>>
>>
>>
>>
>>         <http://phaseportrait.blogspot.com/2007/12/file-associations-and-path-with-macvim.html>However,
>>         I don't see the preference pane you mention that allows you to
>>         "launch
>>         Vim processes in a login shell."  I am at Snapshot 52 of MacVim,
>>         and I
>>         believe that is the latest version.  Am I incorrect?
>>
>>         On Thu, Jul 1, 2010 at 4:01 PM, Abbie Kressner
>>         <abb...@gm... <mailto:abb...@gm...>
>>         <mailto:abb...@gm...
>>         <mailto:abb...@gm...>>> wrote:
>>
>>             I am using MacVim, and :!which bibtex produces the following:
>>
>>             /usr/texbin//bibtex
>>
>>             This looks to be my problem since I think it should be
>>             /usr/texbin/bibtex.  How would I go about changing that to
>>         be correct?
>>
>>             // Abbie
>>
>>
>>             On Thu, Jul 1, 2010 at 3:56 PM, Ted Pavlic
>>         <te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>> wrote:
>>
>>                 Abbie --
>>
>>                         It works fine for me -- \ll runs LaTeX and
>>         BibTeX and
>>                 generates the BBL properly. (however, there was one
>>         \end{figure}
>>                 that wasn't commented out in the TeX you sent, but you
>>         said you
>>                 just now commented those out, and so that wouldn't be
>>         the source
>>                 of the problem)
>>
>>                         I'm starting to suspect that vim isn't picking
>>         up your
>>                 path the way it should (though I'm not sure why it's not
>>         having
>>                 trouble running latex). Are you using vim, gvim, or
>>         MacVim? I
>>                 know you're running a Mac, and there are lots of
>>         different ways
>>                 to run vim on a Mac.
>>
>>                         Inside vim (however you run it), can you type
>>
>>                 :!which bibtex
>>
>>                 That is, the "colon" puts you into command mode, then the
>>                 exclamation point will cause vim to run "which bibtex". You
>>                 should see something like...
>>
>>                 /usr/bin/bibtex
>>
>>                 and then be prompted to press ENTER to continue. If you
>>         instead
>>                 see something like "which: no bibtex in (...)", then vim
>>         isn't
>>                 importing your path properly (in MacVim, you have to
>>         turn on a
>>                 special option use login shells so that commands run
>>         from vim
>>                 are setup with your path).
>>
>>                         --Ted
>>
>>
>>                 On 07/01/2010 03:12 PM, Abbie Kressner wrote:
>>
>>                     I have attached a tex file where I have commented
>>         out the
>>                     figures
>>                     sections.  I have also attached a bib file that I just
>>                     created that only
>>                     contains the references that I use (there are
>>         currently just
>>                     two).
>>
>>                     I am not sure what you mean by "status line in Vim".
>>           I see
>>                     a bunch of
>>                     information flash across the window when I compile,
>>         and then
>>                     it all
>>                     disappears when there is no "process-stopping"
>>         error.  It
>>                     goes pretty
>>                     fast, so I don't have a chance to see what it says.  I
>>                     looked at the log
>>                     file, but couldn't find anywhere that it
>>         specifically says
>>                     it compiled
>>                     bibtex.  The following is the only relevant
>>         information I
>>                     could find...
>>
>>                         ]
>>                         No file *.bbl.
>>                         [14
>>
>>
>>                     where * is the actual base filename.
>>
>>                     I just recently downloaded Vim-Latex in the last
>>         week or so,
>>                     so it would
>>                     be strange if it was out-dated.  I found the
>>         following in
>>                     compiler.vim
>>                     that I believe you were referring to.
>>
>>         " The first time we see if we need to run bibtex and if the
>>                     .bbl file
>>
>>         " changes, we will rerun latex.
>>                     if runCount == 0 && Tex_IsPresentInFile('\\bibdata',
>>                     mainFileName_root.'.aux')
>>                     let bibFileName = mainFileName_root.'.bbl'
>>
>>                     let biblinesBefore = Tex_CatFile(bibFileName)
>>
>>                     echomsg "Running
>>         '".Tex_GetVarValue('Tex_BibtexFlavor')."' ..."
>>                     let temp_mp = &mp | let &mp =
>>                     Tex_GetVarValue('Tex_BibtexFlavor')
>>                     exec 'silent! make '.mainFileName_root
>>                     let &mp = temp_mp
>>
>>                     let biblinesAfter = Tex_CatFile(bibFileName)
>>
>>         " If the .bbl file changed after running bibtex, we need to
>>         " latex again.
>>                     if biblinesAfter != biblinesBefore
>>                     echomsg 'Need to rerun because bibliography file
>>         changed...'
>>                     call Tex_Debug('Tex_CompileMultipleTimes: Need to
>>         rerun because
>>                     bibliography file changed...', 'comp')
>>                     let needToRerun = 1
>>                     endif
>>                     endif
>>
>>                     Does anything seem to be wrong?
>>
>>                     Once again, thank you so much for taking the time to
>>         help me!!
>>
>>
>>                     On Thu, Jul 1, 2010 at 2:36 PM, Ted Pavlic
>>         <te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>> wrote:
>>
>>                         Hm. All of that works for me. \ll runs LaTeX
>>         three times
>>                     with
>>                         relevant runs of bibtex in between to build the BBL.
>>
>>                         Could you send a complete minimal non-working
>>         example?
>>                     Something
>>                         that can be immediately opened in Vim (perhaps
>>         even with
>>                     a minimal
>>                         bib, but I don't think the bib will matter; I
>>         can sub my
>>                     own bib in)
>>                         that causes you problems when you \ll it.
>>
>>                         After you run \ll, what does the status line in
>>         Vim say? For
>>                         example, mine says "Run latex 3 time(s)" right now.
>>                     Also, while \ll
>>                         is running, can you catch a glimpse of some of
>>         the other
>>                     status
>>                         messages? It should report if/when it tries to
>>         run bibtex.
>>
>>                         Also, if you look where Vim-LaTeX is installed
>>         (e.g., in
>>                     your
>>                         .vim/ftplugin/latex-suite/ or in
>>                         /usr/share/vim/vimfiles/ftplugin/latex-suite/ or
>>         similar
>>                     on your
>>                         system), you should find a "compiler.vim" that
>>         has the
>>                     Vim script
>>                         that implements \ll. Is it possible that you
>>         have a very
>>                     very old
>>                         version of Vim-LaTeX that doesn't yet run
>>         bibtex? Search
>>                     through
>>                         that file for "bibdata" -- you should find the
>>         relevant
>>                     section of
>>                         code that checks the AUX file for bibdata and runs
>>                     bibtex as needed.
>>                         You will also notice it references configuration
>>                     variables that can
>>                         be changed by the user. It's possible that your
>>         defaults
>>                     are either
>>                         set wrong or have been changed (?).
>>
>>                         --Ted
>>
>>
>>                         On 07/01/2010 01:24 PM, Abbie Kressner wrote:
>>
>>                             As far as I can tell, there are no errors.  I
>>                     deleted all the files
>>                             except the tex file and reran the \ll compile
>>                     command.  The aux file
>>                             contains the following lines.
>>
>>                                 \bibstyle{IEEEtran}
>>
>>           \bibdata{/Users/abbiekre/Documents/_Papers/_Papers}
>>
>>
>>                             Also, here are the relevant lines in my
>>         beamer tex file.
>>
>>                                 \appendix
>>                                 \begin{frame}[allowframebreaks]
>>
>>                                     \textbf{References}
>>
>>                                     \bibliographystyle{IEEEtran}
>>
>>                                 \bibliography{_Papers}
>>                                 \end{frame}
>>
>>
>>                             Do you see any blaring errors?  Any other
>>         ideas if not?
>>
>>                             Thanks!
>>
>>                             // Abbie
>>
>>                             Thanks in advance for anymore help!
>>           Hopefully I'll
>>                     find a solution
>>                             eventually.
>>
>>                             On Thu, Jul 1, 2010 at 12:38 PM, Ted Pavlic
>>         <te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>>> wrote:
>>
>>                                 Abbie --
>>
>>                                 Are you sure your LaTeX run isn't
>>         causing an error?
>>                             Vim-LaTeX will
>>                                 cease processing on an error. There may be a
>>                     subtle LaTeX error
>>                                 causing the Vim-LaTeX compiler to halt early
>>                     (although that
>>                             usually
>>                                 would cause Vim-LaTeX to report an error).
>>
>>                                 After LaTeX is run (by Vim-LaTeX), an
>>         "AUX" file
>>                     should be
>>                             created.
>>                                 That "AUX" file should have a line in it
>>         that
>>                     has "\bibdata"
>>                             in it.
>>                                 It is that line that causes Vim-LaTeX to
>>         call
>>                     bibtex.
>>
>>                                 Are there other details that might be
>>         confusing
>>                     Vim-LaTeX?
>>                             (e.g.,
>>                                 spaces in file names, etc.?)
>>
>>                                 --Ted
>>
>>
>>                                 On 07/01/2010 12:33 PM, Abbie Kressner
>>         wrote:
>>
>>                                     Thank you, Ted!
>>
>>                                     I still haven't been able to get the \ll
>>                     compiler command to
>>                                     successful
>>                                     compile a .bbl file.  Any help would be
>>                     greatly appreciated!
>>
>>                                     My current workaround is to call bibtex
>>                     manually from
>>                             Terminal.
>>                                       Then
>>                                     when I compile with \ll in MATLAB,
>>         the citations
>>                             correctly turn
>>                                     from "?"
>>                                     to numbers, and my reference page
>>         displays
>>                     correctly (rather
>>                                     than being
>>                                     blank).  Removing the extra steps
>>         involved
>>                     in compiling
>>                             would be
>>                                     fantastic though!
>>
>>                                     On Thu, Jul 1, 2010 at 12:14 PM, Ted
>>         Pavlic
>>         <te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>>>> wrote:
>>
>>                                         Abbie --
>>
>>
>>                                         On 06/30/2010 04:46 PM, Abbie
>>         Kressner
>>                     wrote:
>>
>>                                             Do you happen to know what
>>         to do if
>>                     \ll does not
>>                             call
>>                                     bibtex?
>>
>>
>>                                                 I'm responding to this
>>         message
>>                     via the
>>                                     vim-latex-devel list.
>>                                         I've BCC'd you, but I advise you to
>>                     continue this
>>                             thread on
>>                                     the list
>>                                         where others can help too.
>>
>>                                                 So long as your LaTeX
>>         file has a
>>                     \bibliography{}
>>                                     line in it,
>>                                         the \ll compiler command will issue
>>                     bibtex sa needed. If
>>                                     your LaTeX
>>                                         file only has a \bibliography style
>>                     command but no
>>                             \bibliography
>>                                         command, then Vim-LaTeX won't
>>         know to
>>                     run bibtex. In
>>                             fact,
>>                                     in these
>>                                         cases where there is no
>>         \bibliography
>>                     command, if
>>                             you try to run
>>                                         bibtex manually it will give you
>>         an error.
>>
>>                                                 Of course, there is more
>>         than
>>                     one way to
>>                             skin a cat.
>>                                         However, I'm confident that if your
>>                     LaTeX document is
>>                                     properly setup
>>                                         for including a BibTeX bibliogrpahy,
>>                     then Vim-LaTeX will
>>                                     make the
>>                                         appropriate calls for you (using
>>         \ll).
>>
>>
>>                                                 Best --
>>                                                 Ted
>>
>>                                         --
>>                                         Ted Pavlic <te...@te...
>>         <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>>>>
>>
>>
>>
>>                                           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.
>>
>>
>>
>>                                 --
>>                                 Ted Pavlic <te...@te...
>>         <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>>>
>>
>>                                   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.
>>
>>
>>
>>                         --
>>                         Ted Pavlic <te...@te...
>>         <mailto:te...@te...> <mailto:te...@te...
>>         <mailto:te...@te...>>
>>         <mailto:te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>>
>>
>>                           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.
>>
>>
>>
>>                 --
>>                 Ted Pavlic <te...@te... <mailto:te...@te...>
>>         <mailto:te...@te... <mailto:te...@te...>>>
>>
>>                   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.
>>
>>
>>
>>
>>     --
>>     Ted Pavlic <te...@te... <mailto:te...@te...>>
>>
>>       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.
>>
>>
>
> --
> Ted Pavlic <te...@te...>
>
>   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.
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>



-- 
www.itabeta.org

First published in September 1843 to take part in "a severe contest
between intelligence, which presses forward, and an unworthy, timid
ignorance obstructing our progress"

Re: [Vim-latex-devel] [Question] Bibtex compiling

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

Abbie --

One last thing to look for... Do you have any ".latexmain" files in your 
project? I haven't tested it, but if you have a latexmain that has a 
different name than your project, then maybe Vim-LaTeX wouldn't be able 
to find it... (I would think this might break the entire latex build 
though...) I'm just throwing spaghetti at the refrigerator here.

An alternative approach is to just use one of the many LaTeX build 
scripts out there (e.g., "rubber" is a popular one as is "latexmk"). 
These scripts automatically figure out what needs to be done (as 
Vim-LaTeX is supposed to) when you execute them once. You can then 
configure Vim-LaTeX to call them on \ll, or you can tell Vim to use them 
as your "make" program and execute them as you would a compiler within 
Vim. Moreover, if Vim-LaTeX finds a "Makefile" in your project 
directory, it will use it rather than its own build rules (e.g., it 
calls "make pdf" intsead of "pdflatex ..." and counts on your Makefile 
knowing what to do). There are several "LaTeX Makefiles" out there as 
well (but few of them have the features of, say, rubber).

That approach is actually similar to what I do in my own projects. I 
find that most of these latex build scripts aren't as full featured as I 
need. For example, I want to put a MATLAB script "myfigure.m" in my 
project directory and have the build script automatically call MATLAB to 
run it if "myfigure.eps" doesn't exist and then automatically convert 
"myfigure.eps" to "myfigure.png" if needed (e.g., if I'm using pdflatex 
instead of latex). The build scripts can usually do some of that, and 
they can be extended, but eventually it becomes easier for me to just 
write my own. So I did my best to build a very full featured Makefile 
(the only downside is that "make" takes a lot longer to run than, say, 
perl or python). It does everything *I* need and doesn't take much 
longer to run than Vim-LaTeX cycling through latex/bibtex/etc. Plus, 
it's easy for me to call it from the command line ("make doc" does 
everything, and "make dvi" or "make pdf" does things that make Vim-LaTeX 
happy).

If you're interested, check out the "document_template" set of Makefiles 
that I use for my publications (articles, slides, etc.):

http://hg.tedpavlic.com/templates/document_template/

(that's a Mercurial repository; if you want an unversioned snapshot of 
the repo, click on "files" and then click on "bz2" "zip" or "gz" to get 
your archive of choice)

You can find some sample docs constructed with that template at:

http://hg.tedpavlic.com/docs/

and at:

http://pubs.tedpavlic.com/hg/

(although the "Pavlic07" link was constructed using a different 
approach; the rest use document_template as a base... and there will be 
some additional publications there soon once they go from being 
"accepted" to being in print)

So maybe that will give you some ideas... <?> Good luck --
Ted

On 07/01/2010 05:25 PM, Abbie Kressner wrote:
> ":!bibtex %:r" successfully runs.
>
> I fixed the $PATH issue, so ":!which bibtex" now yields
> "/usr/texbin/bibtex".
>
> I installed the latest /stable/ version of MacVim (Version 7.2 stable
> 1.2 (33.3) in place of Snapshot 52), and the "Launch Vim processes in a
> login shell" option appeared in the General tab of the preferences.  I
> checked that.
>
> However, \ll still does not successfully call bibtex.  I'm not sure what
> is causing the problem, but I think I will just accept it as is right now.
>
> Thanks again for all of your help!
>
> On Thu, Jul 1, 2010 at 4:33 PM, Ted Pavlic <te...@te...
> <mailto:te...@te...>> wrote:
>
>         I found some good information here:
>         http://phaseportrait.blogspot.com/2007/12/file-associations-and-path-with-macvim.html
>
>
>     I wrote that a long time ago (back when I used to run a PowerPC Mac
>     on OS X 10.4; I'm not on a Mac anymore now, and so I can't verify).
>     Maybe they've removed that preference... Type:
>
>     :h macvim-login-shell
>
>     inside Vim to see if that help page still exists. If it does, it
>     should tell you where to find the preference. That help page existed
>     in April of 2010, and so I'm guessing it should still exist now.
>
>
>     (either way, I'm starting to suspect the problem has less to do with
>     Vim-LaTeX and more to do with your Vim environment)
>
>     The vim-mac mailing list (where MacVim discussions go on) can be
>     accessed via Google Groups at:
>
>     http://groups.google.com/group/vim_mac?pli=1
>
>     If you search for "login shell" and sort by date, you'll find recent
>     messages discussing the preference. I get the impression that it is
>     now turned on by default. If it is, you could try turning it off. I
>     don't remember, but I *THINK* using (at a Terminal prompt)
>
>     defaults write org.vim.MacVim MMLoginShell 0
>
>     will turn it off (but maybe that was a hidden setting for something
>     else). There used to be a checkbox in the MacVim preferences that
>     let you control the pref... Maybe they made it all hidden now (via
>     the "MMLoginShell" hidden pref)... The details should be in that ":h
>     macvim-login-shell"
>
>     --Ted
>
>
>
>
>         <http://phaseportrait.blogspot.com/2007/12/file-associations-and-path-with-macvim.html>However,
>         I don't see the preference pane you mention that allows you to
>         "launch
>         Vim processes in a login shell."  I am at Snapshot 52 of MacVim,
>         and I
>         believe that is the latest version.  Am I incorrect?
>
>         On Thu, Jul 1, 2010 at 4:01 PM, Abbie Kressner
>         <abb...@gm... <mailto:abb...@gm...>
>         <mailto:abb...@gm...
>         <mailto:abb...@gm...>>> wrote:
>
>             I am using MacVim, and :!which bibtex produces the following:
>
>             /usr/texbin//bibtex
>
>             This looks to be my problem since I think it should be
>             /usr/texbin/bibtex.  How would I go about changing that to
>         be correct?
>
>             // Abbie
>
>
>             On Thu, Jul 1, 2010 at 3:56 PM, Ted Pavlic
>         <te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>> wrote:
>
>                 Abbie --
>
>                         It works fine for me -- \ll runs LaTeX and
>         BibTeX and
>                 generates the BBL properly. (however, there was one
>         \end{figure}
>                 that wasn't commented out in the TeX you sent, but you
>         said you
>                 just now commented those out, and so that wouldn't be
>         the source
>                 of the problem)
>
>                         I'm starting to suspect that vim isn't picking
>         up your
>                 path the way it should (though I'm not sure why it's not
>         having
>                 trouble running latex). Are you using vim, gvim, or
>         MacVim? I
>                 know you're running a Mac, and there are lots of
>         different ways
>                 to run vim on a Mac.
>
>                         Inside vim (however you run it), can you type
>
>                 :!which bibtex
>
>                 That is, the "colon" puts you into command mode, then the
>                 exclamation point will cause vim to run "which bibtex". You
>                 should see something like...
>
>                 /usr/bin/bibtex
>
>                 and then be prompted to press ENTER to continue. If you
>         instead
>                 see something like "which: no bibtex in (...)", then vim
>         isn't
>                 importing your path properly (in MacVim, you have to
>         turn on a
>                 special option use login shells so that commands run
>         from vim
>                 are setup with your path).
>
>                         --Ted
>
>
>                 On 07/01/2010 03:12 PM, Abbie Kressner wrote:
>
>                     I have attached a tex file where I have commented
>         out the
>                     figures
>                     sections.  I have also attached a bib file that I just
>                     created that only
>                     contains the references that I use (there are
>         currently just
>                     two).
>
>                     I am not sure what you mean by "status line in Vim".
>           I see
>                     a bunch of
>                     information flash across the window when I compile,
>         and then
>                     it all
>                     disappears when there is no "process-stopping"
>         error.  It
>                     goes pretty
>                     fast, so I don't have a chance to see what it says.  I
>                     looked at the log
>                     file, but couldn't find anywhere that it
>         specifically says
>                     it compiled
>                     bibtex.  The following is the only relevant
>         information I
>                     could find...
>
>                         ]
>                         No file *.bbl.
>                         [14
>
>
>                     where * is the actual base filename.
>
>                     I just recently downloaded Vim-Latex in the last
>         week or so,
>                     so it would
>                     be strange if it was out-dated.  I found the
>         following in
>                     compiler.vim
>                     that I believe you were referring to.
>
>         " The first time we see if we need to run bibtex and if the
>                     .bbl file
>
>         " changes, we will rerun latex.
>                     if runCount == 0 && Tex_IsPresentInFile('\\bibdata',
>                     mainFileName_root.'.aux')
>                     let bibFileName = mainFileName_root.'.bbl'
>
>                     let biblinesBefore = Tex_CatFile(bibFileName)
>
>                     echomsg "Running
>         '".Tex_GetVarValue('Tex_BibtexFlavor')."' ..."
>                     let temp_mp = &mp | let &mp =
>                     Tex_GetVarValue('Tex_BibtexFlavor')
>                     exec 'silent! make '.mainFileName_root
>                     let &mp = temp_mp
>
>                     let biblinesAfter = Tex_CatFile(bibFileName)
>
>         " If the .bbl file changed after running bibtex, we need to
>         " latex again.
>                     if biblinesAfter != biblinesBefore
>                     echomsg 'Need to rerun because bibliography file
>         changed...'
>                     call Tex_Debug('Tex_CompileMultipleTimes: Need to
>         rerun because
>                     bibliography file changed...', 'comp')
>                     let needToRerun = 1
>                     endif
>                     endif
>
>                     Does anything seem to be wrong?
>
>                     Once again, thank you so much for taking the time to
>         help me!!
>
>
>                     On Thu, Jul 1, 2010 at 2:36 PM, Ted Pavlic
>         <te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>> wrote:
>
>                         Hm. All of that works for me. \ll runs LaTeX
>         three times
>                     with
>                         relevant runs of bibtex in between to build the BBL.
>
>                         Could you send a complete minimal non-working
>         example?
>                     Something
>                         that can be immediately opened in Vim (perhaps
>         even with
>                     a minimal
>                         bib, but I don't think the bib will matter; I
>         can sub my
>                     own bib in)
>                         that causes you problems when you \ll it.
>
>                         After you run \ll, what does the status line in
>         Vim say? For
>                         example, mine says "Run latex 3 time(s)" right now.
>                     Also, while \ll
>                         is running, can you catch a glimpse of some of
>         the other
>                     status
>                         messages? It should report if/when it tries to
>         run bibtex.
>
>                         Also, if you look where Vim-LaTeX is installed
>         (e.g., in
>                     your
>                         .vim/ftplugin/latex-suite/ or in
>                         /usr/share/vim/vimfiles/ftplugin/latex-suite/ or
>         similar
>                     on your
>                         system), you should find a "compiler.vim" that
>         has the
>                     Vim script
>                         that implements \ll. Is it possible that you
>         have a very
>                     very old
>                         version of Vim-LaTeX that doesn't yet run
>         bibtex? Search
>                     through
>                         that file for "bibdata" -- you should find the
>         relevant
>                     section of
>                         code that checks the AUX file for bibdata and runs
>                     bibtex as needed.
>                         You will also notice it references configuration
>                     variables that can
>                         be changed by the user. It's possible that your
>         defaults
>                     are either
>                         set wrong or have been changed (?).
>
>                         --Ted
>
>
>                         On 07/01/2010 01:24 PM, Abbie Kressner wrote:
>
>                             As far as I can tell, there are no errors.  I
>                     deleted all the files
>                             except the tex file and reran the \ll compile
>                     command.  The aux file
>                             contains the following lines.
>
>                                 \bibstyle{IEEEtran}
>
>           \bibdata{/Users/abbiekre/Documents/_Papers/_Papers}
>
>
>                             Also, here are the relevant lines in my
>         beamer tex file.
>
>                                 \appendix
>                                 \begin{frame}[allowframebreaks]
>
>                                     \textbf{References}
>
>                                     \bibliographystyle{IEEEtran}
>
>                                 \bibliography{_Papers}
>                                 \end{frame}
>
>
>                             Do you see any blaring errors?  Any other
>         ideas if not?
>
>                             Thanks!
>
>                             // Abbie
>
>                             Thanks in advance for anymore help!
>           Hopefully I'll
>                     find a solution
>                             eventually.
>
>                             On Thu, Jul 1, 2010 at 12:38 PM, Ted Pavlic
>         <te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>>> wrote:
>
>                                 Abbie --
>
>                                 Are you sure your LaTeX run isn't
>         causing an error?
>                             Vim-LaTeX will
>                                 cease processing on an error. There may be a
>                     subtle LaTeX error
>                                 causing the Vim-LaTeX compiler to halt early
>                     (although that
>                             usually
>                                 would cause Vim-LaTeX to report an error).
>
>                                 After LaTeX is run (by Vim-LaTeX), an
>         "AUX" file
>                     should be
>                             created.
>                                 That "AUX" file should have a line in it
>         that
>                     has "\bibdata"
>                             in it.
>                                 It is that line that causes Vim-LaTeX to
>         call
>                     bibtex.
>
>                                 Are there other details that might be
>         confusing
>                     Vim-LaTeX?
>                             (e.g.,
>                                 spaces in file names, etc.?)
>
>                                 --Ted
>
>
>                                 On 07/01/2010 12:33 PM, Abbie Kressner
>         wrote:
>
>                                     Thank you, Ted!
>
>                                     I still haven't been able to get the \ll
>                     compiler command to
>                                     successful
>                                     compile a .bbl file.  Any help would be
>                     greatly appreciated!
>
>                                     My current workaround is to call bibtex
>                     manually from
>                             Terminal.
>                                       Then
>                                     when I compile with \ll in MATLAB,
>         the citations
>                             correctly turn
>                                     from "?"
>                                     to numbers, and my reference page
>         displays
>                     correctly (rather
>                                     than being
>                                     blank).  Removing the extra steps
>         involved
>                     in compiling
>                             would be
>                                     fantastic though!
>
>                                     On Thu, Jul 1, 2010 at 12:14 PM, Ted
>         Pavlic
>         <te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>>>> wrote:
>
>                                         Abbie --
>
>
>                                         On 06/30/2010 04:46 PM, Abbie
>         Kressner
>                     wrote:
>
>                                             Do you happen to know what
>         to do if
>                     \ll does not
>                             call
>                                     bibtex?
>
>
>                                                 I'm responding to this
>         message
>                     via the
>                                     vim-latex-devel list.
>                                         I've BCC'd you, but I advise you to
>                     continue this
>                             thread on
>                                     the list
>                                         where others can help too.
>
>                                                 So long as your LaTeX
>         file has a
>                     \bibliography{}
>                                     line in it,
>                                         the \ll compiler command will issue
>                     bibtex sa needed. If
>                                     your LaTeX
>                                         file only has a \bibliography style
>                     command but no
>                             \bibliography
>                                         command, then Vim-LaTeX won't
>         know to
>                     run bibtex. In
>                             fact,
>                                     in these
>                                         cases where there is no
>         \bibliography
>                     command, if
>                             you try to run
>                                         bibtex manually it will give you
>         an error.
>
>                                                 Of course, there is more
>         than
>                     one way to
>                             skin a cat.
>                                         However, I'm confident that if your
>                     LaTeX document is
>                                     properly setup
>                                         for including a BibTeX bibliogrpahy,
>                     then Vim-LaTeX will
>                                     make the
>                                         appropriate calls for you (using
>         \ll).
>
>
>                                                 Best --
>                                                 Ted
>
>                                         --
>                                         Ted Pavlic <te...@te...
>         <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>>>>
>
>
>
>                                           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.
>
>
>
>                                 --
>                                 Ted Pavlic <te...@te...
>         <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>>>
>
>                                   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.
>
>
>
>                         --
>                         Ted Pavlic <te...@te...
>         <mailto:te...@te...> <mailto:te...@te...
>         <mailto:te...@te...>>
>         <mailto:te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>>
>
>                           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.
>
>
>
>                 --
>                 Ted Pavlic <te...@te... <mailto:te...@te...>
>         <mailto:te...@te... <mailto:te...@te...>>>
>
>                   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.
>
>
>
>
>     --
>     Ted Pavlic <te...@te... <mailto:te...@te...>>
>
>       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.
>
>

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

   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.