Option for "Open with Atom" #4695
Comments
👍 Could be very annoying for some people. |
To cite @leranus:
|
And as was pointed out, the specific code which adds and removes the "Open with Atom" item is in https://github.com/atom/atom/blob/master/src/browser/squirrel-update.coffee. |
👍 |
The same here.. New Atom user, works good so far, but the installer integrates stuff into the Windows shell WITHOUT ASKING. Not nice... This should be opt-in, definitely. One simply does not write stuff into system keys like HKEY_CLASSES_ROOT*, directory etc. without asking the user. |
Is this issue still relevant? Labeled as 'enhancement' hence nobody cares :-) Should every user modify
themself? If the option in question will not make it into Atom, maybe provide a simple script executing Update.exe with the specific flags? To quote a comment from another issue by @paulcbetts
|
Okay, I hacked something together... Remove Windows Shell integration: @echo off
C:
cd %LocalAppData%\atom\bin\
for /f "delims=" %%g in (atom.cmd) do set _atom=%%g
set _atom=%_atom:~10,9%
cd ..
cd %_atom%*
atom.exe --squirrel-uninstall This should do the trick.. It's quite an ugly hack, but the Update.exe in %LocalAppData%\atom does not work. Other ideas / suggestions welcome.. |
@Hrxn You don't have to run it on every folder, just on the latest one |
Uh, yes?! That's what I am trying to do.. The most straightforward way would have been to just use The other choice would be something along the lines of So I looked for a file where the correct path is stored, and The script works for now, that is what really matters in the end. |
Closing in favor of #5901 |
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! |
Is there an option to disable the "Open with Atom" shell entry? I can't find one, if there isn't, see this as a feature request :)
The text was updated successfully, but these errors were encountered: