Navigation Menu

Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Option for "Open with Atom" #4695

Closed
Stanzilla opened this issue Dec 18, 2014 · 11 comments
Closed

Option for "Open with Atom" #4695

Stanzilla opened this issue Dec 18, 2014 · 11 comments

Comments

@Stanzilla
Copy link

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 :)

@carstenhag
Copy link

👍 Could be very annoying for some people.

@carstenhag
Copy link

To cite @leranus:

[There should be] a preference where it can be turned off or on entirely, or just for specific files and folders. For example, not many people will open images from Explorer with Atom.

@wyandotte
Copy link

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.

@laktak
Copy link

laktak commented Jan 30, 2015

👍

@Hrxn
Copy link

Hrxn commented Jun 26, 2015

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.

@Hrxn
Copy link

Hrxn commented Jun 30, 2015

Is this issue still relevant?

Labeled as 'enhancement' hence nobody cares :-)

Should every user modify

https://github.com/atom/atom/blob/master/src/browser/squirrel-update.coffee

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

This might be nice to have as a preference in Atom, so that folks who don't want the menus can disable them. While Atom works far better if you open folders rather than files, I also can totally see not wanting Atom on every folder's menu

@Hrxn
Copy link

Hrxn commented Jul 1, 2015

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.
Using the --uninstall switch here deletes the whole atom app dir, so we need atom.exe, it seems.

Other ideas / suggestions welcome..

@Hrxn

@anaisbetts
Copy link
Contributor

@Hrxn You don't have to run it on every folder, just on the latest one

@Hrxn
Copy link

Hrxn commented Jul 3, 2015

Uh, yes?!

That's what I am trying to do..

The most straightforward way would have been to just use cd %LocalAppData%\atom\app-* , but this has some potential for failure. I haven't tried it myself, but CMD normally just sorts by alphanumeric value, just as the TAB autocompletion, so you might end up in a situation where you want to go ...app-2.x.y but land in app-1.x.y instead.

The other choice would be something along the lines of where /r %LocalAppData%\atom atom.exe , but this doesn't really help either. You can find the correct path, but not without jumping through some ridiculous hoops. Definitely not within the scope of a basic script.

So I looked for a file where the correct path is stored, and atom.cmd in \atom\bin seems to be right. Not sure if this is true, or if it stays this way, but still better than just guessing.

The script works for now, that is what really matters in the end.

@mnquintana
Copy link
Contributor

Closing in favor of #5901

@lock
Copy link

lock bot commented Jan 18, 2019

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!

@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants