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

Outlining Errors in Ruby #1445

Closed
jarednorman opened this issue Apr 30, 2015 · 9 comments
Closed

Outlining Errors in Ruby #1445

jarednorman opened this issue Apr 30, 2015 · 9 comments

Comments

@jarednorman
Copy link

With the syntax-checking and ruby layers enabled I'm seeing errors outlined regardless of whether I toggle flycheck off. Is this a bug, or am I mistaken about what's providing this feature?

@swaroopch
Copy link
Contributor

Can you please provide steps to reproduce and/or screenshots?

@jarednorman
Copy link
Author

Enable ruby and syntax-checking layers. If I toggle flycheck off the indicators in the gutter disappear but the red borders on the problems remain.

flycheckenabled

@tuhdo
Copy link
Contributor

tuhdo commented Apr 30, 2015

@jarednorman That red border is trailing whitespace. If you add a character, it will fade away because it's not trailing anymore. You will see such red region when you add trailing whitespace at the end as well.

@jarednorman
Copy link
Author

I realize this; I meant the borders around the rubocop offenses.

@syl20bnr
Copy link
Owner

@jarednorman Do you have some screenshot with flycheck disabled ?

@jarednorman
Copy link
Author

I could go grab one but it looks exactly the same except without the circular indicators in the margin.

@syl20bnr
Copy link
Owner

Ok, I guess the underline under the args and end should be gone too.
Seems that there is already a checker running, so we could disable flycheck or keep flycheck and disable the other one (like in Haskell).

@robbyoconnor
Copy link
Contributor

This is not an issue anymore and/or has been fixed.

@StreakyCobra
Copy link
Contributor

I also can't reproduce this one, it has probably been solved in the meantime. @jarednorman In any case, feel free to reopen this one if its not the case, or open a new one if you encounter any other issue ☺️

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

No branches or pull requests

6 participants