Latex-Box won't compile LaTeX on OS X Yosemite

Question

Latex-Box won't compile LaTeX on OS X Yosemite

Closed this issue 10 years ago · 24 comments

Hi,

Today I tried to compile a LaTeX document on OS X Yosemite Developer Release 7 for the first time. I ran into some issues...
After triggering compilation usually my PDF viewer pops up. This time it did not. However, LaTeX-Box did not report any problems. Looking at the error log (local leader + le) it did not show any errors either.
I deleted all LaTeX garbage from the folder and tried again. Nothing would happen. Manually triggering the error window gave me this:

I can compile my document using latexmk from terminal just fine. Texshop also works. Is this something you could look into?

Thanks!

Answer 1 · 2014-09-07T08:21:04.000Z

Interesting. I have the same problem in Windows.

Answer 2 · 2014-09-07T16:38:53.000Z

Hi. I'm just curious: Could you test if the same problem occurs with vim-latex? If it is reproducible there, then it is easier for me to debug due to a couple of minor debug helpers available with vim-latex.

It is obvious that the problem here is with starting latexmk. It would be easier to help if you could provide some more info, preferably a minimal working example:

A minimal tex file that does not compile.
A minimal vimrcfile. See here for an example.

Answer 3 · 2014-09-08T09:54:56.000Z

Hm this might be a problem due to my build of Macvim. I can get stuff to work with vim-latex in terminal. Will see...

Answer 4 · 2014-09-08T12:03:28.000Z

Things also work with latex-box in the terminal. So forget about it ;)

Answer 5 · 2014-09-09T20:08:01.000Z

So, if I understand correctly, the issue is only with Macvim, and not with terminal vim? Do you have the same issue with Macvim with vim-latex?

Answer 6 · 2014-09-10T08:56:30.000Z

With Macvim both vim plugins fail, correct. Terminal, both are fine.

Answer 7 · 2014-09-10T08:58:07.000Z

Could you give me the outputs of <leader>li and <leader>lo after you've tried compiling from Macvim with vim-latex? As a reference, it could help to also know the same output from terminal vim.

Answer 8 · 2014-09-10T09:12:35.000Z

Hm, actually I think you should not pursue this further at this point. I am using a Macvim version build through a modified homebrew formular on a beta operating system. I had to modify the formular, since Macvim won't build otherwise. This is all really shaky and not the right grounds for debugging.

Answer 9 · 2014-09-10T09:15:36.000Z

Ok. I'll close this then. Feel free to reopen og open a new issue if you change your mind.

Answer 10 · 2014-09-22T16:46:46.000Z

@feju Hi, sorry for disturbing. I am interested in your programming used font in your screenshot, it that Consolas? If so, why your Consolas so slim. See mine as below,

What's more, are't you using the air-line in your vim and what is your color theme of your air-line?

Thanks so much for you time and I am really liking your vim-looking.

Answer 11 · 2014-09-22T17:45:45.000Z

@feju with defaults write com.apple.Terminal AppleFontSmoothing -int 0 I finally fix the problem~ XD

But I am still interested in your air-line theme~

Answer 12 · 2014-09-23T08:28:17.000Z

@udonmai I'm using "Meslo LG M Regular for Powerline" and yes, I have tinkered with FontSmoothing. My iTerm and Vim theme is Base16 Monokai dark. Your Airline will use it if you set the appropriate setting to base16 in your vimrc.

Answer 13 · 2014-09-23T09:10:39.000Z

@feju Thanks much! !

I'll try later for both the font and the color theme~

Answer 14 · 2014-10-18T03:38:35.000Z

I'm running the release of OS X Yosemite as well as MacVim (vim version 7.4.383). I experience a similar issue where MacVim+LatexBox won't compile.

I run /usr/bin/vim, mvim -v, mvim -f and see successful compiles. However, my typical use case doesn't involve any of these; I typically open a TeX file from Alfred (/Spotlight). In this use case, I don't see successful compiles.

This issue seems like it should be opened again, but I should leave that to @lervag

Answer 15 · 2014-10-18T08:29:43.000Z

@scottsievert Hi, I guess your problem occurred likely because of the PDF preview application you are using and what is it? For Mac OS X 's native previewer, it can not automatically update the PDF files when recompiling any tex files while Skim can.

Answer 16 · 2014-10-19T04:19:16.000Z

I should have guessed... my file was in Dropbox, which plays with the filesystem and breaks this MacVim/Spotlight/latexmk combo. This wasn't an issue in Mavericks but is in Yosemite. Outside of Dropbox, I see successful compiles.

Answer 17 · 2014-10-19T05:53:22.000Z

Anyway, nice to you~

Answer 18 · 2014-11-25T03:27:30.000Z

This issue persists and was not resolved with my first impression fix. I can successfully compile while opening MacVim by double clicking, running mvim -f, mvim -v or /usr/bin/vim for my simple test .tex file. However, it is most convenient to edit this after opening from Spotlight.

To work around this issue I am going to open with using the mvim command or opening with :e filename. The last option seems more unreliable as it failed for my more complex tests (a document using \include{}).

Answer 19 · 2014-11-28T09:06:40.000Z

I have found that LaTeX-Box has no issues compiling and opening the resulting PDF in Skim when I use Vim in the Terminal rather than MacVim. I don't get any errors from MacVim, but there does not seem to be any compilation output. I have no idea why this is the case. Personally, I don't mind using Vim directly (I do so for programming anyway). But I feel this is a bit annoying...

Best,

Felix

Answer 20 · 2014-11-29T01:42:13.000Z

Ditto on the annoyance. I've made an Automator application to run mvim on the input file. This gist details how to make this automator application.

Answer 21 · 2014-11-29T16:58:58.000Z

@feju (and perhaps others) At least on linux there is a difference in the environment variables when you run vim from a terminal than a gvim session. I suspect there might be a similar difference on OS X with mvim and terminal vim. To check this, you could either do something like echo $PATH (or other variables) from mvim and vim and check if they are the same. You could also do :!env from vim and mvim to see the entire list of environment variables.

Answer 22 · 2015-08-28T13:24:08.000Z

I'm running OS X 10.10.4 using vim in Terminal and get the same error with the current master and latest vim (7.4.826) and latex-mk version 2.1. Compiling using the terminal is fine, just latex-box is producing this error. Has someone solved this issue?

Compiling to pdf ... (async off!) Error detected while processing function LatexBox_Latexmk..LatexBox_LatexErrors: line 16: E40: Can't open errorfile /Users/johannesdarms/####/####.log Error detected while processing function LatexBox_Latexmk: line 210: E171: Missing :endif

Answer 23 · 2015-08-29T20:55:30.000Z

I'm running Vim 7.4 with patch 769 via brew install macvim, latexmk version 4.39 and the most recent version of LaTeX-Box installed with vim-plug. I can compile just fine from GUI and terminal vim.

(Also running OSX 10.10.4).

Answer 24 · 2015-09-03T08:33:18.000Z

@scottsievert : Thanks for your feedback.
I updated to a newer version of latexmk ( with tlgmr) which solved the problem. The version I used previously is the one from sf, thought that would be the project site...