You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I often use the --prompt option and then hold down the return key for a while because the (pre-selected) automatic analysis based on --regress or a script is correct, yet I want to see the actual output to double check that e.g. there’s no other ICE or error sneaking in or whatnot. I feel like there should be a flag for showing the output without such workarounds. (Unless I’m missing the fact that there might already be such an option.)
The text was updated successfully, but these errors were encountered:
Yes it does work, thanks :-) But that should probably be better documented (or get a dedicated flag anyways, assuming that -vv might also add some other additional output that one wouldn’t need/want). (Also I didn’t quite see yet what -v does compared to no verbosity level at all.)
Another minimum thing would be to always show the output if the "start" fails. That often happens when either you pick the wrong start point, or your test itself is broken. Either way, the output is very important.
Unfortunately the logic around capturing the output is a little complicated.
I often use the
--prompt
option and then hold down the return key for a while because the (pre-selected) automatic analysis based on--regress
or a script is correct, yet I want to see the actual output to double check that e.g. there’s no other ICE or error sneaking in or whatnot. I feel like there should be a flag for showing the output without such workarounds. (Unless I’m missing the fact that there might already be such an option.)The text was updated successfully, but these errors were encountered: