-
Notifications
You must be signed in to change notification settings - Fork 13
Grammar warnings spam stderr #88
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
Comments
That bothers me as well. Thank you for delivering the root cause. I think an option in tm4e would be fine. |
Is there already an issue on tm4e? |
Not yet, I can create an issue there and will try to provide a PR. Btw if the warnings bother you, the clangd log messages bothered me too, but they can be disabled via the clangd command |
Issue: eclipse-tm4e/tm4e#534 If accepted, we can get rid of the messages by setting |
Thank you @ddscharfe ! |
Can be closed when target platform has been updated: see also #90 (comment) |
Keep a reference to the logger, otherwise it will be garbage collected and a new logger will be used in tm4e which has a different warning level. See also eclipse-cdt#101.
Keep a reference to the logger, otherwise it will be garbage collected and a new logger will be used in tm4e which has a different warning level. See also #101.
Fixed with updated target platform |
I get lots of warnings which are written to stderr when a file is opened (only happens once per file after eclipse restart)
The warnings originate from the joni library which parses the regular expressions. In
org.eclipse.tm4e.core.internal.oniguruma.OnigRegExp
, a regex is created like thisSee https://github.com/jruby/joni/blob/master/src/org/joni/WarnCallback.java
The grammar has either to be fixed (in the https://github.com/jeff-hykin/better-cpp-syntax) or there has to be an option in https://github.com/eclipse/tm4e to disable the warnings being printed to stderr.
The text was updated successfully, but these errors were encountered: