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

How to pass multi CLI arguments to antlr? #180

Closed
ArcticLampyrid opened this issue Jul 23, 2022 · 2 comments
Closed

How to pass multi CLI arguments to antlr? #180

ArcticLampyrid opened this issue Jul 23, 2022 · 2 comments
Labels
possible bug Could be a bug

Comments

@ArcticLampyrid
Copy link

Like #69
options.additionalParameters only supports to pass a single argument currently.


A detailed example:

{
    "antlr4.generation": {
        "additionalParameters": "-encoding UTF8"
    }
}

will pass "-encoding UTF8" instead of "-encoding" "UTF8"

@mike-lischke mike-lischke added the possible bug Could be a bug label Jul 25, 2022
@JohnLouderback
Copy link

I'm experiencing the same issue. The encoding is being interpreted incorrectly, but I don't seem to have any way to pass it in.

@ArcticLampyrid
Copy link
Author

For encoding problems, since VSCode did't yet provide encoding-related APIs (microsoft/vscode#156039), it's impossible to handle it perfectly.
But I recommend to use UTF-8 by default in CLI arguments, as many parts of this extension have assumed that the encoding is UTF-8 when analyzing the grammar files.

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

No branches or pull requests

3 participants