8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If there's a parse/build error when using the feaLib command line tool, we currently do this:
fonttools/Lib/fontTools/feaLib/__main__.py
Lines 69 to 73 in 445108f
i.e. we save the font anyway and exit with status code 0.
My Makefiles and I think this is a terrible idea, and I would like to change it. Any objections / thoughts?
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
If there's a parse/build error when using the feaLib command line tool, we currently do this:
fonttools/Lib/fontTools/feaLib/__main__.py
Lines 69 to 73 in 445108f
i.e. we save the font anyway and exit with status code 0.
My Makefiles and I think this is a terrible idea, and I would like to change it. Any objections / thoughts?
The text was updated successfully, but these errors were encountered: