Thread: Re: [Vim-latex-devel] [Question] Bibtex compiling
Brought to you by:
srinathava,
tmaas
Menu
▾
▴
vim-latex-devel
|
From: Ted P. <te...@te...> - 2010-07-01 16:14:23
|
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...>
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.
|
|
From: Ted P. <te...@te...> - 2010-07-01 16:38:20
|
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...>> 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...>>
>
> 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.
|
|
From: Ted P. <te...@te...> - 2010-07-01 18:36:27
|
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...>> 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...>>> 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...>>>
>
>
> 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.
|
|
From: Ted P. <te...@te...> - 2010-07-01 19:56:46
|
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...>> 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...>>> 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...>>>> 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...>>>>
>
>
>
> 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.
|
|
From: Ted P. <te...@te...> - 2010-07-01 20:24:40
|
Abbie --
I don't think that will cause a problem. That likely means that your
PATH environment variable includes "/usr/texbin/" instead of
"/usr/texbin". You can type:
echo $PATH
at a shell prompt to verify. In fact, typing:
:!echo $PATH
in vim will tell you what Vim sees as its path. Check to see if
"/usr/texbin" is followed by a slash. If it is, find where it's being
set. It could be set in a global profile (e.g., /etc/profile or
/etc/bash_profile or /etc/bashrc) or in a user profile (e.g.,
/etc/.bash_profile or /etc/.bashrc) or in a script included from one of
those. I don't recall how TeXLive for the Mac organizes itself.
I do recommend you try going to MacVim->Preferences and look for a
setting to "Run in login shell" or something like that. I don't recall
the actual wording (the vim-mac mailing list would be a good place to
check), but there is a setting in MacVim preferences that forces all
shells to be run as login shells to ensure that the same PATH that gets
set when you login is used within Vim.
One more thing to try.. execute
:!bibtex
inside vim. In fact, you can execute
:!bibtex %:r
inside vim to run bibtex on the TeX file you're working on at the time
(and you can make a macro that runs that for you). Either way, does
bibtex return an error from the shell about not being found, or does it run?
--Ted
On 07/01/2010 04:01 PM, Abbie Kressner 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...>> 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...>>> 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...>>>> 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...>>>>> 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...>>>>>
>
>
>
> 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.
|
|
From: Ted P. <te...@te...> - 2010-07-01 20:33:45
|
> 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...>> 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...>> 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...>>> 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...>>>> 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...>>>>> 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...>>>>> > > > > 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. |
|
From: Ted P. <te...@te...> - 2010-07-02 16:06:30
|
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.
|
|
From: Gianluca M. <gia...@gm...> - 2010-07-02 16:26:39
|
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"
|
|
From: Ted P. <te...@te...> - 2010-07-02 16:34:18
|
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.
|
|
From: Gianluca M. <gia...@gm...> - 2010-07-03 11:26:30
|
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 |
|
From: Ted P. <te...@te...> - 2010-07-05 15:49:16
|
> 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...>
|
|
From: Gianluca M. <gia...@gm...> - 2010-07-06 07:03:21
|
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"
|
|
From: Ted P. <te...@te...> - 2010-07-06 14:29:40
|
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.
|
|
From: Alfredo C. <alf...@gm...> - 2015-02-10 17:11:03
|
This is awesome! You fixed the Bibtex bug on Mac! Can we please push this to the main documentation and/or release? Actually, if someone has a Mac, the following lines must be put in your ~/.vimrc let g:Tex_TreatMacViewerAsUNIX = 1 let g:Tex_ExecuteUNIXViewerInForeground = 1 let g:Tex_ViewRule_pdf = 'open -a Preview' let g:Tex_MultipleCompileFormats = 'pdf' Regards, Alfredo > 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 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X