-
-
Notifications
You must be signed in to change notification settings - Fork 143
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
"Show in Explorer" from right clicked file explorer context menu, open Explorer on background #1088
Comments
Thanks a ton for reporting this issue! Looking into this, the way we currently open the file explorer occurs here. Which essentially boils down to: const shell = require('electron').shell;
shell.showItemInFolder(filePath); Looking into it I can find some reports of the same behavior, such as here. Which suggests that a solution would look like: const shell = require('electron').remote.shell;
shell.showItemInFolder(filePath); Although, I haven't done the testing or research to see if we would be able to do this. |
thanks to you ! |
These directions are pretty thorough, though they probably need an update. You'll want to run Make sure the |
Taking a look at the reporters GitHub I don't see the package published. Which in this case may be fine, as I feel like this is absolutely something we would want to add to core, especially seeing as it's a pretty simple change. I'll try to draft up something soon |
Thanks in advance for your bug report!
What happened?
"Show in Explorer" from right clicked file explorer context menu,
open Explorer on the background of pulsar
(the system explorer window dont receive the focus or at least do not open over the pulsar window)
Pulsar version
1.118
Which OS does this happen on?
🪟 Windows
OS details
11
Which CPU architecture are you running this on?
None
What steps are needed to reproduce this?
On the file explorer panel,
Right-click a Folder
Click on "Show in explorer"
Additional Information:
I observed this bug too in the past , on windows 10 with atom editor
The text was updated successfully, but these errors were encountered: