Hello! I asked my question on the #general room but since no one answered and its more related to the compiler, i'll try here. I usually using sublime-text as text editor with rust enhanced plugin. I haven't tried to enable it for the compiler as it uses the special
./x.py build script and not cargo directly. Is there any tricks to make sublime-text work with the toolchain used by the compiler? In such a way that the build errors are reported directly in the code editor?
I am currently doing some refactoring and having to open manually hundreds of file and manually jump to the error line is very cumbersome
Put it another way: what workflow and tools do you use to work on the compiler?
how do you "manually jump"?
in VSCode, even if I run
cargo check in a terminal (or
./x.py check in Rust's case), I can Ctrl+Click on error locations
Right now, i am running
./x.py check in a separate terminal and manually open files in sublime text by browsing in the directories
Thats .. suboptimal, to say the least
does sublime not have an integrated terminal?
or some kind of feature where you get a "build output"?
by running arbitrary commands?
i am looking at the doc right now
@marmeladema heh for me it was infuriating enough that I can Ctrl+Click paths
rustfmt --check errors outputs but they don't have
:123 right after them for the line number, instead they say "foo.rs at line 123"
what you're describing is way worse
(I fixed this by finding a way to format on save w/o the RLS extension, so that I don't need to fix formatting differences from those
rustfmt --check errors)
yeah^^ i am trying to fix that. There is a way to define a custom build system that can run arbitrary comment, ill dig into that. I just hopes it can parse blindly the ouput and detect paths so that i can double click on it
well, i managed to run
./x.py check from sublime-text but it does not parse anything and i cannot click on the paths.
not even Ctrl+Click?
yep, but there is another option to parse the output with a regex, ill try that