srithon / kmonadx

A concise and expressive extension language for configuring KMonad

kmonadx's Issues

Make CLI set the exit code properly

Currently, the CLI prints out "Exit code would be ...". This was because of an issue with the exit() function terminating the program without running destructors, but this is easily solved.

Add support for contextual compile-time variables

At times, it would be nice to be able to refer to the environment of an alias or a key. One prominent example used in target_tutorial.kbdx is the &layer variable, which would resolve to the name of the layer within which an alias or key is defined. It could also be convenient to have an &key variable, which resolved to the key being mapped.

[some-layer]
[[private]]
exit-layer = (layer-rem &layer)

Integrate with CI for pre-built binaries

Now that the tool is functional, users may want to try it out without having to install cargo or the rust compiler.

Support variable interpolation in buttons

The parser currently supports all types as rvalues, but the compiler only allows buttons outside of the [configuration] table. It would be really convenient if we could define variables and use them in buttons, like so:

[aliases]
tap-hold-delay = 250

[some-layer]
[[public]]
l = (tap-hold-next-release $tap-hold-delay @leader_next lmet)

The interpolation syntax itself is yet to be decided; should it be &tap-hold-delay to disambiguate from shell variable interpolation?

Make CLI write to file rather than stdout by default

The help message says that this is the default behavior, but while debugging I set it to print to stdout.

Make CLI print help when no arguments are passed in

Currently the program just no-ops and returns

Support list lvalues in [[keys]] assignments

Sometimes, you may want to have two keys do the same thing. Currently, the best way to achieve this behavior is to abstract the functionality into an alias, and have both keys execute that alias. However, it would be cleaner if instead, we could just set the values of both keys simultaneously, like so:

{ X, Y } = 'A'

Create custom syntax highlighting rules for kbdx

Currently, the TOML syntax highlighting on GitHub is flagging all of the unquoted rvalues red, as they would not be valid TOML syntax.

This is valid syntax in kbdx, so we need to add custom rules to make sure our documents get highlighted properly.
Another issue that could come about is tap macro syntactic sugar being interpreted as comments, since they are prefixed with a hash symbol.
This is currently being masked by the red highlighting from the first issue, but after that is fixed it will likely become a problem.
Custom highlighting rules would fix both of these