package specific setting page become not accessible from v1.4.0

[t9md]

After upgraded to v1.4.0, setting can not accessible for page which have activationCommands, I first noticed in my package, but confirmed this issue is also happen for symbols-view package.

I'm not sure this issue is for settings-view or Atom core.
But I believe all package which have activationCommands in package.json have affect this issue.

OS X 10.9.5
Atom v1.4.0

When I reverted to v1.3.3 the issue not happen, OR when I removed activationCommands section from package.json issue not happen(can access setting page via settings-view)

The setting page I'm saying is package specific setting page by clicking setting button of specific package panel.

Screen capture with symbols-view package.

When I removed activationCommands from package.json, setting page become accessible.

[kandros]

atom 1.4.0
osx 10.11.02

Not working for me too

[t9md]

@kandros What you want to say is not working for me right?
Since your screen capture not showing setting section

[kandros]

@t9md typo 😁

[maxbrunsfeld]

✨ Thanks for catching this and for the detailed report, @t9md!

[trois]

osx 10.11.2
atom 1.5.0-b1 => missing
atom 1.4.1 => missing
atom 1.3.3 => work (to avoid autoupdating, I made temporary change.
chmod 555 ~/Library/Application\ Support/com.github.atom.ShipIt ）

[50Wliu]

@trois the fix isn't in the betas (yet). At the current rate it'll be in Atom 1.7.0, but it may be cherry-picked as a hotfix.

[lierdakil]

Damn it all to hell! This issue pretty much kills all atom-haskell projects, since I use deferred activation extensively, for performance reasons, and most packages need to be configured.

[50Wliu]

Hey @lierdakil, the fix has been released in Atom 1.4.2 😄.

[lierdakil]

Thanks.
1 февр. 2016 г. 23:27 пользователь "Wliu" notifications@github.com
написал:

Hey @lierdakil https://github.com/lierdakil, the fix has been released
in Atom 1.4.2 [image: 😄].

—
Reply to this email directly or view it on GitHub
#10426 (comment).

[jonobacon]

It looks like this issue may be back. See AtomLinter/linter-pylama#33 for details.

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!