mbertucci47

Defining keyvals like this only seems to come up in tikz/pgfkeys packages, in which case the cwl listing usually has a `#c` anyways. I suppose this should be a FR...

The `\setmainfont{font}[font features%keyvals]`-type commands in fontspec and unicode-math are the main places I can think of. `\pgfpagesuselayout{layout}[options%keyvals]` of pgfpages is another.

There is a cwl for svg: https://github.com/texstudio-org/texstudio/blob/127327d7b45f3d7dea6d4be8f340b030b89ec6d6/completion/svg.cwl Commands from the package should be recognized after any instance of `\usepackage{svg}`

> There're CTAN packages that each of them does only provide a single .sty or .cls file, but with a file name different from the corresponding CTAN package name. I...

It seems the option you're talking about is "Insert arguments" which does fix it - there is also an "Arguments as placeholders" option; it seems to have no effect on...

Actually from the [documentation](https://texstudio-org.github.io/configuration.html#configuring-the-autocompletion) it would seem "Arguments as placeholders" should be the option which controls the placeholder feature. But I just double checked and it's "Insert arguments" that determines...

Thanks! Right, I admit I'm a somewhat odd user in wanting keyval completion without using command completion much. I'll test the new build

As far as I can tell the behavior is the same as before, though perhaps that's what you meant by > the actual problem is the "unlosed" square bracket

> It simply counts argument types and assumes that mandatory argument is always the last Is there a reason these other argument types can't be treated the same way as...

Not a replacement for the FR but the recent [`texfindpkg`](https://ctan.org/pkg/texfindpkg) uses TXS's cwls to find packages from commands