By having an $ATOM_HOME-dependent part in the socket name, Atom
instances that have different homes will run in independent processes.
Fixes the current behaviour where starting Atom with a new $ATOM_HOME
"opens" an Atom window with settings and packages from the original
$ATOM_HOME. Useful for IDEs.
By having an $ATOM_HOME-dependent part in the socket name, Atom
instances that have different homes will run in independent processes.
Fixes the current behaviour where starting Atom with a new $ATOM_HOME
"opens" an Atom window with settings and packages from the original
$ATOM_HOME. Useful for IDEs.
Some Atom extensions (like Nuclide) have functionality that can only be
triggered by open-url events, which only work on Mac OS. With this
change, `atom://` URLs can be passed on the command-line, and they will
opened with the normal openUrl method on all platforms.
This change doesn't set Atom up as the default handler for atom:// urls.
That will require some platform-specific changes.
I think this slipped through during the refactoring performed in
dc32018. With this commit we are fixing the regression and adding a new
main process regression test to exercise this behavior.
Electron allows us to pass an "accelerator" property for each menu item, which
is renders to the right of the menu item. We were already adding these for the
application level menus.
This pull request adds the accelerator property to regular context menu items,
which should make it easier for people to discover/recall key mappings for
actions which they usually take via a context menu.
Changed "Close" to "Force Close" because "Close" might imply closing the Alert/Dialog instead of the editor, whereas "Force Close" better describes the action that button will take.
