Blue Shadow wrote:But, I could try and add support for a few, though which ones?
Heh, I was mostly thinking out loud and just mooting the possibility really. The need is far from pressing.
I guess the ones that have more complex syntax or, perhaps, the ones that do a few different things within them would be the higher priorities.
MAPINFO might be a good example, and it's possibly the one that has the most diverse set of things that it can be used for. Obviously, it's there for defining map parameters, but the blocks of text for clusters (enter/exit text) would be nice if they could be easily identified by colour. Then MAPINFO also supports episode definitions, the gameinfo section, EdNums for things, intermissions and more. MAPINFO can become quite complicated these days in a big project.
GLDEFS can also get complicated. It has light definitions and the allocation of lights to actors, skybox definitions, material definitions, glowing flat defintions...
I think most of the other control lump types are simpler in as much as they generally only do a couple of things. Therefore the need for them would be less pressing and more of an "it looks prettier" thing now rather than massicely helping usability. e.g. SNDINFO is mostly for defining sounds and then (optionally) defining ambient sound entries. While it would be nice to have them colour-coded, I suggest that it would be less important than for the more complicated lumps. DECALDEF is probably similar (define decals and then allocate them) as is TERRAIN (define terrains and then allocate them to flats). I guess that SNDSEQ is much the same level of complexity too.
ANIMDEFS has a few things it supports (different types of animation, switches, warps) but none of it is that complicated.
I think MODELDEF is reasonably straight forward and really only single-purpose. Perhaps LOCKDEFS is similar to that.
LANGUAGE could be made pretty, but, again, probably not needed.
MENUDEF could perhaps benefit. Although it's reasonably straight forward in concept, it can become complicated from a code perspective once various options and nested menus are defined.
SBARINFO would have been a suggestion but I it's deprecated in favour of ZScript status bars now.