-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Context menu is showing Hyper but trows an error when clicked #1165
Comments
To solve this until it's fixed by an update: Step 1 : Type "regedit" in start menu Step 2 : Run the registry editor Step 3 : Navigate to HKEY_CURRENT_USER\SOFTWARE\Classes\Directory\Background\shell\Hyper\command Step 4 : Right-click on "REG_SZ" entry and choose modify Step 5: Enter the Path to Hyper, like: C:\Users\username\AppData\Local\app-1.0.0\Hyper.exe Unfortunately Hyper doesn't navigate directly to the "open here" directory. This should be fixed too. |
@lednhatkhanh Hyper adds/removes the context menu entry only during install/uninstall. That's why your entry may have been broken. @kilianso I can't seem to reproduce this. Is this on Windows 10? Could you share your config? |
@kilianso opening in the current directory can be fixed by adding "%V" as an argument in the command key: You can also change the text that is displayed in the context menu by adding a value to the parent Hyper key such as "Open Hyper Here". Windows reg export:
|
@kilianso |
I just hit this also. The default reg key is getting erased on update. Perhaps something wrong with the squirrel update? @linonetwo That doesn't seem to work as the path (via %V) isn't passed to Hyper.exe from Squirrel's update.exe. I think that it should be set to the full path, then the update.exe handler should update the reg key on update. |
Somehow the command: "C:\Users<username>\AppData\Local\hyper\app-1.0.0\Hyper.exe" "%V" was not working for me. Hyper showed up but not at the correct path. So I changed it to: |
@EsSpricht's solution works for me |
Fix by #1831 |
This issue's related to this: #1133
I'm facing this issue on windows 10 when I build the app from source (latest commit, master).
But, after removing and reinstall using the .exe file downloaded from here, it started working fine.
Nodejs: 7.2.1 64 bit
Windows 10 64bit.
Note that this also happends with GritKraken (another Electron app), so I think that there should be some problems with Electron or something. Vscode's still working fine tho.
The text was updated successfully, but these errors were encountered: