ctrl+shift+p filters: :st2 :st3 :win :osx :linux

Rust Enhanced

by rust-lang ST3 Trending

The official Sublime Text 3 package for the Rust Programming Language



  • Total 50K
  • Win 17K
  • OS X 18K
  • Linux 16K
Nov 20 Nov 19 Nov 18 Nov 17 Nov 16 Nov 15 Nov 14 Nov 13 Nov 12 Nov 11 Nov 10 Nov 9 Nov 8 Nov 7 Nov 6 Nov 5 Nov 4 Nov 3 Nov 2 Nov 1 Oct 31 Oct 30 Oct 29 Oct 28 Oct 27 Oct 26 Oct 25 Oct 24 Oct 23 Oct 22 Oct 21 Oct 20 Oct 19 Oct 18 Oct 17 Oct 16 Oct 15 Oct 14 Oct 13 Oct 12 Oct 11 Oct 10 Oct 9 Oct 8 Oct 7 Oct 6
Windows 0 8 12 11 11 13 21 22 9 6 11 13 9 10 10 13 13 11 4 13 11 10 7 2 2 10 11 10 10 8 6 9 13 6 12 9 12 15 9 9 4 8 10 9 8 9
OS X 1 13 16 14 6 15 20 11 3 12 13 4 8 9 8 8 11 8 9 9 9 10 7 4 7 5 7 5 7 5 8 4 8 8 17 4 8 11 10 8 6 15 14 9 6 17
Linux 4 15 18 14 23 15 19 21 10 4 14 7 8 11 3 5 8 7 13 10 5 9 10 7 9 5 9 7 12 10 7 5 11 6 8 11 6 10 12 7 7 10 14 13 11 16



Rust Enhanced


This is a Sublime Text 3 package which supports Rust starting with version 1.0, it makes no attempt at supporting earlier incompatible versions.

This package used to be called 'Rust', but as of version 3, Sublime now comes with Rust built-in. The built-in version on Sublime is actually just a snapshot of this package with some fixes from quite some time ago. This package is still active and will continue to update and release, so if you want up to date features, and extra tools (such as syntax checking or building) we recommend using this package. It does not automatically override the built-in Rust package so you will have to disable it, and check “Rust Enhanced” is set. There is currently no plan to push upstream changes back into the Sublime Core Packages repo, and extra features will stay here.

For syntax highlighting for Cargo files. Its recommended installing this with the TOML package.

Running Tests with Rust EnhancedHighlighting errors and warnings with Rust Enhanced


Install the Package Control package if you haven't got it yet. Package Control is the best way to install packages for Sublime Text. See http://wbond.net/sublime_packages/package_control/installation for instructions.

Open the palette (control+shift+P or command+shift+P) in Sublime Text and select Package Control: Install Package and then select Rust Enhanced from the list. That's it. If you can't see Rust Enhanced its most likely because you're using Sublime Text 2.

It is possible that the built-in Rust package will cause conflicts with Rust Enhanced. If the default syntax for Rust documents is Rust instead of Rust Enhanced, then this is likely the case. A recommended solution is to disable the built-in Rust package. You can do so through Package Control: Disable Package -> Rust.


Go To Definition

Cargo Build

Rust Enhanced has a custom build system tailored for running Cargo. It will display errors and warnings in line using Sublime's phantoms. It also supports a variety of configuration options to control how Cargo is run.


See the build docs for more information.

Cargo tests with highlighting

Thanks to urschrei we have Highlighting for: - passed test - failed test - failed test source line (clickable) - total number of passed tests - total number of failed tests > 0 - total number of ignored tests > 0 - total number of measured tests > 0



Syntax Checking

Rust Enhanced will automatically perform syntax checking each time you save a file. Errors and warnings are displayed in line the same way as the build system. This relies on Cargo and Rust (>= 1.8.0) being installed and on your system path. Plus Sublime Text >= 3118.

Settings for controlling the on-save syntax checking:

Setting Default Description
rust_syntax_checking true Enable the on-save syntax checking.
rust_syntax_checking_method "check" The method used for checking your code (see below).
rust_syntax_checking_include_tests true Enable checking of test code within #[cfg(test)] sections (only for no-trans method).

The available checking methods are:

Method Description
no-trans Runs the rustc compiler with the -Zno-trans option. This will be deprecated soon, however it has the benefit of supporting #[test] sections.
check Uses cargo check (requires at least Rust 1.16).
clippy Uses cargo clippy. This requires Clippy to be installed. This also may be a little slower since it must check every target in your package.

This will use the same configuration options as the “Check” and “Clippy” build variants (for example, extra environment variables, or checking with different features). See the build docs for more information.

Projects with multiple build targets are supported too (–lib, –bin, –example, etc.). If a cargo project has several build targets, it will attempt to automatically detect the correct target. In some rare cases, you may need to manually specify which target a file belongs to. This can be done by adding a “projects” setting in Rust.sublime-settings with the following format:

"projects": {
       // One entry per project. Keys are project names.
       "my_cool_stuff": {
           // Path to the project root dir without trailing /src.
           "root": "/path/to/my/cool/stuff/project",

           // Targets will be used to replace {target} part in the command.
           // If no one target matches an, empty string will be used.
           "targets": {
               "bin/foo.rs": "--bin foo",  // format is "source_code_filename -> target_name"
               "bin/bar.rs": "--bin bar",
               "_default": "--lib"         // or "--bin main"


To customize the settings, use the command from the Sublime menu:

Preferences > Package Settings > Rust Enhanced > Settings - User

Additionally, you can customize settings per-project by adding settings to your .sublime-project file under the "settings" key.


The files are written in the JSON format supported by the Sublime Text package AAAPackageDev, because the format is much easier to read / edit than the xml based plist format.

So install that package and then work on the .JSON-* files. There is a build system that comes with that package, so if everything is set up right, you should just be able to trigger the build (F7) and get the corresponding .tmLanguage / .tmPreferences files. It will also display errors if you have not formatted the file correctly.

One impact of using this indirect format is that you usually have to double escape anything in the match patterns, ie, “\(” has to be “\(” as otherwise it will try to interpret '\(' as a JSON escape code (which doesn't exist).

We have just moved to the new .sublime-syntax file, which only supports ST3 and upwards. Any PR's should be updating this file and not the old tmLanguage file.


Created 2012 by Daniel Patterson, as a near complete from scratch rewrite of a package by Felix Martini.

This project is currently maintained by Jason Williams


This package is licensed under the MIT License.