Open brupelo opened 4 years ago
Have you tried to restart sublime text or your PC? Obviously this should not happen, but it is hard to see what's the problem from the error message.
@r-stein About restarting sublime text, yeah, definitely (few times while debuggin)... in fact, i've uninstalled/installed the package (removed completely all the remaining settings) as well.
Also, few hours ago I've opened this https://forum.sublimetext.com/t/lightweight-workflow-to-edit-preview-latex-docs-in-st3/50149/7... in there you'll find some additional info related to this one... I've stoped debugging as I didn't know the cause of the traceback i was seeing (you can see the traceback in that thread).
That said, gonna restart the PC... that's something I didn't do yet :) . Tbh, I'd love to give it a shot to this package so I can stop using TexStudio et al
The other suggestion would be to try the basic builder (ctrl + shift + b should let you change the builder). TeXify is the default builder when using MiKTeX on Windows, but that’s largely for historical reasons. TeXify doesn’t tend to provide helpful output (there’s a logging file somewhere; I don’t remember where exactly, but it seems like you might be running into some other issue).
If that doesn’t work, try running the command you see in the output in a CMD or Powershell window. That may give a better clue as to what is going on.
After a lot of researching I've figured out how to reproduce this bug quite easily.
Make sure to spawn sublime_text from the terminal, that way the package will be broken completely. Why? Because the current version it's assuming SublimeText is always spawned "normally" (ie: as a explorer.exe subprocess child on windows instead cmd's one)... Ideally the package should run normally no matter how sublime text has been spawned though.
Finally I'm testing the package and it's pretty awesome actually... Offtopic, when I'm not working on a latex document, the package won't be consuming any resources in the background, right?
Thanks for reproducing this. If you have no latex document open should not consume additional resources. However currently every start time from sublime text is delayed a little bit until it is fully loaded, because this a rather big package and we have some mechanism during the package loading. We are planing to move to a lazy load mechanism, but it does not yet exists.
Hello, newbie user here and trying to get started but I'm having some issues. Here's the steps I've followed:
Reset User Settings to Default
"texpath" : "$PATH",
or"texpath" : "",
Unfortunately that didn't work and if I try to compile a simple tex such as:
Using
LaTex
build system I'll get:With the console error:
I've read on the internet everybody saying wonderful things about this package and I'd love to give it a shot but so far the initial experience has been really painful :crying_cat_face: ... So, could you please advice? Is this a bug or it's just me being clumsy?