85     85   | `dict` | `hashtable` | complex dictionary (Excel-style) setting field. |
    86     86   
    87     87   Again, supporting base type aliases (str=string) is very advisable. But complex types (table/dict) often cause too much effort for basic plugin/config systems. There's no need to cram in support for rarely used features.
    88     88   
    89     89   
    90     90   ## Other fields
    91     91   
    92         -Other per-config attributes migh encompass
           92  +Other per-config `{…}` attributes migh encompass
    93     93   
    94     94   | `category:` | grouping config options (else inherited from plugin) |
    95     95   | `class:`       | either decoration or additional type qualifier |
    96     96   | `arg:`          | declares a commandline argument instead of global app setting |
    97     97   | `param:`   | plugin invocation argument instead of global app flag |
    98     98   
    99     99   There's some paritiy with the main plugin meta fields. Except that config entries should not have a nested config: attribute, of course^^