Feature request: shell command or workaround about kanata

[jtroo]

Thanks for the compliment!

I'll look into this feature.

My understanding is that wmctrl is an executable that's installed by virtual box tools. When it's executed with your example command, it deactivates virtualbox capturing your inputs and you can control the host again. Is my understanding correct?

I personally use VMware for my VMs and it uses a key combination to return to the host, so I haven't had a need to use kanata for this workflow. Does virtualbox have any way to check for a key combo to leave the VM as a temporary workaround?

Looking this up now while not on my phone; seems my understanding of wmctrl was incorrect.

[jtroo]

I've implemented something that might work for your needs. You can check out the pre-release to try it out:
https://github.com/jtroo/kanata/releases/tag/v1.0.4

Note that I've added conditional compilation for this feature since I consider it to be a bit dangerous. E.g. changing your configuration file is an attack vector for arbitrary code execution.

[13minutes-yt]

The command works. Yet In some cases as I run it in terminal after the info message the cursor goes down rapidly without any trigger from my part.
.
One time it opened my image viewer 50 times and I had to shut the terminal.

I tested the executable kanata without cmd and also the cursor is moving fast in the terminal.

[jtroo]

The downward cursor movement isn't new; I've noticed it in the past and have been trying to mitigate it for some time. The "catching only releases" message on init is one such mitigation attempt. It seems to have to do with keys being pressed (particularly enter) when the program starts up.

I haven't encountered the behaviour of it opening up any applications though. Maybe you clicked on something or changed the focus and the enter key inputs made the image viewer load up a bunch?

[jtroo]

I've added another mitigation for the key repeat issue and updated the pre-release binaries to include the mitigation.

Feel free to try them out.

[13minutes-yt]

I have been experimenting with this issue. Interestingly as I wrap it in a bash script there was no problem. That is how I used it before and that is why I could not see the problem before. I will experiment with the mitigation on different distros and will report back.
Really liking the ram usage (3 MB!!!)

[13minutes-yt]

The command works as expected but the tilda ~ does not work
ex:
(cmd rm -r ~/tmp/mytempfiles)will not work. I had to do
(cmd -r /home/13minutes/tmp/tempfiles) for it to work also $HOME doesn't work either

[jtroo]

The command works as expected but the tilda ~ does not work ex: (cmd rm -r ~/tmp/mytempfiles)will not work. I had to do (cmd -r /home/13minutes/tmp/tempfiles) for it to work also $HOME doesn't work either

Yea this is expected behaviour based on the implementation. The program is executed directly (e.g. via the execv syscall) rather than through a shell. You may be able to use ~ or $HOME using cmd bash -c "your stuff here". I'll update this in the config file comments.