Closed gcampbell-msft closed 2 months ago
@jasonmp85 ended up finding the answer to his questions: https://github.com/microsoft/vscode-makefile-tools/issues/506#issuecomment-1947218152, but the possible issue still stands about the pop-up being misleading.
I was confused as well, especially because I didn't know that make
had a --dry-run
command-line option.
@MightyCreak Thank you for the feedback, we are currently working on a PR #573 that removes the dry-run pop-up. Thanks!
@MightyCreak We have merged #573 and it should be available in pre-release within the hour.
Thanks! And thank you for the heads up!
Thanks for the resolution! Reporting this felt minor, but I'm glad to see the attention to user-experience here!
Happy to see your issue has been resolved, thanks for contributing to Developer Community.
--dry-run
relevant at all? This is unexplained, and there are no buttons for more information. Is VS Code going to run things in--dry-run
without me asking? Or is this just informing me of a side-effect possible inmake
, a tool my project is, definitionally, already using?make
with--dry-run
for some reason and I need to confirm myMakefile
has no side effects, then ask thatmake
behavior? It should probably read something like "It is possible formake
to have side-effects even when--dry-run
is provided. Enable Makefile extension for this project?"Originally posted by @jasonmp85 in https://github.com/microsoft/vscode-makefile-tools/issues/506#issuecomment-1947191752