Stream: t-compiler/help

Topic: compiler dev with vim


Santiago Pastorino (Jan 31 2019 at 17:20, on Zulip):

have any of you use something like vim-dispatch?

Santiago Pastorino (Jan 31 2019 at 17:20, on Zulip):

I want to run ./x.py build inside vim and be able to jump between errors on the quickfix

Santiago Pastorino (Jan 31 2019 at 17:21, on Zulip):

unsure why the output I'm getting is broken, all the output lines are errors for quickfix so I can't jump quickly between files

Santiago Pastorino (Jan 31 2019 at 17:22, on Zulip):

I have 66 errors which are mechanical to fix but it will take ages going copying and pasting the file paths manually :)

Santiago Pastorino (Jan 31 2019 at 18:04, on Zulip):

problem fixed :)

Santiago Pastorino (Jan 31 2019 at 18:05, on Zulip):

this https://shinglyu.github.io/web/2016/12/25/vim-quickfix-for-rust-and-servo.html has some information about it

Santiago Pastorino (Jan 31 2019 at 18:05, on Zulip):

main thing was that I was using :Dispatch but I need to use :Make and properly configure makepkg

nikomatsakis (Jan 31 2019 at 19:05, on Zulip):

just gonna say, this works fine in emacs :)

nikomatsakis (Jan 31 2019 at 19:05, on Zulip):

but I guess you found a vim sol'n

Santiago Pastorino (Jan 31 2019 at 19:13, on Zulip):

it may be that I don't know some things really ;)

Santiago Pastorino (Jan 31 2019 at 19:14, on Zulip):

all you need to do is run :make

Santiago Pastorino (Jan 31 2019 at 19:14, on Zulip):

but of course of you don't say that you have a ./x.py it's not going to realize by itself

Santiago Pastorino (Jan 31 2019 at 19:14, on Zulip):

so you need to do :set makepkg=./x.py

Santiago Pastorino (Jan 31 2019 at 19:14, on Zulip):

and then :make build ...

Santiago Pastorino (Jan 31 2019 at 19:15, on Zulip):

I'm going to try with projectionist which is a plugin in which you can configure some things so that could be changed on a project basis

blitzerr (Feb 01 2019 at 16:14, on Zulip):

Thanks @Santiago Pastorino for posting that link and the info.

Santiago Pastorino (Feb 01 2019 at 16:22, on Zulip):

@blitzerr my intention is to build something that has everything integrated :)

Santiago Pastorino (Feb 01 2019 at 16:22, on Zulip):

let me know if you need something else :)

blitzerr (Feb 01 2019 at 16:58, on Zulip):

That's a good intention @Santiago Pastorino :grinning:

Please share if you have RLS working with rustc Dev

Santiago Pastorino (Feb 01 2019 at 17:01, on Zulip):

I do have something working

Santiago Pastorino (Feb 01 2019 at 17:01, on Zulip):

to be honest I'm not sure what is the thing that makes some suggestions and stuff

Santiago Pastorino (Feb 01 2019 at 17:01, on Zulip):

have RLS and Racer

Santiago Pastorino (Feb 01 2019 at 17:01, on Zulip):

it may be Racer, unsure

QuietMisdreavus (Feb 01 2019 at 17:02, on Zulip):

iirc racer is the thing that makes suggestions, but RLS is the thing that hooks it up into your editor

QuietMisdreavus (Feb 01 2019 at 17:02, on Zulip):

so you'll need both

Santiago Pastorino (Feb 01 2019 at 17:02, on Zulip):

yeah, that's what I have

Santiago Pastorino (Feb 01 2019 at 17:02, on Zulip):

:+1:

nikomatsakis (Feb 01 2019 at 17:03, on Zulip):

@Aleksey Kladov tells me you can use rust-analyzer with VSCode when working on rustc

nikomatsakis (Feb 01 2019 at 17:03, on Zulip):

but I've never tried it myself

Wesley Wiser (Feb 01 2019 at 18:01, on Zulip):

I might have to try rust-analyzer. Racer rarely gives me completions when working rustc but maybe it's just a user issue and I have it misconfigured or something.

blitzerr (Feb 01 2019 at 21:16, on Zulip):

@nikomatsakis are you suggesting we give up vims and emacses ? :smiley:

csmoe (Feb 02 2019 at 03:59, on Zulip):

@blitzerr I had tried vscode several times, then back to vim again and again. vscode is kind of slow while dealing with such big project as rustc, the extensions keep crashing(but my machine might be the one to blame)

Last update: Nov 11 2019 at 22:05UTC