Skip to content
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

Using the explorer command always prompts failure #550

Closed
LanYangYang-114 opened this issue Jul 30, 2024 · 2 comments
Closed

Using the explorer command always prompts failure #550

LanYangYang-114 opened this issue Jul 30, 2024 · 2 comments
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@LanYangYang-114
Copy link

Short Summary

If the explorer command is used in the Command input box, it will prompt failure regardless of whether it is successful or not

Steps to Reproduce the Issue

  1. Open the default 'Home' item
  2. A failed prompt appeared, but in reality, it was opened

Kando Version

v1.2.0

Installation Method

Via a portable zip archive downloaded from a release on GitHub

Desktop Environment

Windows

Environment Version

Windows 11

Additional Information

PixPin_2024-07-31_03-46-34

@LanYangYang-114 LanYangYang-114 added the bug Something isn't working label Jul 30, 2024
@Ka1zza
Copy link
Contributor

Ka1zza commented Jul 30, 2024

This is a possible duplicate of #450
I noticed that too and just turned notifications off for Kando. Not the best solution but meh.
Kando might need to make an execption when it comes to explorer return codes.

@Schneegans Schneegans added the duplicate This issue or pull request already exists label Jul 31, 2024
@Schneegans
Copy link
Contributor

Yeah, that's a weird Windows issue. But I think you can almost always replace an explorer command with something else. Opening this directory for instance should also work with start %USERPROFILE%. Also, you could wrap this in a Powershell command to ignore the wrong exit code: powershell -Command "Start-Process explorer.exe" 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants