@vaxry , dude, thank you for your work, despite the regular breaking changes and all that. That is a very cool project, and man, I just describe my use case and how I configured stuff to accomplish it, and boom, a few months later monocle has spawned ! Man, you love your project don’t you ?
I see your direction getting out of hyprlang and embracing lua, great move !
That’s the spirit, and I’ll put my money where my mouth is right now.
way off topic contructive criticism
Now I have been struggling a bit when reading the new docs, for example on the Dispatchers page, let’s take the exec_cmd({ cmd, rules? }), one might guess that the correct usage is
hl.bind(
"SUPER + T",
hl.dsp.exec_cmd({
cmd = 'some -command "and stuff"'
}),
)
but it could be written
hl.bind(
"SUPER + T",
hl.dsp.exec_cmd{
cmd = 'some -command "and stuff"'
}
)
and when seeing the example config in the repo, we see it written :
hl.bind("SUPER + T", hl.dsp.exec_cmd('some -command "and stuff"'))
plus the ? next to some parameters in the docs only makes the most sens to people used to regular expressions…
There is still some work to do so that just reading the docs, a newcomer can write a configuration file entirely, and that goes with explaining some basics of lua.
That’s just my two cents.
I’ve dabbled too few times with lua to be super confortable with its perticularities that are not so common in other programming languages… and not having it well explained just like the docs for hyprlang were, makes the process feeling a bit haphazard.
Well, that part wasn’t intended ! Anyhow, keep up the good work ! (and I hope we soon reach a stabilization of configurations) 
Now that may look more like a DM or something, but guys if you wish to join me thanking the dude, by all means 
