Navigation Menu

Skip to content
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

Why won’t --output-path option create required directories, even though --output-dir will? #847

Closed
arrowtype opened this issue Jan 22, 2022 · 3 comments

Comments

@arrowtype
Copy link

I was running a build shell script and quite confused why my variable fonts were failing to build.

Turns out, I was specifying an --output-path for them to save to – without first creating a directory structure for those paths.

This seems redundant and unintuitive, especially because --output-dir will create a required structure if it doesn’t exist.

Is this intentional? If so, can I ask the logic behind it?

Thanks!

Reproduction:

In this branch, running the ./fontmake-test.sh with FontMake 3.1.2 will reproduce this problem. Or, it seems that simply specifying a not-yet-created directory with the --output-path option will fail.

@arrowtype
Copy link
Author

I ran into this again today, and was once again confused. 😅

I also found that I can’t just run --output-dir and --output-path together – I have to make the directory first, e.g. with mkdir -p.

This isn’t a huge problem, but seems a bit inconvenient.

@anthrotype
Copy link
Member

yeah, that's odd indeed. Will be fixed with #1020

@arrowtype
Copy link
Author

Nice, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants