This pull request tweaks the configuration of the VSCode extension and MagpieServer to make analysis trigger on .h and .i files.
MagpieBridge appears to contain a hard-coded list of associations between file extensions and languages, so some subclassing trickery is required to make the necessary changes.
PS: @sim642 mentioned that he vaguely recalls analysis-on-save working for .h and .i files sometime in the past. Is it possible that this somehow worked in the past and .h and .i files not triggering analysis is actually a regression?
This pull request tweaks the configuration of the VSCode extension and MagpieServer to make analysis trigger on .h and .i files.
MagpieBridge appears to contain a hard-coded list of associations between file extensions and languages, so some subclassing trickery is required to make the necessary changes.
PS: @sim642 mentioned that he vaguely recalls analysis-on-save working for .h and .i files sometime in the past. Is it possible that this somehow worked in the past and .h and .i files not triggering analysis is actually a regression?
PPS: I have opened a feature request for better support for changing file extension and language mappings in MagpieBridge (https://github.com/MagpieBridge/MagpieBridge/issues/88)