-
Notifications
You must be signed in to change notification settings - Fork 363
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
Goto error from build window #30
Comments
Are you using miktex or texlive? Also, do you have spaces in your path name? |
Sorry, I'm using Miktex & a path with no spaces. I should note, everything else works as advertised. It's just the double click to jump to error that does not. |
Do you still have this issue? If so, could you please attach a log file? I no longer have miktex on my windows machine. |
Arg, missed this sorry! I remove spaces from directory names as a work around. I'll take a look see... |
Any news? |
Sorry for the lack of updates. Just defended my MSc, been a little preoccupied. :( Just did a test with a folder with spaces in the path, and it seems fine. Do sublime plugins silently update? I.e., did you make an update to fix this? I am unable to reproduce the original error. I wish I had done a proper bug report with MikTex version number included. I wonder if this was fixed in an Sublime update?
The errors and warnings that properly skip to the file location: |
If you installed the plugin via Package Control, then yes, it should Anyway, glad it's fixed, and congrats on your defense! On Thu, Sep 6, 2012 at 12:04 PM, Chris Marsh notifications@github.comwrote:
Marciano Siniscalchi |
Thanks :) |
When there is a build error, if you double click the error, it opens a newfile instead of jumping to the line in the file.
For example,:
will create a new file background.tex [3] instead of opening background.text to line 69.
The text was updated successfully, but these errors were encountered: