Return code 5 when running hyperenable from terminal
martin-braun opened this issue · 6 comments
I added hyperenable to a path that is in my $PATH, when I launch it, it outputs nothing and the exit code is 5. I try to launch it with MSYS2's bash shell.
I also tried to supply its configuration, it doesn't work. I don't wish to install and auto start the tool, I want to launch it on demand.
Why is this not working please?
You have to install. hyperenable intercepts explorer.exe during startup. You can't intercept it after Windows is booted.
Why I have to install? I just killed explorer.exe, then I run hyperenable start -c .hyperenable.yml and restarted explorer.exe:
Blocking keybinds.
Waiting for explorer.exe
Waiting until release signal or timeout.
Unblocking keybinds.
Is this the expected result? Because the office key website still opens when I press the hyper key combination ...
Don't get me wrong, but I rather wish to have a solution that I can maintain more easily in my dot files. So that's why I try to understand how this works, so I can incorporate it in my portable setup.
I tried
# see keys.hpp for possible values
keyboard_shortcuts:
- "ctrl+alt+shift+win"I also tried a configuration with ctrl+alt+shift+win+a ... ctrl+alt+shift+win+z (all letters). I'm probably missing something crucial still. Could you please guidance me in that regard?
Yes, that's the expected result. The caveat is that there's no way to know when explorer.exe is done so you have depend on the timeout to know when to kill hyperenable.exe.
@midrare Could you please elaborate? Although I get the expected result, the hotkey is still captured from explorer.exe
These should be the steps.
- Kill
explorer.exe hyperenable.exe start- Start
explorer.exe - Wait
hyperenable.exe stop
Did you try without config argument? If it's not the config, then the other possibility I can think of is that explorer.exe is taking too long and the timeout is not long enough.
@midrare Thanks, I was missing hyperenable.exe stop:
The hotkey is still captured by explorer.exe. Same result when using the configuration.
It's ok mate, I already decided to kill explorer.exe for most of my workflow. This turned into a shtt OS. Windows 7 was the best, this is garbage. I just need to build some stuff on this OS for Windows users, so I kill explorer.exe and do everything in the shell and I'm in the process to get my configuration working with MSYS2 and then I just SSH onto Windows and still be able to use my shell tools. Backslashes for paths, they lost their mind early on anyways.
Screw M$, I refuse to waste more time with trying to get explorer.exe to behave my way, the OS is lost.