Environment of shell commands

[callumenator]

It took me some time to figure out what was going on here, so just posting this in case it's helpful or worth mentioning somewhere in the docs.

I was trying to work out why the following wouldn't inject any keys:

# Config
Meta{K} >> $(keymapperctl --type "HELLO")

I'm on a mac M3, and the homebrew install ended up putting this binary here:

which keymapperctl
/opt/homebrew/bin/keymapperctl

But the shell commands are run with a different environment:

# Config
Meta{K} >> $(printenv > $LOG_FILE)

cat LOG_FILE
[snip]
PATH=/usr/bin:/bin:/usr/sbin:/sbin
PWD=/
[snip]

So keymapperctl was not being found. I work around this atm by just hardcoding the full path:

# Config
KEYMAPPER_BIN = "/opt/homebrew/bin/keymapperctl"
type = $($KEYMAPPER_BIN --type "$0")
...

[houmain]

Thanks for reporting! I think launchd should launch keymapper from the installation directory.
Inserting this here will likely work (I still need to test it on MacOS):

<key>WorkingDirectory</key>
<string>${basepath}</string>

[callumenator]

I tested this, and it requires giving a relative path to the binary, e.g. this now works

# Config
KEYMAPPER_BIN = "./keymapperctl"

I had a play with adding a this to the plist:

<key>EnvironmentVariables</key>
<dict>
    <key>PATH</key>
    <string>${basepath};$PATH</string>
</dict>

And this seemed to work for me - it looks like it sets path to my normal user path plus the keymapper dir, which means i can run keymapperctl (and some other utils) without specifying a path.
(I don't know what I'm doing tho, first time I've tinkered with a launchd config)

[houmain]

Thanks, the solution with the PATH variable is even better, which I added now.