-
-
Notifications
You must be signed in to change notification settings - Fork 165
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
Fix the check_latex
script.
#2545
Fix the check_latex
script.
#2545
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On my develop server check_latex
runs successfully whether I am on the develop branch or this PR branch. I am not sure why. Approving this, but I don't feel like I tested it since I had no change in behavior.
I am also not able to reproduce the error, even if I unset I did notice that the output of the script changed, before it would only output On a side note the script did fail with |
note, just because I don't think I was clear, it still outputs |
4cac5c0
to
27ace61
Compare
The output of the pg directory was a debugging line that I added and forgot to remove. It has been removed now. |
If the I also have noticed the |
The addition of the requirement of PG files for hardcopy (namely the `pg.sty` file), means that the `check_latex` script needs to know where the pg directory is. So find that the same way the webwork2 app does. This fixes issue openwebwork#2543.
27ace61
to
42cfb80
Compare
I still cannot get Further I even tested setting |
Okay, I tracked it down, in Furthermore, the patch fixes the issue. |
Ahh, that makes sense. If you still have the old setting in |
…tfix Fix the `check_latex` script. (hotfix of #2545)
The addition of the requirement of PG files for hardcopy (namely the
pg.sty
file), means that thecheck_latex
script needs to know where the pg directory is. So find that the same way the webwork2 app does.This fixes issue #2543.