by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 05 22:56
    Undin labeled #5878
  • Aug 05 22:12
    hahnrobert opened #5878
  • Aug 05 21:06
    Undin edited #5877
  • Aug 05 21:05
    Undin labeled #5877
  • Aug 05 21:05
    Undin assigned #5877
  • Aug 05 21:05
    Undin opened #5877
  • Aug 05 20:45
    Undin assigned #5783
  • Aug 05 20:32
    vpiryns closed #5767
  • Aug 05 19:11
    Undin labeled #5783
  • Aug 05 19:10
    Undin labeled #5783
  • Aug 05 19:02
    Kobzol assigned #5875
  • Aug 05 19:01
    Undin labeled #5832
  • Aug 05 19:01
    Undin closed #5832
  • Aug 05 19:01
    Undin reopened #5832
  • Aug 05 19:01
    Undin closed #5832
  • Aug 05 19:01
    Undin labeled #5832
  • Aug 05 19:01
    Undin labeled #5832
  • Aug 05 18:58
    Undin labeled #5861
  • Aug 05 18:54
    Undin labeled #5859
  • Aug 05 18:53
    Undin labeled #5815
Teiva Harsanyi
@teivah
cargo check!!
I mean I did not find how to setup cargo check only once I save the file!
I mean not from a file watcher, I want the compilation errors to be seen on the editor directly (not the terminal)
Jakub Beránek
@Kobzol
If you open the Cargo window and use the "Run external linter" action, it will run the linter in the IDE and display errors in a structured way, with direct links to source code etc.
I usually bind the action to a keybind and run it after I change something and I want to lint it.
Settings -> Keymap -> Run External Linter
Teiva Harsanyi
@teivah
mmh I see, yes thanks that's not too bad I suppose
Jakub Beránek
@Kobzol
You can also choose whether to run cargo check or cargo clippy in Settings - > Languages & Frameworks -> Rust -> Cargo -> External linter
Teiva Harsanyi
@teivah
I would have preferred if we would had a Run external linter on save in Languages & Frameworks -> Rust -> Cargo
but at least thanks, it's kinda saving my day ;)
Jakub Beránek
@Kobzol
I'll create an issue for that and if it seems reasonable, I'll try to implement it. To be honest it seems to me that it would be annoying for most users, to show the inspection GUI after each save. But as an off-by-default option for specific users, why not I guess.
Teiva Harsanyi
@teivah
well, the best option would be to not have this new window showing up
I mean the perfect scenario would be I save then I see directly in the code editor the potential issues
Jakub Beránek
@Kobzol
right, that makes sense
Teiva Harsanyi
@teivah
but thanks at least it's helping me a lot
Jakub Beránek
@Kobzol
I created an issue: intellij-rust/intellij-rust#5542 let's see what the others think :-)
Teiva Harsanyi
@teivah
thanks @Kobzol
Matyáš Racek
@panstromek
image.png
@Kobzol You're on fire ❤️
Vlad Beskrovnyy
@vlad20012
@Kobzol is legendary ❤️
Jakub Beránek
@Kobzol
it's sometimes a form of procrastination for me :) but I use the plugin on a daily basis, so it's a win-win for me when it gets improved
Vlad Beskrovnyy
@vlad20012
We just created a release branch release-125. The release is scheduled for 29.06.2020.
Ara Adkins
@iamrecursion
Quick Q. Does intellij-rust obey rustup directory overrides? I'm having an issue where the toolchain for a given repo is overridden, but Clion is still seeing my global default toolchain
The same issue is present in IntelliJ itself.
Vlad Beskrovnyy
@vlad20012
Oh, no, rustup directory overrides are not supported. Furthermore, opening a project with rustup override leads to lots of bugs and weird things
Ara Adkins
@iamrecursion
How so?
I assume it'll be fine if I manually specify the correct toolchain?
Vlad Beskrovnyy
@vlad20012
Well, you can specify rustup channel in a run configuration
image.png
Ara Adkins
@iamrecursion
the cargo command configurations pick up the correct toolchain from the override
Vlad Beskrovnyy
@vlad20012
A real possibility to switch toolchains is work in progress intellij-rust/intellij-rust#5529
Ara Adkins
@iamrecursion
That's great news.
Vlad Beskrovnyy
@vlad20012

the cargo command configurations pick up the correct toolchain from the override

It's coold, but, as I mentioned, if you have rustup override in a project, Intellij Rust starts behaving strangely. At least, it was so some time ago. Rustup override is a very rarely used feature, so I'm not sure

Ara Adkins
@iamrecursion
What kind of strangeness should I be on the lookout for?
Maybe I'm wrong and you need 2 things to run into the bug:
1) rustup override
2) multiple cargo projects in a single IDEA project
Ara Adkins
@iamrecursion
Ah yeah my situation is multiple crates all using the same toolchain
in one cargo workspace
Vlad Beskrovnyy
@vlad20012
A workspace should works fine
Ara Adkins
@iamrecursion
It seems to, for the most part!
I'm seeing some errors that don't occur during compilation, though
Vlad Beskrovnyy
@vlad20012
Intellij Rust has some false-positives, unfortunately(
Ara Adkins
@iamrecursion
Fair enough!
Vlad Beskrovnyy
@vlad20012
We just created a release branch release-126. The release is scheduled for 13.07.2020.
Ara Adkins
@iamrecursion
I'm having an issue where builds using cargo done through "Run Anything" are failing randomly with "crate not found for $foo"
When done in the shell it works absolutely fine
Ara Adkins
@iamrecursion
Vlad Beskrovnyy
@vlad20012
Thanks!
Evan Stoll
@evanjs

So I am trying to set some breakpoints on gtk-rs, which is a dependency on my project.
Currently, the breakpoints seem to be valid/recognized by the debugger (they are red), but do not suspend the program.

Note that I can step into these areas of execution just fine.
It's just that I can't have the debugger run until it hits a breakpoint in an external library.

Is suspending on breakpoints in external libraries supported?

Evan Stoll
@evanjs
rust-lldb seems to stop at the breakpoint just fine when run outside of CLion