Currently, completion of module names relies on generic text completion by Sublime Text. Syntax rules do highlight module names in module and options regions, and that naturally gets indexed into symbols list, but it requires opening individual files or kdesrc-build project directory as a whole to get indexed at least those few named which are defined there. Most data for kdesrc-build is coming from sysadmin-metadata repository, stored in files with special custom format. If we could parse those files, we could provide better completions for all available module and module-set names. For options region the two lists should be just concatenated into one, because it allows both.
Goto Definition command should take to the module or module-set block in the config itself, one of its included configs, or to a metadata file.
Currently, completion of module names relies on generic text completion by Sublime Text. Syntax rules do highlight module names in
moduleandoptionsregions, and that naturally gets indexed into symbols list, but it requires opening individual files or kdesrc-build project directory as a whole to get indexed at least those few named which are defined there. Most data for kdesrc-build is coming from sysadmin-metadata repository, stored in files with special custom format. If we could parse those files, we could provide better completions for all available module and module-set names. For options region the two lists should be just concatenated into one, because it allows both.Goto Definition command should take to the module or module-set block in the config itself, one of its included configs, or to a metadata file.