Config file design and handling about swhkd HOT 9 CLOSED

If we are gonna do JSON files, maybe something like this:

{
  // Don't include / have empty list to use all keyboards
  "use_keyboards": [
    "/dev/input8"
  ]
  // All combos we should look for
  "combos": [
    {
      "keys": ["SUPER", "m"],
      "action": {
        "working_dir": "~",
        "environment_vars": [
          {
            "name": "DEBUG",
            "value": "1"
          }
        ]
        "command": "mousepad"
      }
    }
  ]
}

(Obviously, this is trying to show off every setting you can use)

from swhkd.

Have you seen the config file of sxhkd? I plan to clone it exactly as is.

from swhkd.

That's probably a better idea :)

from swhkd.

I think making the config file of sxhkd and swhkd cross compatible will be the better idea rather than using something like TOML or JSON

mod edit:
#8 (comment)

from swhkd.

@angelofallars Hi angelo, you can go ahead and make a config-devel branch for your work.

Please do send a PR if possible and mark it as a draft if you do 🥰

from swhkd.

Will do!

from swhkd.

https://github.com/baskerville/sxhkd/blob/master/src/parse.c I believe this can help you @angelofallars

from swhkd.

any updates on this?

from swhkd.

I finally added a basic config parser: see commit on config 252ce9f . I also wrote some unit tests to test the config parser, as it was the only way to test it. It is still not complete, however.

As an example, here's a config file that "works":

r
    alacritty

w
    kitty

t
    /bin/firefox

TODO:

• Add more supported key presses (alphabetical, numerical, insert, home, delete, end, super, etc)
• Add chained keybindings (super + g, shift + 1, shift + ctrl + o)
• Add error handling for config errors (example: keybinding without command, invalid/unrecognizable keybind combination)

from swhkd.