-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
File 'article.cls' not found when using PyCharm on a Mac #1785
Comments
Assuming that We can of course implement a workaround for PyCharm, perhaps a simplified version of the SDK system we use in IntelliJ. Basically it allows you to provide the path to BasicTeX, and then TeXiFy figures out the rest. I think BasicTeX is just a fancy name for a small TeX Live installation, so if you have IntelliJ you would select a TeX Live SDK when creating a new project. Can you provide the output of |
I had a (maybe?) similar issue last week with \LoadClass{article}, see TEX-109. Don't know if it's related. It is on windows... Edit: 109 not 108 |
Yes, I specified the path to Yes, exactly, BasicTeX is a smaller version of MacTeX. I don't have "TeX Live SDK" as an option when I create a new project. Would that solve the problem if I installed MacTeX instead of BasicTeX? |
Hi, I found this issue because I have probably the same exact problem. I'm trying to use TeXiFy on Mac with Intellij. The only problem here seems to be article.cls not being found. I've also tried adding a TeXLive SDK at |
[Moved comment to #1815] |
Hello there,
Thank you for creating the plugin! I love it that I can write LaTeX documents right inside PyCharm!
I'm using PyCharm Pro 2020.3, and TeXiFy 0.7.3. I'm on a Mac, using BasicTeX.
I'm getting an error from the inspection. It underlines
article
in\documentclass[11pt]{report}
stating thatarticle.cls
cannot be found. However, if I usepdflatex
from BasicTeX to compile the file, it works just fine, and the pdf file is created correctly. Is that a bug or am I missing some configuration that I need to do?The text was updated successfully, but these errors were encountered: