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

goto error #22

Open
nadako opened this issue Mar 19, 2015 · 5 comments
Open

goto error #22

nadako opened this issue Mar 19, 2015 · 5 comments

Comments

@nadako
Copy link

nadako commented Mar 19, 2015

when something goes wrong, it's nice that we have those red messages with compiler errors, but I'd like to be able to click on them (or just press F4/Shift-F4 to cycle between them like in ST) to jump at error position. that is very useful!

I'm not sure how hard is it to implement on Atom, but for ST it's a builtin feature of build systems, see
https://github.com/clemos/haxe-sublime-bundle/blob/master/Support/Hxml.sublime-build#L3

@ruby0x1 ruby0x1 added this to the 0.7.0 milestone Mar 19, 2015
@ruby0x1
Copy link
Member

ruby0x1 commented Mar 19, 2015

For the linting errors, there is a small red dot on the bottom right hand side that you can click to jump to the errors.

For the build results window this is pending, but will be added.

@nadako
Copy link
Author

nadako commented Mar 19, 2015

@underscorediscovery oh I didn't notice that red dot! thanks. is there some way to keybind that?

@ruby0x1
Copy link
Member

ruby0x1 commented Mar 19, 2015

You'll probably check at https://atom.io/packages/linter somewhere, as it just uses that directly atm

@ruby0x1
Copy link
Member

ruby0x1 commented Mar 19, 2015

Actually, if you check commands:

screenshot 2015-03-19 16 54 19

In atom command speak that would be linter:next-message and you could bind that in your keymap

@nadako
Copy link
Author

nadako commented Mar 19, 2015

thanks! i'll do that.

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

2 participants