[cmake-developers] Documenting command signatures

Stephen Kelly steveire at gmail.com
Mon Feb 3 18:04:01 EST 2014


Matthew Woehlke wrote:
> I guess you mean that in a '..code-block:: cmake' block, kate should
> apply the CMake HL rules? (What about other languages; I guess the same
> argument would apply to e.g. C++, Python, etc?)

Kate already does that, since my recent patches to the cmake rst 
highlighting rules. Here's some html exports from kate:

 http://www.steveire.com/cmake-buildsystem.7.html
 http://www.steveire.com/cmake-developer.7.html
 http://www.steveire.com/source_group.html

I only mapped c++ and cmake highlighting between rst names and kate names 
though. 

 http://quickgit.kde.org/?p=kate.git&a=commitdiff&h=a87a68668

Mappings for other languages could be added. A more-general way of doing the 
mapping would be nice, but Milian told me such a thing does not currently 
exist in kate.

> (Or do you mean that the CMake HL also doesn't mark the previous example
> as invalid? ...which it doesn't.)

Kate does not mark the source_group signature linked above as invalid. It 
can color this invalid/valid preprocessor code with c++ highlighting error 
detection.

 http://www.steveire.com/main.html

(it underlines in kate too, but that is not exported to html. kate bug 
apparently)

It should be possible to get some rules for highlighting invalid cmake code 
into the kate cmake.xml too.

Thanks,

Steve.





More information about the cmake-developers mailing list