Sorry if I'm misunderstanding something about how Sublime works or a config option I missed.
When I save a file, it runs the Rust check. Errors and warnings show up just fine. Great!
But the build output box (Ctrl+Shift+O) is only updated when I do a "real" build (Ctrl+B).
This means that the F4 and Shift+F4 keys for jumping between build results don't work properly after a normal "Rust check;" they use outdated build results from the last time I hit Ctrl+B.
Is this how it's supposed to work?
It makes the "Rust check" less useful. I save, I get 4 errors, 1 is in the current file I just changed, and the other 3 are who-knows-where, so I have to trigger a build to update the build output window. This happens to me so frequently.
Sublime version: build 4169
RustEnhanced version: 2.28.0
Cargo version: 1.93.0
Tools > Build System is set to RustEnhanced
Platform: macOS Sequoia
RustEnhanced.sublime-settings:
{
"rust_message_theme": "solid",
}
Sorry if I'm misunderstanding something about how Sublime works or a config option I missed.
When I save a file, it runs the Rust check. Errors and warnings show up just fine. Great!
But the build output box (Ctrl+Shift+O) is only updated when I do a "real" build (Ctrl+B).
This means that the F4 and Shift+F4 keys for jumping between build results don't work properly after a normal "Rust check;" they use outdated build results from the last time I hit Ctrl+B.
Is this how it's supposed to work?
It makes the "Rust check" less useful. I save, I get 4 errors, 1 is in the current file I just changed, and the other 3 are who-knows-where, so I have to trigger a build to update the build output window. This happens to me so frequently.
Sublime version: build 4169
RustEnhanced version: 2.28.0
Cargo version: 1.93.0
Tools > Build System is set to RustEnhanced
Platform: macOS Sequoia
RustEnhanced.sublime-settings:{ "rust_message_theme": "solid", }