-
Notifications
You must be signed in to change notification settings - Fork 0
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
bugs with config override logic #58
Comments
--hints:off --hint:successx:on
does not honor --hint:successx:on
This is intended, and changing it would make the code really messy. |
after ad6d559 from nim-lang#13606
|
proposal for
|
bugs as of devel 70bd41d
some are pre-existing bugs, other are recent regressions
regression:
--listcmd --hint:link:on --hint:cc:off
should show "just the (verbose) link command, but instead it also shows the (verbose) compilation commandsnote: hintLink was recently "broken" in Only print the link command when listCmd is active and fix the docs nim-lang/Nim#13603 and we agreed on proposal 1 to fix it (see Only print the link command when listCmd is active and fix the docs nim-lang/Nim#13603 (comment)); this should work but doesn't yet:
--verbosity:0 --hint:FOO:on --hint:BAR:of
works with every FOO,BAR except for--hint:cc:on
--hints:off --hint:successx:on
does not honor--hint:successx:on
but it should because it comes AFTERmore generally for other hints (eg
--hint:conf:on
).The point of overriding like this is it makes it easy to test 1 thing at a time (whether inside a test where we just want to check 1 aspect, or when you want to debug a specific issue etc)
It should behave like
--verbosity:0
which CAN be overridden (except for --hint:cc:off bug specific to cc)--verbosity:0
should imply --hint:processing:off but does notnot sure about these
--verbosity:0 --hint:exec:on
works as intended (enables hintExec) but--hint:exec:on --verbosity:0
also enables hintExec even though --verbosity:0 comes afterThe text was updated successfully, but these errors were encountered: