-
Notifications
You must be signed in to change notification settings - Fork 62
Don't show the output channel if checking is an action on save #133
Conversation
@sinkuu @redactedscribe, |
@KalitaAlexey I have no problem with this change. Using It also might be a good idea to improve the comment above the |
@redactedscribe, |
@KalitaAlexey The docs do not say that Maybe better than commenting finer details about each configuration parameter in the settings file, you could write "See documentation for details" on params that have certain conditions for them to work. |
@redactedscribe, |
@redactedscribe, |
@KalitaAlexey I will tomorrow. |
doc/legacy_mode/main.md
Outdated
|
||
## Configuration Parameters | ||
|
||
### Show Output | ||
|
||
The `"rust.showOutput"` configuration parameter controls whether the output channel should be shown when [a cargo command is started executing](../cargo_command_execution.md). | ||
The `"rust.showOutput"` configuration parameter controls whether the Output channel should be shown when [a Cargo command starts executing](../cargo_command_execution.md). All Cargo command other than `build` and `check` trigger this event. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why capital O in Output?
doc/legacy_mode/main.md
Outdated
|
||
## Configuration Parameters | ||
|
||
### Show Output | ||
|
||
The `"rust.showOutput"` configuration parameter controls whether the output channel should be shown when [a cargo command is started executing](../cargo_command_execution.md). | ||
The `"rust.showOutput"` configuration parameter controls whether the Output channel should be shown when [a Cargo command starts executing](../cargo_command_execution.md). All Cargo command other than `build` and `check` trigger this event. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace all with any or add s to command.
Actually the PR make different other than you are describing.
I am going to write what the PR does.
doc/legacy_mode/main.md
Outdated
|
||
However, it may be changed. | ||
### Executing Cargo commands in the integrated temrinal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo: te mr inal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will replace the
with a
if it makes more sense. Will fix typo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@redactedscribe,
We talking about any integrated terminal, not about the only specific terminal.
doc/legacy_mode/main.md
Outdated
|
||
Unfortunately, there is no way to parse output of an integrated terminal. | ||
By default, the extension executes a Cargo command as a child process. It then parses the output of the command and publishes diagnostics. This is useful if you need to run a binary and enter some text. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace This is useful with Executing Cargo command in an integrated terminal is useful.
Why do you write a Cargo? I thought the correct variant was "Cargo" because it is the tool's name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's either "Executing a Cargo command…" or "Executing Cargo commands…". It doesn't sound right without the a
or plural.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@redactedscribe,
I don't mind to keep a Cargo, but replace how I suggested This is useful.
@redactedscribe, |
@KalitaAlexey Do I need to mention anything about the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor questions.
doc/legacy_mode/main.md
Outdated
|
||
The possible values: | ||
|
||
* `true` - the output channel should be shown | ||
* `false` - the output channel shouldn't be shown | ||
|
||
When `"rust.executeCargoCommandInTerminal"` is set to `true`, `"rust.showOutput"` has no effect. | ||
The output channel will not be shown under the following conditions: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me, as not native speaker, it is ambiguous if the output channel will not be shown if all the conditions are met or at least one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point.
doc/legacy_mode/main.md
Outdated
- `"rust.executeCargoCommandInTerminal"` is set to `true` | ||
- `"rust.actionOnSave"` is set to `"check"` | ||
|
||
### Executing Cargo commands in a integrated terminal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't that be an instead of a?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, you are correct, Sorry, I am tired today.
doc/legacy_mode/main.md
Outdated
|
||
The `"rust.executeCargoCommandInTerminal"` configuration parameter controls whether [a Cargo command should be executed](../cargo_command_execution.md) in an integrated terminal. | ||
|
||
By default, the extension executes a Cargo command as a child process. It then parses the output of the command and publishes diagnostics. This is useful if you need to run a binary and enter some text. | ||
By default, the extension executes Cargo commands as a child process. It then parses the output of the command and publishes diagnostics. Executing Cargo commands in an integrated terminal is useful if you need to run a binary and enter some text. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me it sounds weird Cargo commands as a child process.
How about you?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should be better now.
Good. Thanks. |
This PR changes how the extension behave when checking (
Cargo: Check
) is executed because the user set"rust.actionOnSave"
to"check"
.Before the PR the output channel was opened if the user hadn't set
"rust.showOutput"
tofalse
.After the PR the output channel will not be opened.
It is breaking change, but I think it is the behavior we all expect.
Fixes #129