{"action":"opened","issue":{"url":"https://api.github.com/repos/atom/atom/issues/17430","repository_url":"https://api.github.com/repos/atom/atom","labels_url":"https://api.github.com/repos/atom/atom/issues/17430/labels{/name}","comments_url":"https://api.github.com/repos/atom/atom/issues/17430/comments","events_url":"https://api.github.com/repos/atom/atom/issues/17430/events","html_url":"https://github.com/atom/atom/issues/17430","id":327727536,"number":17430,"title":"A colorful palette of breakages since update to 1.26","user":{"login":"Redsandro","id":1702193,"avatar_url":"https://avatars3.githubusercontent.com/u/1702193?v=4","gravatar_id":"","url":"https://api.github.com/users/Redsandro","html_url":"https://github.com/Redsandro","followers_url":"https://api.github.com/users/Redsandro/followers","following_url":"https://api.github.com/users/Redsandro/following{/other_user}","gists_url":"https://api.github.com/users/Redsandro/gists{/gist_id}","starred_url":"https://api.github.com/users/Redsandro/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Redsandro/subscriptions","organizations_url":"https://api.github.com/users/Redsandro/orgs","repos_url":"https://api.github.com/users/Redsandro/repos","events_url":"https://api.github.com/users/Redsandro/events{/privacy}","received_events_url":"https://api.github.com/users/Redsandro/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-30T13:19:59Z","updated_at":"2018-05-30T13:19:59Z","closed_at":null,"author_association":"NONE","body":"I've never experienced a break when updating Atom.\r\n\r\nHowever, the last two weeks everything seems broken after an update. Not just a small annoyance, but bloodboil. As if there was a major update from stable to an alpha version.\r\n\r\nThere's just too much wrong for me to open 7 tickets and fill in all the details: I'm hoping someone will recognize this sudden breakage of many functionalities, and will recognize a certain common cause for this. Surely I can't be the only one that suddenly experienced this.\r\n\r\n__Since upgrading to Atom 1.26:__\r\n\r\n* **The _Search Results_ tab no longer opens in a new panel**, and I cannot find a setting for this behavior.\r\n* **Opening a result** from the _Search Results_ tab **no longer focuses the new tab**, and I cannot find a setting for this\r\n* **Single-clicking** a search-result or a tree-view-item **no longer works**. Double-click-paradise.\r\n* `eslint` conflicts with **`atom-ide-diagnostics`** and I need to disable one (warning popup), which **is actually `atom-ide-ui`** (confusing)\r\n* Being a fan of progress, I pick the new thing (diagnostics) but **I can't get `atom-ide-diagnostics` to lint my files** (eslint), so I'm forced pick the old linter package in stead.\r\n* Now **`atom-ide-diagnostics` needs to be disabled _on every newly opened tab_ again**. The popup keeps coming back, forcing me to disable the entire `atom-ide-ui` package.\r\n* eslint now works on only the open tab. **For every new file, I need to close and re-open atom before I can see the linting errors.**\r\n\r\n```\r\nAtom    : 1.26.1\r\nElectron: 1.7.11\r\nChrome  : 58.0.3029.110\r\nNode    : 7.9.0\r\n4.13.0-32-generic Ubuntu 16.04.1 SMP\r\n```\r\n\r\nWhat I could and probably will do is remove [evvverrryyythinggg](https://www.youtube.com/watch?v=A_iAE2JIyEE), start from scratch and enable functionality one by one.\r\n\r\nHowever, I sincerely think that this is something that would have occured to many users, and I'm wondering if there's a known cause and perhaps a less drastic fix.\r\n\r\nIf not, don't dwell on it. I will waste a couple of hours setting everything up again and/or reinstalling version 1.24. In a couple of weeks I'll have forgotten about this, and promote Atom again amongst my now laughing Webstorm colleagues."}}
{"actor":{"display_login":"Redsandro"}}