core: handle scoped keywords if flags are not allowed

[aurelien-brabant]

I was playing with Hyprlang to handle configuration for a project of mine and found out that keywords inside categories are not properly handled (they are simply being ignored).

I added tests to make sure only the correctly scoped keywords are calling the handler.

[vaxerski]

also rebase on main to fix ci

[vaxerski]

thanks!

[fufexan]

@vaxerski you forgot to merge.

[vaxerski]

no I totally didnt

[zjeffer]

After updating my whole system with paru, this config stopped working:

animations {
  enabled = true

  # Some default animations, see https://wiki.hyprland.org/Configuring/Animations/ for more
  animation = windows, 1, 1, default
  animation = windowsOut, 1, 2, default
  animation = border, 1, 5, default
  animation = borderangle, 1, 8, default
  animation = fade, 1, 3, default
  animation = workspaces, 1, 4, default
  animation = specialWorkspace, 1, 4, default, slidevert
}

I get the config error config option <animations.animation> does not exist.

Instead, I now have to do this:

animations {
  enabled = true
}
# Some default animations, see https://wiki.hyprland.org/Configuring/Animations/ for more
animation = windows, 1, 1, default
animation = windowsOut, 1, 2, default
animation = border, 1, 5, default
animation = borderangle, 1, 8, default
animation = fade, 1, 3, default
animation = workspaces, 1, 4, default
animation = specialWorkspace, 1, 4, default, slidevert

I believe this commit is responsible.

[vaxerski]

hm, right. General keywords should be unscoped. Gimme sec.

[vaxerski]

fixed and added a test case: 5df0174

if you want your keyword to only work in global scope (not in categories) prefix it with :

:globalScopeOnly
anyScope
category:onlyThisCat