-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update message handling for Rust 1.24. #235
Conversation
Could we get some eyes on this? I run into this issue daily. |
Do I just have to restart Sublime to get this fix? Is there a way to update rust-enhanced without restarting sublime? |
I think technically you can disable then enable rust enhanced from the package control commands. There's also a check for updates commands if I remember correctly |
Ah, i just updated rust sublime but now ctrl-b doesn't do anything anymore. Ctrl shift b still opens the menu but upon choosing one entry it also doesn't build or check etc.. |
I also tried disabling and enabling it, didn't work either.. |
@Boscop Is there anything displayed in the Sublime console? |
I'm also still getting the issue on |
@TheIronBorn which issue are you having? No messages inside a workspace? Which version of rustc are you using? |
Yes, no messages. I just tested with |
@TheIronBorn I think you need 2018-01-19 or newer. |
Ah. It works for |
Confirm it works for |
@ehuss When I press Ctrl-B, in the console it shows this:
|
@Boscop Did you restart Sublime? I think the automatic package updater doesn't always reload the package properly. |
@ehuss Now after I restarted Sublime Ctrl-B works again, but the original problem is not fixed, it still interprets the path wrong. rustc 1.25.0-nightly (da569fa9d 2018-01-16) |
@Boscop look up a few comments, you need 2018-01-19 or newer. |
Ah thanks, it works now :) |
Do i need to update the readme with which version of Rust we're supporting now? |
@Jayflux it's up to you, but I don't think it's important. I try to ensure that things work with reasonably old versions of Rust (at least back to 1.15, check requires 1.16). Specifying which nightly works is an endless game, since it will break occasionally. I've thought about setting up CI to catch breaking changes faster, but I think there would be a high risk of false errors (the tests are not as robust as I'd like, and it would be at the mercy of spurious nightly rust problems). |
@ehuss i do think CI would be a great thing, The sublime team are working on exporting their syntax checker as a separate executable so we could run syntax tests on CI, it should be available in their next release, here's an example of them using it here: |
@Jayflux The test framework I use (https://github.com/sublimetext/unittesting) actually supports running a full Sublime installation on CI and executing all the tests. I'll take a look at getting it started sometime soon. |
* Remove Cargo.lock files in tests, not needed. * Update message handling for Rust 1.24.
Rust 1.24 introduces some breaking changes, in particular:
Fixes #234.