{"action":"opened","issue":{"url":"https://api.github.com/repos/SublimeTextIssues/Core/issues/1425","repository_url":"https://api.github.com/repos/SublimeTextIssues/Core","labels_url":"https://api.github.com/repos/SublimeTextIssues/Core/issues/1425/labels{/name}","comments_url":"https://api.github.com/repos/SublimeTextIssues/Core/issues/1425/comments","events_url":"https://api.github.com/repos/SublimeTextIssues/Core/issues/1425/events","html_url":"https://github.com/SublimeTextIssues/Core/issues/1425","id":180407642,"number":1425,"title":"Setting to move inline errors to gutter","user":{"login":"flux627","id":5218949,"avatar_url":"https://avatars.githubusercontent.com/u/5218949?v=3","gravatar_id":"","url":"https://api.github.com/users/flux627","html_url":"https://github.com/flux627","followers_url":"https://api.github.com/users/flux627/followers","following_url":"https://api.github.com/users/flux627/following{/other_user}","gists_url":"https://api.github.com/users/flux627/gists{/gist_id}","starred_url":"https://api.github.com/users/flux627/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/flux627/subscriptions","organizations_url":"https://api.github.com/users/flux627/orgs","repos_url":"https://api.github.com/users/flux627/repos","events_url":"https://api.github.com/users/flux627/events{/privacy}","received_events_url":"https://api.github.com/users/flux627/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-30T21:38:09Z","updated_at":"2016-09-30T21:38:09Z","closed_at":null,"body":"I'm currently a fan of the *idea* of inline errors, but not a fan of it's current *implementation*.\r\n\r\nProblem\r\n-\r\nCurrently, the extra space added by the inserted line puts a significant amount of extra energy needed to recognize my own code in the affected area, and forces me to re-understand what's happening in that part of the code. When debugging, this error insertion often jumps around to other places in the code, furthering my disorientation.\r\n\r\nAlso, in Python (can't speak for other languages), it currently inserts an error line in *every affected call up the stack*, so it's often not useful for quickly finding where the real error resides. If you want to clear out one of the innocent calls, then all the other errors disappear too (in another sudden, disorienting way).\r\n\r\nSolution\r\n-\r\nI propose that instead of disrupting the visibility of the code by inserting a new line, instead on the offending line we either:\r\n\r\n* Show a red dot in the gutter \r\n* Change the background color\r\n\r\nSince it might be hard to figure out what color to change the background in a universally pleasant way on all color themes, the gutter option is cleaner. In addition, in non-primary offending lines (calls up the stack), we could show a hollow red circle instead.\r\n\r\nFor the message, we can simply show it either in a hover box, or in the status bar.\r\n\r\nIn addition to the `show_errors_inline` option, we could have another `inline_errors_style` which can be one of `box`, `gutter`, or `highlight`.\r\n\r\nThoughts?"}}
{"actor":{"display_login":"flux627"}}