Currently, this is not highlighted like "break" is.

#[attribute(x)] is highlighted correctly, but
#[attribute(x, y)] is not highlighted

The case I discovered this with was #[deriving(Eq, FromPrimitive)]

https://github.com/zargony/atom-language-rust/blob/master/snippets/rust.cson
https://github.com/abaez/ta-rust/blob/master/snippets.lua
https://github.com/freebroccolo/rust-snippets/blob/master/rust-snippets.el
https://github.com/darookee/vim-snippets/blob/master/UltiSnips/rust.snippets

Maybe you can add the missing snippets from other editors and implement it in your project.

Many standard libc types are already highlighted (e.g. c_int, ssize_t, FILE), however there's a lot more, like uint64_t etc: http://web.mit.edu/rust-lang_v0.11/doc/libc/index.html

The ones I noticed so far (mostly from stdint):

int8_t
int16_t
int32_t
int64_t
uint8_t
uint16_t
uint32_t
uint64_t
dirent_t
suseconds_t
wchar_t

Constants:

S_IFLNK

For the sake of consistency, maybe these constants as well:

pub use consts::os::posix88::{PROT_READ, PROT_WRITE, PROT_EXEC};
pub use consts::os::posix88::{MAP_FIXED, MAP_FILE, MAP_ANON, MAP_PRIVATE, MAP_FAILED};
pub use consts::os::posix88::{EACCES, EBADF, EINVAL, ENODEV, ENOMEM};
pub use consts::os::posix88::{ECONNREFUSED, ECONNRESET, EPERM, EPIPE};
pub use consts::os::posix88::{ENOTCONN, ECONNABORTED, EADDRNOTAVAIL, EINTR};
pub use consts::os::posix88::{EADDRINUSE, ENOENT, EISDIR, EAGAIN, EWOULDBLOCK};
pub use consts::os::posix88::{ECANCELED, SIGINT, EINPROGRESS};
pub use consts::os::posix88::{ENOSYS, ENOTTY, ETIMEDOUT, EMFILE};
pub use consts::os::posix88::{SIGTERM, SIGKILL, SIGPIPE, PROT_NONE};
pub use consts::os::posix01::{SIG_IGN};

The function declaration fn foo<T: Iterator<Item=i32>>(x: &T) isn't highlighted like a function declaration. The Item=i32 associated type constraint is throwing it off.

It seems like the bracket closes the attribute even if it is part of the string:

--> E:\Source\wio-rs\src\console.rs:175:26

is not handled by the Cargo.sublime-build file_regex as

--> ([^:]+):([0-9]+):([0-9]+)$

does not allow a : in the path.

I added a new issue for this seems it seems to be a different cause.

ST 3, Rust plugin, tried building using Cargo and I got this:

[Errno 2] No such file or directory: 'cargo'
[cmd: ['cargo', 'build']]
[dir: /Users/dutt/workspace/rust/gridwar/src/entities]
[path: /usr/bin:/bin:/usr/sbin:/sbin]
[Finished]

Which is understandable, since I get this:

dutt$ which cargo
/usr/local/bin/cargo

How do I edit the path used by the plugin?

Should we upstream this to the main Sublime repo? https://github.com/sublimehq/Packages

cc @brson @nrc @glennw

I'm using the eiffel theme for my rust code and when I syntax check with a warning I get the following:

I'm sure it's possible but I'm not sure how to change the colour theme for these errors.

Here's the error I get when trying to install this package via Package Control in the latest ST3 dev build:

Package Control: Error downloading package. HTTP exception InvalidCertificateException (Host codeload.github.com returned an invalid certificate ([SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:550)) ) downloading https://codeload.github.com/jhasse/sublime-rust/zip/master.

Doc-comments allow markdown within them it'd be nice if they reflected that at least somewhat and looked different from normal comments.

... which it probably shouldn't be since it's just a module.

use std::str::from_utf8;

Switching from brew to rustup causes this package to break
by default this package checks the typical paths /bin:/usr/bin etc but rustup puts rust in ~/.cargo/bin

I've tryed adding that folder for the path: but it doesn't seem to be working for me.
Would love to see if anyone can get this working

Rust build paths:

    "osx":
    {
        "path": "/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin"
    },

When i try changing the path in https://github.com/rust-lang/sublime-rust/blob/master/Rust.sublime-build and reload the plugin, the path is still the same.

As you can see in the images, even though i add a new path to the end, it does not reflect when running the plugin. I've tried adding a lot of different paths.

Is this a bug within Sublime 3 itself? @FichteFoll @wbond
Build: 3125

Note:
This issue has also been mentioned in #22

When I try to Build or Run using the Cargo build system, the status bar says "Building" but nothing shows up on the console.
Commenting out the "syntax" specification (line #4 in the Cargo.sublime-build file) fixes the issue, at least on my system.

Environment:
Windows 7 64-bit
rustc 0.12.0-nightly (740905042 2014-09-29 23:52:21 +0000)
cargo 0.0.1-pre-nightly (2d101e2 2014-10-09 19:44:57 +0000)
Sublime Text 2 Version 2.0.2, Build 2221

variable type highlight too greedy now and highligths all from : to last = in a line. pic related

When defining a module in a lib.rs or mod.rs file, the module name is always highlighted red. The corresponding error message is "Error: file not found for module xxx" with xxx beeing the name of the module. However, compiling and executing works just fine.

After I pressed ctrl+B or click the menu compile, nothing happend.
I checked the Rust.sublime-build, the file content was written like this
selector:source.rust
Is it a correct form? or I should change it to source.rs?
Also, how can I use cargo as a compile and run tool?
looking forward to any solution

Both the default syntax highlighting and the highlighting included in this package are named Rust, leading to a naming conflict where the built-in highlights take priority. Because they are named the same, any attempts to rebind back to the highlights included in this package fail. This could probably be fixed by renaming these highlights to "Rust Enhanced", removing the naming conflict.

I have other projects in sublime in Go, PHP and Javascript. Therefore my build system is set to automatic.
Yet when I hit build (ctrl+b) cargo options always comes up instead of just building.

Can we scope cargo builds to just rust projects please?
Maybe add selector.rust in the cargo build file?

...which probably shouldn't be the case since attributes have a semantic meaning, unlike comments. They often come out greyed out and hardly readable, such as in Solarized Dark.

For example:

Option<extern "C" fn (c_int)>

fn is not highlighted as keyword (and if there is no space before the opening parenthesis, it's erroneously highlighted as an identifier).

I have switched to Atom for developing in Rust. Therefore would be great if someone else wants to maintain this package :)

I'd love to know what sublime-rust actually does if possible :)

Hi all,

Sorry to use the issue tracker as a message box, but I wanted to mention that we're working on a possible update to the compiler error output: rust-lang/rfcs#1644 This might have an impact on the sublime plugin if you all happen to be parsing the compiler output.

That said, we're also thinking about standardizing a JSON format, so IDEs can get more information from the compiler (and not have to parse the error).

Would love to chat and hear your thoughts.

Thanks for this package! I don't see the print! or println! macros in master but I think they would be handy.

<snippet>
    <content><![CDATA[
print!("${1}"${2:, ${3:args}})
]]></content>
    <scope>source.rust</scope>
    <tabTrigger>print!</tabTrigger>
    <description>print! macro</description>
</snippet>

and

<snippet>
    <content><![CDATA[
println!("${1}"${2:, ${3:args}})
]]></content>
    <scope>source.rust</scope>
    <tabTrigger>println!</tabTrigger>
    <description>println! macro</description>
</snippet>

Performance is notably worse than with a non-syntax highlighted file, and compared to other syntax highlightings.

As I type I can see new temp files appearing in Sublime's sidebar:

The temp files contain copy of the currently edited file.

For example, given a function

fn distance(self, other: Vec3f) -> f64 {
    (self - other).length()
}

self does not appear highlighted as other keywords would.

Currently, the plugin can't always provide a good mapping between filenames associated with error messages and filenames open in the editor. Reasons this might fail:

• Use of the #[path] attribute with ../ in it
• Symbolic links
• (possibly others)

Hello,

Due to this bug: rust-lang/cargo#2494 when the Build command is given multiple times the error messages are not persisted.

This can be worked around by running cargo clean prior to building.

Whenever I create an array, the semicolon gets rewritten to the end of the line.

expect: let test:[u8;2]

result: let test:[u8];2;

Rust have adopted a new style of unicode char syntax

const UNICODE_CHAR: char = '\u{0086}';

Any number followed by the f literal is highlighted when used like

use hello1fworld;

Hmm... GitHub highlighter does it too.

Currently only the functions are defines as symbol (you can see them by using ctrl+r or ctrl+shift+r). It could be great to have function and [struct/enum] and functions.

so the following code :

struct Aaa {
    field1: i32,
}

impl Aaa {
    pub fn new (f1: i32) -> Aaa {
        // code here
    }

    fn another_fn() {
        // code here
    }
}

impl Display for Aaa
{
    fn fmt(&self, f: &mut Formatter) -> Result<(), Error> {
        // code here
    }
}

would be converted, on the goto symbol pallet :

struct Aaa
impl Aaa
    new
    another_fn
impl Display for Aaa
    fmt

Hey, I just found, that Rust supports nested block comments like

/* a comment /* within a comment */ that's cool */

But the part that's cool */ is highlighted as if it was code. (Don't know if this is even possible to accomplish with Sublime's syntax definitions, a very quick google search didn't find anything)

when I edit rs file, sublime create a lot of temp file .menu tree like this
(fail to upload a picture :( ):
main.rs
tmp9tzn72
tmpaeu3zy
tmphhg8wt
tmprjw53i
tmpurpnft
tmpv63r4d
but when I edit other kinds of files,such as py and html,there is no temp file made;
so I afraid that I can do something with the sublime-rust settings.

See the snippet below. This snippet is a documentation block in a Rust source file which contains a code example. As such the sublime-rust parser isn't able to recognize the code example separately. This is manageable. But a bigger issue is: since there is a ] present in the code block, the parser thinks that the #doc block has finished there itself. This breaks the syntax highlighting completely for the rest of the file. The solution I can think of at this moment is that [doc=" should be matched with "] for closing the documentation block. Don't know how is it implemented internally.

#[doc="Returns a 64-bit signed integer matrix whose entries are
picked up from a slice in column wise order.
    let m = matrix_i32(2,2, [1,2,3,4]);
    for i in range(0, 4){
        let c = i >> 1;
        let r = i & 1;            
        assert_eq!(m.get(r, c), (i + 1) as i32);
    }
"]

Given I have a rust source file which would emit a warning,
When I trigger the build from within Sublime,
Then the console displays the whole path for the source file.

/Users/kostaskarachalios/Code/Learning/Rust/for Rubyists/fizzbuzz.rs:15:13: 15:23 warning: variable does not need to be mutable, #[warn(unused_mut)] on by default
/Users/kostaskarachalios/Code/Learning/Rust/for Rubyists/fizzbuzz.rs:15         let mut answer =
                                                                                    ^~~~~~~~~~

On the other hand, when I do the same with rustc, it only displays the file's name.

fizzbuzz.rs:15:13: 15:23 warning: variable does not need to be mutable, #[warn(unused_mut)] on by default
fizzbuzz.rs:15         let mut answer =
                           ^~~~~~~~~~

Enhancement request for something similar to this, but for Sublime

https://github.com/edubkendo/atom-racer

Because lifetimes.

{ "keys": ["'"], "command": "insert_snippet", "args": {"contents": "'"}, "context":
    [{ "key": "selector", "operator": "equal", "operand": "source.rust" }]
},

when I search Rust in st3's package control,it just return Sublimelinter-contrib-rustc, no Rust, why?

This would make learning rust much faster.
At the moment every change i make i need to run cmd + B - Rust, then cmd + B - Run
could we have one which runs the 2 so i can just run 1 build in sublime which does both?

So we have functionality similar to go run?

Thanks

please, add letm.sublime-snippet

<snippet>
    <content><![CDATA[let mut ${1:pat} = ${2:expr};]]></content>
    <tabTrigger>letm</tabTrigger>
    <scope>source.rust</scope>
    <description>let mut … = …;</description>
</snippet>

I have no idea how to debug this further, but the plugin seems to have stopped working. I tried un-installing and re-installing but no joy. This happened a few days ago, before I installed the most recent Sublime update, no change after updating.

Raw strings, such as r##"This is a "raw" string"##, are not highlighted properly.

Looks like if a project contains both src/main.rs and src/lib.rs, post-save error highlight doesn't work. If I run the cargo rustc command manually it just fails with the following error.

$ cargo rustc -- -Zno-trans -Zunstable-options --error-format=json
error: extra arguments to rustc can only be passed to one target, consider filtering
the package by passing e.g. --lib or --bin NAME to specify a single target

I have to add either --lib or --bin for the rustc command to work.

$ cargo rustc --lib -- -Zno-trans -Zunstable-options --error-format=json # works
$ cargo rustc --bin [BIN-NAME] -- -Zno-trans -Zunstable-options --error-format=json #works

Also setting RUSTFLAGS with "cargo build" seems to work -- should the plugin switch to it??

$ RUSTFLAGS="--error-format=json" cargo build # this also seems to work

The last line of doc has nothing after ///.

If I added something after that, such as a blank space: ///, or a blank line, the next line will not be treated as doc/comment.