[Feature request] Context depending on environment variable

[taffit]

Hello, and thank you for this wonderful software, first and foremost.

This feature request is about contexts. IMHO it would be extremely helpful if you could define a context depending on environment variables as well. This way you could e. g. define different shortcuts or paths depending on the machine you are working on.

E. g.:

[environment = "hostname=workPC"]
run_script = $("C;\Path\to\the\executable\executable.exe")

[environment = "hostname=atHome"]
run_script = $("C:\MyOwnPathAtHome\path\to\the\executable.exe")

Would that be possible? Or is there another way to define the context at least for different working PCs that I'm missing without having to add different config files?

Thank you again and best regards,
David

[houmain]

Good idea, I will think about it.

Or is there another way to define the context at least for different working PCs that I'm missing

Another way is to include a file containing machine specific mappings. e.g:

@include-optional "$HOME/.keymapper.conf"

[ristomatti]

Third option could be device specific mappings if the two PC's do not happen to have the exact same keyboard.

[taffit]

I've solved it using a local.conf-include for now (resolving environment variables didn't work on Windows, though). Having a context defined based on an environment variable would be easier, IMO.
The device specific mapping would probably also work, however then you need the interception-library installed.
Thank you for the possible workarounds, though!

[houmain]

Thanks for requesting. This is available now in 5.4.0.

[taffit]

Thank you! Works like a charm! But with a little glitch: The environment variable must exist, or you will get an Identifier expected error when saving your configuration. This makes it a little bit more complicated, e. g. the hostname is HOSTNAME on Linux/WSL, but COMPUTERNAME on Windows.
Could you slightly modify it that, when an environment variable doesn't exist, the context is not active, but no error is shown?

Thank you nonetheless, it helps already a lot.

[houmain]

Thanks, this should be fixed now.

[taffit]

Works like a charm. Thank you for the implementation as well the quick fix!
This opens up a lot of possibilities ...