ranged cprint -> cprint /m ? is handled like cprint /m *
Note: the following was tested with 4.28, so please drop a note if this is already fixed in 4.29.
The current cprint /m ?
breaks this (I guess as soon as this is "fixed" the vsix extension may needs adjustments) because it "handles" it like cprint /m *
, so emulating -stack-list-variables --all-values
.
Note: it would be nice if cprint /m /q *
could emulate -stack-list-variables --no-values
.