Skip to content
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

Lints are not shown anymore, not sure what is wrong #4

Closed
ollie opened this issue Aug 26, 2014 · 5 comments
Closed

Lints are not shown anymore, not sure what is wrong #4

ollie opened this issue Aug 26, 2014 · 5 comments

Comments

@ollie
Copy link

ollie commented Aug 26, 2014

Hello,

until a while back, this plugin normally worked and showed linted errors and warnings. But probably a week ago Sublime stopped showing those errors and I'm not sure why. I thought I tinkered with something so I deleted everything today and re-installed it but it appears the same.

So I turned the Tools -> SublimeLinter -> Debug Mode on again and looked in the console. I have rust installed from source and this code:

fn main() {
    let a = "c";
}

produces this output in the console (I deleted many lines that are not relevant to SublimeLinter, but I can post it all if it should help):

reloading plugin SublimeLinter-contrib-rustc.linter
SublimeLinter: rust linter loaded
reloading plugin SublimeLinter-ruby.linter
SublimeLinter: ruby linter loaded
reloading plugin SublimeLinter.commands
reloading plugin SublimeLinter.sublimelinter
SublimeLinter: debug mode: on
SublimeLinter: temp directory: /var/folders/c1/tdg9ssr96qg4kdyzqltc0vt80000gn/T/SublimeLinter3
SublimeLinter: user shell: /usr/local/bin/zsh
SublimeLinter: computed PATH using /usr/local/bin/zsh:
/usr/bin
/bin
/usr/sbin
/sbin
/usr/local/bin
/opt/X11/bin

SublimeLinter: ENV['GEM_HOME'] = 'None'
SublimeLinter: rust activated: /usr/local/bin/rustc
SublimeLinter: found existing HTML syntax, version 3
SublimeLinter: found existing Rails syntax, version 1
SublimeLinter: rust output:
/var/folders/c1/tdg9ssr96qg4kdyzqltc0vt80000gn/T/SublimeLinter3/untitledrs:2:9: 2:10 warning: unused variable: `a`, #[warn(unused_variable)] on by default
/var/folders/c1/tdg9ssr96qg4kdyzqltc0vt80000gn/T/SublimeLinter3/untitledrs:2     let a = "c";

So Rust works but nothing is shown.

If I do this in new Ruby file

a = "b"

The output is this and lints are shown:

SublimeLinter: ruby: <unsaved> ['/usr/bin/ruby', '-wc'] 
SublimeLinter: ruby output:
Syntax OK
-:1: warning: assigned but unused variable - a 

Do you have an idea why this is (not) happening?
Or do I have to go somewhere else?

Thank you,
Ollie

@oschwald
Copy link
Owner

Thanks for reporting this. I believe it should now be fixed. Please update to the latest version and let me know if it works for you.

@ollie
Copy link
Author

ollie commented Aug 27, 2014

I've upgraded everything through Package Control (showing version 1.2.2 of rustc linter) and it remains the same, lints are not shown:

fn main() {
    let a = "b";
}
SublimeLinter: rust output:
/var/folders/c1/tdg9ssr96qg4kdyzqltc0vt80000gn/T/SublimeLinter3/untitled.rs:2:9: 2:10 warning: unused variable: `a`, #[warn(unused_variable)] on by default
/var/folders/c1/tdg9ssr96qg4kdyzqltc0vt80000gn/T/SublimeLinter3/untitled.rs:2     let a = "b";

@ollie
Copy link
Author

ollie commented Aug 27, 2014

Rustc version is rustc 0.12.0-pre (f92015f71 2014-08-21 17:30:57 +0000)
and cargo is cargo 0.0.1-pre (1a275e1 2014-08-21 17:20:50 +0000) although I haven't used it yet (newbie here).

@ollie
Copy link
Author

ollie commented Aug 27, 2014

A-ha! One more update: It now works for saved files correctly, but not for untitled unsaved files. Not sure if bug or not. :)

@oschwald
Copy link
Owner

Ah, that is a separate issue and currently the expected behavior, but I think it should be fixable, at least when not using the Cargo support. I'll create an issue for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants