Skillmon

@DBX12 this is already documented, see page 4, subsection 4.1 "Basics": > The possible input separators are `/`, `=`, `*`, `+`, `,`, `;`, `:`, `-`, `>`, ` > **Example** `\menu[,]{Extras,Settings,{Units,...

@DBX12 it happens. The real reason why documentation is written is only to say "documented" when questions arise :P

One can use `fontawesome` and its `\faMousePointer` for a cursor, `\faICursor` for a text-insertion cursor, `\faHourGlass` for "waiting". `\faMousePointer\textsubscript{R}` could produce something similar to the col B row 1 symbol.

This could be possible with the `accsupp` package. The result would depend on the used PDF viewer (I tested the `accsupp` package with a few a while ago and while...

Yes, this could happen indeed. I'll have to try things, maybe I can come up with something that works well across a bunch of viewers.

I already have an idea how this could be implemented. I'd add an option to specify how empty fields should be treated. Some key with the choices: - `ignore-empty=none` parse...

@tweh proof-of-concept (the following uses `pgfkeys` but of course could be implemented with other key=value interfaces), showing that the planned implementation works (this doesn't implement `ignore-empty=all`, since many things are...

@ralessi two things (and I hope this doesn't sound unfriendly; it isn't meant unfriendly, I promise): 1. In case you haven't noticed yet, the `catoptions` requirement was removed and `menukeys`...

@ralessi no harm done. I just have to ignore the parts in this thread not about `pgfkeys` vs. `kvoptions` :)

@tweh Before making a final decision about the used key=value frontend, I'd like to port more things to LaTeX3 (you mentioned in some other thread that you intended to do...