Winston Liu
Winston Liu
:+1: from me on adding a `--packages` argument to apm and simply propagating that flag in settings-view rather than trying to filter out themes.
They both hit the same endpoint, but settings-view does some [extra sorting](https://github.com/atom/settings-view/blob/45ca0d560f48d36c3b3a647ebf023e30b7d03251/lib/install-panel.js#L221-L223). See #1042.
I can only reproduce this with the dev tools open. Though tests should be run through the command line, which would mean there shouldn't be a dev tools to open...
@damieng: @udnaan was referring to the _existing_ Cmd+, Settings View shortcut.
What is the output of `where apm`?
Can you make sure that `C:\Users\TAXUE\AppData\Local\atom\app-1.15.0\resources\app\apm\lib\cli.js` is non-empty? I just did `node test.js`, where `test.js` was a 0-byte file, and Node returned with no output.
It's possible.
@jsejcksn `Application: Open Safe` using the command palette (cmd-shift-p).
Ok, this is because the updates container is cleared and new package cards are initialized each time. Seems wasteful.
@Ingramz I recently changed some logic with regards to how scoped setting defaults are calculated. Can you take a look at https://github.com/atom/settings-view/pull/967 and see if that fixes this issue?