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

NOLOL compilation doesn't seem to respect output parameter #71

Closed
TheCodedOne opened this issue Aug 8, 2021 · 2 comments
Closed

NOLOL compilation doesn't seem to respect output parameter #71

TheCodedOne opened this issue Aug 8, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@TheCodedOne
Copy link

Describe the bug
When compiling NOLOL, the CLI doesn't seem to respect the -o/-out parameter

To Reproduce
Steps to reproduce the behavior:

  1. Make nolol script
  2. Compile it with a custom output path

Expected behavior
the CLI should output the new file to the path specified.

Platform:

  • OS: windows
  • Version of 0.1.6
@TheCodedOne TheCodedOne added the bug Something isn't working label Aug 8, 2021
@dbaumgarten
Copy link
Owner

Seems like you are right.
Funny that nobody noticed that until now.
Will be fixed with the next version, thanks for the bug-report 👍

@dbaumgarten
Copy link
Owner

Fixed as part of v0.1.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants