Emanuele Torre

why are there quotes areound the `3`? should there be quotes there? In shell syntax, `\[con_mark="3"\]` and `\[con_mark=3\]` have the exact same meaning.

@eater that is different. `i3-msg \[con_mark="3"\]` and `i3-msg \[con_mark=3\]` are exactly the same thing, I'm not saying they behave similarly. `i3-msg` will receive `[con_mark=3]` as the argument in both cases,...

yes. you need to use the keysym name, so `ccedilla`; `sxhkd` won't understand `super + ç` or similar since `ç` is not a valid keysym name. duplicate of #249, check...

I guess what is missing is a bot that automatically generates `jq.1.prebuilt`, `parser.c`, etc after a PR is merged, but do we really wan that?

The examples are wrong; they are using unquoted expansions that will split the output by whitespace, and then `eval` will join the splits back collapsing a sequence of multiple spaces...

@nicowilliams It only makes sense that `x=(['*']='*')` doesn't glob expand to the files in your directory, the are no spaces so it is a glob in its entirety. It would...

You just need to double quote the expansion so it is not splitted and glob expanded: `eval "x=($(jq ...))"` instead of `eval x=($(jq ...))`; also note that you don't need...

Can you write `@sh` instead of `@sh` in your commit message so github does not render it as a user mention ^^

I get `jq: error (at :1): Unfinished abandoned text at EOF at line 2, column 0` in both jq 1.6, 1.7rc1, and the master branch, so this is probably windows...

Though, we run tests on the windows amd64 CI, so it is weird that the CI does not fail this assertion.