When you get a Window like this upon Atom.io start, and starting to report a bug, they guide you to a “start Atom in safe mode first, then try to disable all packages to sort out if it’s a package issue” and point to [WayBack] Debugging: using safe mode.
The problem here is that when you start Atom in safe mode (from the console using atom --safe) then in the preferences you cannot disable packages: clicking on the “Disable” button has absolutely no effect.
This was with atom --version
atom --version
Atom : 1.12.8
Electron: 1.3.13
Chrome : 52.0.2743.82
Node : 6.5.0
I worked around this by editing ~/.atom/config.cson as that already contained a section like this:
core:
disabledPackages: [
"nav-panel"
]
So I wrote a poor-mans little script that generated the inner portion of that block:
pushd ~/.atom && ls -1d packages/*/ | sed 's/packages\// "/g' | sed 's/\//"/g' && popd
which got me this nice list:
"atom-beautify"
"atom-html-preview"
"atom-keyboard-macros"
"atom-wrap-in-tag"
"autocomplete-xml"
"broadcast"
"close-tags"
"color-picker"
"counter"
"emmet"
"export-html"
"file-icons"
"git-plus"
"language-batch"
"language-bbcode"
"language-innosetup"
"language-pascal"
"language-plantuml"
"language-restructuredtext"
"language-routeros-script"
"linter"
"nav-panel-plus"
"nav-panel"
"omnisharp-atom"
"pandoc-convert"
"plantuml-preview"
"print-atom"
"rot13"
"rst-preview-pandoc"
"sort-lines"
"sync-settings"
"tabs-to-spaces"
"xml-formatter"
"xml-tools"
From there, I did a binary search for the offending package: broadcast so I’ve filed an issue there.
–jeroen
The Wiert Corner - irregular stream of stuff 