build does not work

[newton108]

I'm not sure how exactly should I use this feature.
I'm in a tex file, and nothing happens after I use the cntr + alt + b or click build in the menu bar.

[thomasjo]

Unfortunately the user experience is not very friendly yet; success and error logging is only logged in the Developer Tools console. Enable it by pressing CMD + ALT + I (or via View -> Developer -> Enable Developer Tools). Once the console is visible, try executing the build on your .tex file once more. Most likely you'll see an error message.

The package is not documented at all, beyond the README, but I'm hoping to get around to that over the weekend. My point though is that unless your TeX distribution is located under /usr/texbin, you will need to configure this, which is most easily done from the package settings window.

Also, what operating system are you using, and which TeX distribution? Right now the only tested and verified combination is OS X and TeX Live (because up until two days ago, OS X was the only supported OS). I plan on supporting MikTeX in the near future.

[newton108]

TeXification failed! Check the log file for more info... latex.coffee:36
module.exports.showError latex.coffee:36
(anonymous function) latex.coffee:26
(anonymous function) latexmk.coffee:14
EventEmitter.emit events.js:123
maybeClose child_process.js:821
(anonymous function) child_process.js:1038
EventEmitter.emit events.js:101
(anonymous function) net.js:459

I use texlive 2013 and OS X mavericks. latex command is under /usr/texbin

[thomasjo]

You should have a <filename>.log file in the same folder as your .tex file. Would you mind sharing the contents of that file? Since I'm not exposing the actual underlying errors yet, I need to look at the log file produced by latexmk.
This is assuming a log file gets produced. There might be a preceding error of course, preventing latexmk from being invoked as expected.

[ghost]

Are there any spaces in your file/folder names? Then you might be having the issue referenced above...

[newton108]

Yes, there is space in the path of the file, and I try build somewhere else and it works! Thank you.