Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LaTeXTools on OS X 10.10 #401

Closed
leandersabel opened this issue Jun 4, 2014 · 41 comments
Closed

LaTeXTools on OS X 10.10 #401

leandersabel opened this issue Jun 4, 2014 · 41 comments

Comments

@leandersabel
Copy link

@leandersabel leandersabel commented Jun 4, 2014

Hey there,

I just upgraded to OS X 10.10 and building LaTeX documents from Sublime Text 3 stopped working. It simply stops after invoking latexmk.

[Compiling /Users/Me/Document.tex]
TraditionalBuilder: Invoking latexmk... done.

Are there any more logs that might show why this is happening?

Running latexmk on a simple .tex file from the command line still works.
and building from Sublime also worked fine yesterday before the upgrade to 10.10


Latexmk, John Collins, 10 Nov 2013. Version 4.39
pdfTeX 3.14159265-2.6-1.40.15 (TeX Live 2014)
OS X 10.10
Sublime Text Build 3059
@msiniscalchi
Copy link
Collaborator

@msiniscalchi msiniscalchi commented Jun 5, 2014

Lucky you... I have no access to 10.10... Anyway, what do you see in the
ST3 console (Ctrl+backtick)?

On Wed, Jun 4, 2014 at 12:29 PM, Leander Sabel notifications@github.com
wrote:

Hey there,

I just upgraded to OS X 10.10 and building LaTeX documents from Sublime
Text 3 stopped working. It simply stops after invoking latexmk.

[Compiling /Users/Me/Document.tex]
TraditionalBuilder: Invoking latexmk... done.

Are there any more logs that might show why this is happening?

Running latexmk on a simple .tex file from the command line still works.
and building from Sublime also worked fine yesterday before the upgrade to

10.10

Latexmk, John Collins, 10 Nov 2013. Version 4.39
pdfTeX 3.14159265-2.6-1.40.15 (TeX Live 2014)
OS X 10.10
Sublime Text Build 3059


Reply to this email directly or view it on GitHub
#401.

Marciano Siniscalchi
Economics Department, Northwestern University
http://faculty.wcas.northwestern.edu/~msi661

@leandersabel
Copy link
Author

@leandersabel leandersabel commented Jun 6, 2014

Ok thats what I was looking for. I was not aware those are different consoles.

ST3 Console

Exception in thread Thread-6:
Traceback (most recent call last):
  File "X/threading.py", line 639, in _bootstrap_inner
  File "/Users/Leander/Library/Application Support/Sublime Text 3/Packages/LaTeXTools/makePDF.py", line 147, in run
    data = open(self.caller.tex_base + ".log", 'rb').read()
FileNotFoundError: [Errno 2] No such file or directory: '/Users/Leander/Freiburg/Master-Thesis/Thesis/Thesis.log'

So I went ahead and manually created the Thesis.log file.
Here are my permissions by the way

Folder drwxr-xr-x 
aux files -rw-r--r--
tex files -rwxr-xr-x@

After creating the log file and building again I get:

<module 'traditionalBuilder' from '/Users/Leander/Library/Application Support/Sublime Text 3/Packages/LaTeXTools/builders/traditionalBuilder.py'>
<class 'traditionalBuilder.TraditionalBuilder'>
3
Welcome to thread Thread-4
['latexmk', '-cd', '-e', "$pdflatex = 'pdflatex -interaction=nonstopmode -synctex=1 %S %O'", '-f', '-pdf', 'Thesis.tex']
Finished normally
12
False True True
!TEX root =  '/Users/Leander/Freiburg/Master-Thesis/Thesis/Thesis.tex'
Jump to:  9 0

And in the LaTeXTools Console

[Compiling /Users/Leander/Freiburg/Master-Thesis/Thesis/Thesis.tex]
TraditionalBuilder: Invoking latexmk... done.
No errors.
[Done!]

Thesis.log is empty and Thesis.fdb_latexmk says

# Fdb version 3
["pdflatex"] 1402050257 "Thesis.tex" "Thesis.pdf" "Thesis" 1402050257
 "Thesis.aux" 1401990796 8 a94a2480d3289e625eea47cd1b285758 ""
  "Thesis.tex" 1401990693 4728 4001963e42fc9f8e5086a3b74e6b1aaf ""
  (generated)
  "Thesis.pdf"
  "Thesis.log"

Unfortunately there is no Thesis.pdf. Judging from the inability to create the Thesis.log file I am assuming ST is unable to create the pdf file?!

Update: I just tried a chmod -R 777 . on the project folder but that did not change anything.

@landaire
Copy link

@landaire landaire commented Jun 7, 2014

I'm having this issue as well.

Here's my log before manually running latexmk:

['latexmk', '-cd', '-e', "$pdflatex = 'pdflatex -interaction=nonstopmode -synctex=1 %S %O'", '-f', '-pdf', 'Final Exam Notes.tex']
Finished normally
12
Exception in thread Thread-28:
Traceback (most recent call last):
  File "X/threading.py", line 639, in _bootstrap_inner
  File "/Users/lander/Library/Application Support/Sublime Text 3/Packages/LaTeXTools/makePDF.py", line 147, in run
    data = open(self.caller.tex_base + ".log", 'rb').read()
FileNotFoundError: [Errno 2] No such file or directory: '/Users/lander/Documents/Math/Final Exam Notes/Final Exam Notes.log'

And after:

<module 'traditionalBuilder' from '/Users/lander/Library/Application Support/Sublime Text 3/Packages/LaTeXTools/builders/traditionalBuilder.py'>
<class 'traditionalBuilder.TraditionalBuilder'>
7
Welcome to thread Thread-26
['latexmk', '-cd', '-e', "$pdflatex = 'pdflatex -interaction=nonstopmode -synctex=1 %S %O'", '-f', '-pdf', 'Final Exam Notes.tex']
Finished normally
0
False True True
!TEX root =  '/Users/lander/Documents/Math/Final Exam Notes/Final Exam Notes.tex'
Jump to:  22 4
Traceback (most recent call last):
  File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 543, in run_
    return self.run(edit, **args)
  File "/Users/lander/Library/Application Support/Sublime Text 3/Packages/LaTeXTools/jumpToPDF.py", line 66, in run
    options + [str(line), pdffile, srcfile])
  File "X/subprocess.py", line 818, in __init__
  File "X/subprocess.py", line 1416, in _execute_child
FileNotFoundError: [Errno 2] No such file or directory: '/Applications/Skim.app/Contents/SharedSupport/displayline'

The Skim exception should be ignored because I actually don't have Skim downloaded.

@leandersabel
Copy link
Author

@leandersabel leandersabel commented Jun 10, 2014

Another thing that is not related to LaTeXtools but for people reading this issue:
Skim is broken on 10.10 and will crash on launch when you try to open a document. Upgrading to Version 1.4.8r8359 (82) fixes that issue. http://sourceforge.net/projects/skim-app/

@leandersabel
Copy link
Author

@leandersabel leandersabel commented Jun 21, 2014

To test whether this is a SublimeText issue with creating new files I created short ruby script that creates a new file on the hard drive and ran it with cmd+b. That works as expected so I guess there is something going on with LaTeXtools. :(

Is there any way I can help with this?
Right now I a working around it by calling latexmk from the command line to build the pdf but I would hope to get my regular workflow back as soon as possible.

@flipphillips
Copy link

@flipphillips flipphillips commented Jul 20, 2014

I too am having the same.
I did some monkeying around with paths, etc (since I can successfully get latexmk to compile the file via command line) and I have a sneaking suspicion that there is some symbolic-link-following annoyance in 10.10. For example, if I tell the TeXLive Updater path to use the /usr/texbin path, I get all sorts of trouble, mainly programs not found. But- if I hard-path it to /usr/local/texlive/2014/bin/x86_64-darwin/ instead, it will work (mostly... at least it can find the files. )

I'm happy to help in any way possible too-

@msiniscalchi
Copy link
Collaborator

@msiniscalchi msiniscalchi commented Jul 20, 2014

What LaTeXTools does with respect to building is not very sophisticated:
the traditional builder just calls latexmk using standard python calls.

Try using the "simple" builder, which does not use latexmk but just calls
pdflatex and bibtex. I would be surprised if that made a difference, but
who knows?

One possibility is that the version of python that is embedded in ST3 does
not play nice with 10.10. I am not sure what might be done in this case.

On Sun, Jul 20, 2014 at 5:18 PM, flipphillips notifications@github.com
wrote:

I too am having the same.
I did some monkeying around with paths, etc (since I can successfully get
latexmk to compile the file via command line) and I have a sneaking
suspicion that there is some symbolic-link-following annoyance in 10.10.
For example, if I tell the TeXLive Updater path to use the /usr/texbin
path, I get all sorts of trouble, mainly programs not found. But- if I
hard-path it to /usr/local/texlive/2014/bin/x86_64-darwin/ instead, it will
work (mostly... at least it can find the files. )

I'm happy to help in any way possible too-


Reply to this email directly or view it on GitHub
#401 (comment)
.

Marciano Siniscalchi
Economics Department, Northwestern University
http://faculty.wcas.northwestern.edu/~msi661

@flipphillips
Copy link

@flipphillips flipphillips commented Jul 20, 2014

That's an interesting hypothesis re: the Sublime internal-python.
I will experiment with the 'simple' builder.

I've gotten a -little- closer to things actually doing -something- but now it appears that xelatex isn't being used at all, since mathspec doesn't think its in xelatex land... baby steps :)

[Compiling /Users/flip/Dropbox/Magic/drop.tex]

TraditionalBuilder: Engine: pdflatex -> xelatex. Invoking latexmk... done.

Errors:

/usr/local/texlive/2014/texmf-dist/tex/xelatex/mathspec/mathspec.sty:12: [\RequireXeTeX]
/usr/local/texlive/2014/texmf-dist/tex/xelatex/mathspec/mathspec.sty:18: Undefined control sequence. [ {\relax}]
/usr/local/texlive/2014/texmf-dist/tex/xelatex/mathspec/mathspec.sty:18: Undefined control sequence. [ {\relax}]
/usr/local/texlive/2014/texmf-dist/tex/xelatex/mathspec/mathspec.sty:18: You can't use `the character .' after \the. [ {\relax}]
/usr/local/texlive/2014/texmf-dist/tex/xelatex/mathspec/mathspec.sty:18: Package mathspec Error: mathspec requires a more recent version of XeTeX. [ {\relax}]
/usr/local/texlive/2014/texmf-dist/tex/latex/fontspec/fontspec.sty:43: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [ }]

[Done!]

@flipphillips
Copy link

@flipphillips flipphillips commented Jul 20, 2014

OK- I wonder if the traditional builder needs a little tweaking, since it's invoking latexmk via:

['latexmk', '-cd', '-e', "$pdflatex = 'xelatex -interaction=nonstopmode -synctex=1 %S %O'", '-f', '-pdf', 'drop.tex']

and, as far as running it from the command line, I use the latexmk -xelatex form.

Furthermore, there still seems to be other pathology, in that, even when running this way, I see:

Running 'xelatex -interaction=nonstopmode -synctex=1 "drop.tex"  -recorder '
------------
Latexmk: applying rule 'pdflatex'...
sh: xelatex: command not found
Failure to make 'drop.pdf'

so it's complaining about not being able to even find xelatex...

@jiehanzheng
Copy link

@jiehanzheng jiehanzheng commented Jul 27, 2014

On OS X Yosemite too. Switching to 'simple' seems to work for me.

@kenohori
Copy link

@kenohori kenohori commented Jul 31, 2014

Switching to simple also works for me

@battlepope
Copy link

@battlepope battlepope commented Sep 2, 2014

Simple works for me.
However Skim (1.4.9 (83)) crashes after opening the newly built document. 1.4.8 does the same. Are there any news on that?

@flipphillips
Copy link

@flipphillips flipphillips commented Sep 2, 2014

There is a nasty bug in PDFKit that happens whenever you (essentially) 'seek' in a PDF. We reported it months ago and just cross our fingers each DP release. In the mean time I use Preview as my viewer.

Also, the problem that causes this particular issue is, interestingly, even more crazy. There is all sorts of trouble with the environment variables when a subprocess is created by a GUI. If you try to update TeXLive via the app you will (probably) see this. I sent the LaTeX tools author a fix for this bug that at least works now, but who knows what will happen as 10.10 matures.

On Sep 2, 2014, at 9:18 AM, battlepope <notifications@github.commailto:notifications@github.com> wrote:

Simple works for me.
However Skim (1.4.9 (83)) crashed after opening the newly built document. 1.4.8 does the same. Are there any news on that?

Reply to this email directly or view it on GitHubhttps://github.com//issues/401#issuecomment-54149284.

@forgo
Copy link

@forgo forgo commented Oct 8, 2014

Seeing this same issue using the GM version of Yosemite. Both Sublime Text 2 and Sublime Text 3 Beta have this issue. Any updates since a month ago on this? Using the "simple" option allowed me to generate a PDF, but the formatting was wrong, and subsequent builds do not pick up any of my changes to the .tex file.

@flipphillips
Copy link

@flipphillips flipphillips commented Oct 8, 2014

The author of LaTeXing made the fix I suggested months ago and it has been working fine.
The author of LaTeXTools hasn’t made the fix. I sent it to him a while back but never heard from him. But, if you really need it I can tell you what to fix.

On Oct 8, 2014, at 4:42 PM, forgo <notifications@github.commailto:notifications@github.com> wrote:

Seeing this same issue using the GM version of Yosemite. Both Sublime Text 2 and Sublime Text 3 Beta have this issue. Any updates since a month ago on this? Using the "simple" option allowed me to generate a PDF, but the formatting was wrong, and subsequent builds do not pick up any of my changes to the .tex file.


Reply to this email directly or view it on GitHubhttps://github.com//issues/401#issuecomment-58424226.

-fp

www.skidmore.edu/~fliphttp://www.skidmore.edu/~flip

@msiniscalchi
Copy link
Collaborator

@msiniscalchi msiniscalchi commented Oct 8, 2014

Guys, I'll look for the fix---was it in a pull request? I'm hopelessly
behind :(

On Wed, Oct 8, 2014 at 4:23 PM, flipphillips notifications@github.com
wrote:

The author of LaTeXing made the fix I suggested months ago and it has been
working fine.
The author of LaTeXTools hasn’t made the fix. I sent it to him a while
back but never heard from him. But, if you really need it I can tell you
what to fix.

On Oct 8, 2014, at 4:42 PM, forgo <notifications@github.com<mailto:
notifications@github.com>> wrote:

Seeing this same issue using the GM version of Yosemite. Both Sublime Text
2 and Sublime Text 3 Beta have this issue. Any updates since a month ago on
this? Using the "simple" option allowed me to generate a PDF, but the
formatting was wrong, and subsequent builds do not pick up any of my
changes to the .tex file.


Reply to this email directly or view it on GitHub<
https://github.com/SublimeText/LaTeXTools/issues/401#issuecomment-58424226>.

-fp

www.skidmore.edu/~fliphttp://www.skidmore.edu/~flip


Reply to this email directly or view it on GitHub
#401 (comment)
.

Marciano Siniscalchi
Economics Department, Northwestern University
http://faculty.wcas.northwestern.edu/~msi661

@hijoe320
Copy link

@hijoe320 hijoe320 commented Oct 14, 2014

start Sublime Text 3 by using sudo
sudo subl

then problem solved!

@msiniscalchi
Copy link
Collaborator

@msiniscalchi msiniscalchi commented Oct 14, 2014

Ha! So it's a permission issue. That's bad news. Running ST3, and every
single process launched by it
as root is a security risk. Maybe there's
some limitation in Yosemite on which processes can launch shell scripts?
Again, I don't have Yosemite (I applied for the beta, but never got it), so
I can't test directly until they release it.

Time to switch to Windows...

On Tue, Oct 14, 2014 at 9:45 AM, Haizhou Qu notifications@github.com
wrote:

start Sublime Text 3 by using sudo
sudo subl

then problem solved!


Reply to this email directly or view it on GitHub
#401 (comment)
.

Marciano Siniscalchi
Economics Department, Northwestern University
http://faculty.wcas.northwestern.edu/~msi661

@flipphillips
Copy link

@flipphillips flipphillips commented Oct 14, 2014

Actually- I think I sent a later email- you have to pass a better PATH to the os. subprocess launcher.

The default PATH in 10.10 is not the user path (in fact, to be fully correct, there are —duplicate— PATHs in the environment)

To see for yourself, run TeX Live Updater and look at the diagnostics re: path. It fails too because of this.

On Oct 14, 2014, at 10:49 AM, msiniscalchi <notifications@github.commailto:notifications@github.com> wrote:

Ha! So it's a permission issue. That's bad news. Running ST3, and every
single process launched by it
as root is a security risk. Maybe there's
some limitation in Yosemite on which processes can launch shell scripts?
Again, I don't have Yosemite (I applied for the beta, but never got it), so
I can't test directly until they release it.

Time to switch to Windows...

On Tue, Oct 14, 2014 at 9:45 AM, Haizhou Qu <notifications@github.commailto:notifications@github.com>
wrote:

start Sublime Text 3 by using sudo
sudo subl

then problem solved!


Reply to this email directly or view it on GitHub
#401 (comment)
.

Marciano Siniscalchi
Economics Department, Northwestern University
http://faculty.wcas.northwestern.edu/~msi661


Reply to this email directly or view it on GitHubhttps://github.com//issues/401#issuecomment-59057611.

-fp

www.skidmore.edu/~fliphttp://www.skidmore.edu/~flip

@msiniscalchi
Copy link
Collaborator

@msiniscalchi msiniscalchi commented Oct 14, 2014

I need to dig out your email then. So it's back to the bad old days of
environment.plist :)

Actually, now that the config file is more flexible and user-editable, it
would probably be enough to specify the right path---using the "texpath"
option (under "Platform Settings")

M

On Tue, Oct 14, 2014 at 9:53 AM, flipphillips notifications@github.com
wrote:

Actually- I think I sent a later email- you have to pass a better PATH to
the os. subprocess launcher.

The default PATH in 10.10 is not the user path (in fact, to be fully
correct, there are —duplicate— PATHs in the environment)

To see for yourself, run TeX Live Updater and look at the diagnostics re:
path. It fails too because of this.

On Oct 14, 2014, at 10:49 AM, msiniscalchi <notifications@github.com
mailto:notifications@github.com> wrote:

Ha! So it's a permission issue. That's bad news. Running ST3, and every
single process launched by it
as root is a security risk. Maybe there's
some limitation in Yosemite on which processes can launch shell scripts?
Again, I don't have Yosemite (I applied for the beta, but never got it),
so
I can't test directly until they release it.

Time to switch to Windows...

On Tue, Oct 14, 2014 at 9:45 AM, Haizhou Qu <notifications@github.com
mailto:notifications@github.com>
wrote:

start Sublime Text 3 by using sudo
sudo subl

then problem solved!


Reply to this email directly or view it on GitHub
<
https://github.com/SublimeText/LaTeXTools/issues/401#issuecomment-59056705>

.

Marciano Siniscalchi
Economics Department, Northwestern University
http://faculty.wcas.northwestern.edu/~msi661


Reply to this email directly or view it on GitHub<
https://github.com/SublimeText/LaTeXTools/issues/401#issuecomment-59057611>.

-fp

www.skidmore.edu/~fliphttp://www.skidmore.edu/~flip


Reply to this email directly or view it on GitHub
#401 (comment)
.

Marciano Siniscalchi
Economics Department, Northwestern University
http://faculty.wcas.northwestern.edu/~msi661

@flipphillips
Copy link

@flipphillips flipphillips commented Oct 14, 2014

proc = subprocess.Popen(cmd, stderr=subprocess.STDOUT, stdout=subprocess.PIPE,
env=os.environ)

That’s all I had to do, add env=os.environ…

On Oct 14, 2014, at 11:58 AM, Haizhou Qu <notifications@github.commailto:notifications@github.com> wrote:

I need to dig out your email then. So it's back to the bad old days of
environment.plist :)

Actually, now that the config file is more flexible and user-editable, it
would probably be enough to specify the right path---using the "texpath"
option (under "Platform Settings")

M

On Tue, Oct 14, 2014 at 9:53 AM, flipphillips <notifications@github.commailto:notifications@github.com>
wrote:

Actually- I think I sent a later email- you have to pass a better PATH to
the os. subprocess launcher.

The default PATH in 10.10 is not the user path (in fact, to be fully
correct, there are —duplicate— PATHs in the environment)

To see for yourself, run TeX Live Updater and look at the diagnostics re:
path. It fails too because of this.

On Oct 14, 2014, at 10:49 AM, msiniscalchi <notifications@github.commailto:notifications@github.com
mailto:notifications@github.com> wrote:

Ha! So it's a permission issue. That's bad news. Running ST3, and every
single process launched by it
as root is a security risk. Maybe there's
some limitation in Yosemite on which processes can launch shell scripts?
Again, I don't have Yosemite (I applied for the beta, but never got it),
so
I can't test directly until they release it.

Time to switch to Windows...

On Tue, Oct 14, 2014 at 9:45 AM, Haizhou Qu <notifications@github.commailto:notifications@github.com
mailto:notifications@github.com>
wrote:

start Sublime Text 3 by using sudo
sudo subl

then problem solved!


Reply to this email directly or view it on GitHub
<
https://github.com/SublimeText/LaTeXTools/issues/401#issuecomment-59056705>

.

Marciano Siniscalchi
Economics Department, Northwestern University
http://faculty.wcas.northwestern.edu/~msi661


Reply to this email directly or view it on GitHub<
https://github.com/SublimeText/LaTeXTools/issues/401#issuecomment-59057611>.

-fp

www.skidmore.edu/~fliphttp://www.skidmore.edu/~fliphttp://www.skidmore.edu/~flip


Reply to this email directly or view it on GitHub
#401 (comment)
.

Marciano Siniscalchi
Economics Department, Northwestern University
http://faculty.wcas.northwestern.edu/~msi661


Reply to this email directly or view it on GitHubhttps://github.com//issues/401#issuecomment-59069650.

-fp

www.skidmore.edu/~fliphttp://www.skidmore.edu/~flip

@patrickhoefler
Copy link

@patrickhoefler patrickhoefler commented Oct 14, 2014

Same here, adding env=os.environ in makePDF.py fixed the problem for the traditional builder using xelatex.

My setup:

OS X 10.10 Beta 6
Sublime Text 3 Build 3065
LaTeXTools 2014.03.14.03.33.13
@fhieber
Copy link

@fhieber fhieber commented Oct 17, 2014

I can confirm the solution of @patrickhoefler is working with Sublime2 + Yosemite as released yesterday.

@patrickhoefler
Copy link

@patrickhoefler patrickhoefler commented Oct 17, 2014

Glad to hear that! Just for the record: @flipphillips came up with this solution, not me :)

@flipphillips
Copy link

@flipphillips flipphillips commented Oct 17, 2014

:)

-- flipphone

On Oct 17, 2014, at 11:54 AM, Patrick Hoefler <notifications@github.commailto:notifications@github.com> wrote:

Glad to hear that! Just for the record: @flipphillipshttps://github.com/flipphillips came up with this solution, not me :)

Reply to this email directly or view it on GitHubhttps://github.com//issues/401#issuecomment-59533841.

@msiniscalchi
Copy link
Collaborator

@msiniscalchi msiniscalchi commented Oct 17, 2014

I am about to upgrade to Yosemite (wish me luck!) which will force me to
pull in this change :)

On Fri, Oct 17, 2014 at 11:26 AM, flipphillips notifications@github.com
wrote:

:)

-- flipphone

On Oct 17, 2014, at 11:54 AM, Patrick Hoefler <notifications@github.com
mailto:notifications@github.com> wrote:

Glad to hear that! Just for the record: @flipphillips<
https://github.com/flipphillips> came up with this solution, not me :)

Reply to this email directly or view it on GitHub<
https://github.com/SublimeText/LaTeXTools/issues/401#issuecomment-59533841>.


Reply to this email directly or view it on GitHub
#401 (comment)
.

Marciano Siniscalchi
Economics Department, Northwestern University
http://faculty.wcas.northwestern.edu/~msi661

@cbonsig
Copy link

@cbonsig cbonsig commented Oct 17, 2014

Same issue here on the production release of Yosemite OS X 10.10 (14A389). The env=os.environ fix worked for me. I had to hunt around a bit to find makePDF.py. On my system, here are the details:

Library / Application Support / Sublime Text 2 / Packages / LaTeXTools / makePDF.py

Line 95 changed from:
proc = subprocess.Popen(cmd, stderr=subprocess.STDOUT, stdout=subprocess.PIPE)

to:
proc = subprocess.Popen(cmd, stderr=subprocess.STDOUT, stdout=subprocess.PIPE, env=os.environ)

cbonsig added a commit to cbonsig/LaTeXTools that referenced this issue Oct 17, 2014
This fixes PDF creation, which was broken by upgrading to OSX 10.10 Yosemite. Fix from @flipphillips per SublimeText#401
@rameezk
Copy link

@rameezk rameezk commented Oct 18, 2014

Can confirm the env=os.environ fix works for Sublime Text 3 and the production version of Yosemite as well. As a side, Skim seems to be rendering the PDF document incorrectly. This is an issue with Skim, however.

@huihuazhao
Copy link

@huihuazhao huihuazhao commented Oct 18, 2014

helps for me

@amaxwell
Copy link

@amaxwell amaxwell commented Oct 19, 2014

I ended up here via a tex.stackexchange thread, and I'd like to request that everyone affected by this bug file a report with Apple; I did, back in August, but duplicates are needed. It appears that they've broken environ(7) really badly, such that it ends up with duplicate envvars and doesn't get synced up with setenv(3) or getenv(3). I have notes and a Cocoa example program here https://code.google.com/p/mactlmgr/issues/detail?id=102 if you're interested.

@msiniscalchi
Copy link
Collaborator

@msiniscalchi msiniscalchi commented Oct 19, 2014

Ok @flipphillips and @patrickhoefler (and everyone else), I just implemented the proposed fix. It works for me on both 10.10 and 10.8, ST2 and ST3. I am a bit worried about the issue raised by @amaxwell though---it seems like we may be working around a deep Yosemite bug, and when that's fixed, it may be we may have to revert back to calling Popen without env=os.environ. Anyway, if things work for now, please close. And THANKS for your patience!

@patrickhoefler
Copy link

@patrickhoefler patrickhoefler commented Oct 19, 2014

Thanks for the fix :)

@flipphillips
Copy link

@flipphillips flipphillips commented Oct 19, 2014

Yes. It is a nasty bug. I filed a radar a while back too.

-- flipphone

On Oct 19, 2014, at 1:39 AM, msiniscalchi <notifications@github.commailto:notifications@github.com> wrote:

Ok @flipphillipshttps://github.com/flipphillips and @patrickhoeflerhttps://github.com/patrickhoefler (and everyone else), I just implemented the proposed fix. It works for me on both 10.10 and 10.8, ST2 and ST3. I am a bit worried about the issue raised by @amaxwellhttps://github.com/amaxwell though---it seems like we may be working around a deep Yosemite bug, and when that's fixed, it may be we may have to revert back to calling Popen without env=os.environ. Anyway, if things work for now, please close. And THANKS for your patience!

Reply to this email directly or view it on GitHubhttps://github.com//issues/401#issuecomment-59640079.

@snario
Copy link

@snario snario commented Oct 26, 2014

Confirming that making line 80 on makePDF.py to proc = subprocess.Popen(cmd, env=os.environ) works on ST3 with LaTeXTools for SB3 for Yosemite.

@msiniscalchi
Copy link
Collaborator

@msiniscalchi msiniscalchi commented Oct 26, 2014

This was fixed last week. If you use Package Control, it should have
updated automatically. otherwise, you can pull the changes from github.

On Sun Oct 26 2014 at 3:38:54 PM Liam Horne notifications@github.com
wrote:

Confirming that making line 80 on makePDF.py to proc =
subprocess.Popen(cmd, env=os.environ) works on ST3 with LaTeXTools for
SB3.


Reply to this email directly or view it on GitHub
#401 (comment)
.

@snario
Copy link

@snario snario commented Oct 26, 2014

Got it, thanks

bcomnes added a commit to bcomnes/sublime-text-git that referenced this issue Nov 19, 2014
This adds the `env=os.environ` option to the `subprocess.Popen` call.  It provides a decent work around for the upstream PATH problems in OS X 10.10.  

Work around for kemayo#368

See SublimeText/LaTeXTools#401 (comment) for details on how this fix works.
Same issue here: SublimeGit/SublimeGit#150
@dgreiss
Copy link

@dgreiss dgreiss commented Dec 12, 2014

Hi all,

I know this issue seems to be resolved with the package update, but I still get the same error when I try compiling with biber. Would anyone have any additional thoughts on this issue? Here's my console output:

Welcome to thread Thread-12
['latexmk', 'latexmk', 'biber', 'latexmk', '-cd', '-e', "$pdflatex='%E -interaction=nonstopmode -synctex=1 %S %O'", '-f', '-pdf', 'ut-thesis.tex']
Finished normally
12
Exception in thread Thread-12:
Traceback (most recent call last):
  File "./threading.py", line 901, in _bootstrap_inner
  File "/Users/DG/Library/Application Support/Sublime Text 3/Packages/LaTeXTools/makePDF.py", line 150, in run
    data = open(self.caller.tex_base + ".log", 'rb').read()
FileNotFoundError: [Errno 2] No such file or directory: '/Users/DG/Thesis/ut-thesis.log'
@adrfinance
Copy link

@adrfinance adrfinance commented Oct 5, 2015

Hey guys, I am getting the same issue now that the new Mac OS X is out.. Seems to be a bug with every new edition of Mac OS X .. Any idea how to fix it ? It doesnt compile through ST3, does compile through the terminal and texworks... Thanks

@PeterPablo
Copy link

@PeterPablo PeterPablo commented Oct 6, 2015

Take a look at #531 and #560. Updating to the latest version of LaTexTools should suffice to solve your problem.

@adrfinance
Copy link

@adrfinance adrfinance commented Oct 6, 2015

Thanks Pablo. Here is what I did and it now works (on a MAC) : Open SublimeText 3, press Command+Shift+P, write "install" and press enter when Package Control: Install Package appears, then exit this menu, press Command+Shift+P, select LatexTools: Reconfigure and migrate settings, press enter, then it works. cheers

@ig0774
Copy link
Collaborator

@ig0774 ig0774 commented Feb 19, 2016

Closing as this should be resolved...

@ig0774 ig0774 closed this Feb 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet