Stream: t-compiler/help

Topic: Sublime-text


marmeladema (Apr 11 2020 at 14:46, on Zulip):

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?

marmeladema (Apr 11 2020 at 14:47, on Zulip):

I am currently doing some refactoring and having to open manually hundreds of file and manually jump to the error line is very cumbersome

marmeladema (Apr 11 2020 at 14:49, on Zulip):

Put it another way: what workflow and tools do you use to work on the compiler?

eddyb (Apr 11 2020 at 15:18, on Zulip):

how do you "manually jump"?

eddyb (Apr 11 2020 at 15:19, on Zulip):

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

marmeladema (Apr 11 2020 at 15:24, on Zulip):

Right now, i am running ./x.py check in a separate terminal and manually open files in sublime text by browsing in the directories

marmeladema (Apr 11 2020 at 15:24, on Zulip):

Thats .. suboptimal, to say the least

eddyb (Apr 11 2020 at 15:24, on Zulip):

does sublime not have an integrated terminal?

eddyb (Apr 11 2020 at 15:24, on Zulip):

or some kind of feature where you get a "build output"?

eddyb (Apr 11 2020 at 15:25, on Zulip):

by running arbitrary commands?

marmeladema (Apr 11 2020 at 15:25, on Zulip):

i am looking at the doc right now

eddyb (Apr 11 2020 at 15:26, on Zulip):

@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"

eddyb (Apr 11 2020 at 15:26, on Zulip):

what you're describing is way worse

eddyb (Apr 11 2020 at 15:27, on Zulip):

(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)

marmeladema (Apr 11 2020 at 15:27, on Zulip):

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

marmeladema (Apr 11 2020 at 15:30, on Zulip):

well, i managed to run ./x.py check from sublime-text but it does not parse anything and i cannot click on the paths.

eddyb (Apr 11 2020 at 15:30, on Zulip):

not even Ctrl+Click?

marmeladema (Apr 11 2020 at 15:31, on Zulip):

yep, but there is another option to parse the output with a regex, ill try that

Last update: Sep 28 2020 at 16:30UTC