-
Notifications
You must be signed in to change notification settings - Fork 48
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
Overleaf reducing compile timeout to 20 seconds #163
Comments
Yes, only tests will show. Hopefully the time reduction is compensated by the fact that "free users’ compiles are moving to faster servers" ... |
Since it will still take a semester or more until we get reliable feedback from students and advisors if this causes any noticeable impact, I will add a short paragraph about Overleaf and the possible implications of the restrictions of the free version in Appendix A and the README.md in this repository. |
Just saw the hints in https://t.ly/uvYt5 and got myself a free Overleaf PRO subscription through my IEEE Collabratec account ;-) |
Updated list of editors (changed Texworks to VS Code). Added a paragraph about the Overleaf compile timeout (see #163).
Updated list of editors (changed Texworks to VS Code). Added a paragraph about the Overleaf compile timeout (see #163).
I opened the branch |
IntelliJ with the TeXify IDEA plugin might be another option ... |
Great, I'll add that, too. I think I'll also remove TeXnicCenter. The latest public release was over ten years ago. They did add a 2.03 alpha build some time last year, but it still seems like active development has been pretty much abandoned. |
Overleaf has announced changes, that it will reduce the compile timeout to 20 seconds on the free plan: https://www.overleaf.com/blog/changes-to-free-compile-timeouts-and-servers
This will most likely not be enough to compile our tutorial document but it might also fail for a larger thesis.
I don't think that there is an obvious solution here, except going for a pro account or switching to a local setup.
We should however conduct some tests and add this circumstance to our README to make people aware that they could run into problems.
The text was updated successfully, but these errors were encountered: