You are probably using gedit to write / edit your source code.
I figured that there are probably some ways to make this a better environment. Antonio has already shown how you can build your application from within gedit. I figured that the default syntax highlighting wasn't exactly what I wanted. (What I have been using is the C style syntax highlighting which I get by default for my .prg files once they have been saved once (and thus have a known file extension = type).
I haven't fully understood everything about this but I have started editing my c.lang file (in /usr/share/gtksourceview-2.0/language-specs) and whilst some things I have tried to do aren't working yet. I'm finding it a help.
Maybe someone knows of an xBase pption for gedit (and I can save my time) - if so please let me know.
If not maybe someone(s) want to help getting gedit so that it better suits us?
My modifications to date are:
- Code: Select all Expand view
<!-- Keywords -->
<context id="keywords" style-ref="keyword">
<keyword>CLASS</keyword>
<keyword>INIT</keyword>
<keyword>READONLY</keyword>
<keyword>PERSISTENT</keyword>
<keyword>ENDCLASS</keyword>
<keyword>FROM</keyword>
<keyword>BEGIN SEQUENCE</keyword>
<keyword>BREAK</keyword>
<keyword>RECOVER</keyword>
<keyword>ENDSEQUENCE</keyword>
<keyword>DO CASE</keyword>
<keyword>CASE</keyword>
<keyword>OTHERWISE</keyword>
<keyword>ENDCASE</keyword>
<keyword>SWITCH</keyword>
<keyword>IF</keyword>
<keyword>ELSE</keyword>
<keyword>ELSEIF</keyword>
<keyword>ENDIF</keyword>
<keyword>ENDDO</keyword>
<keyword>DO WHILE</keyword>
<keyword>FOR EACH</keyword>
<keyword>FOR</keyword>
<keyword>TO</keyword>
<keyword>STEP</keyword>
<keyword>IN</keyword>
<keyword>EXIT</keyword>
<keyword>LOOP</keyword>
<keyword>RETURN</keyword>
<keyword>LOCAL</keyword>
<keyword>MEMVAR</keyword>
<keyword>FIELD</keyword>
<keyword>MESSAGE</keyword>
<keyword>OPERATOR</keyword>
<keyword>OVERRIDE PARAMETERS</keyword>
<keyword>REQUEST</keyword>
<keyword>END</keyword>
<keyword>TRY</keyword>
<keyword>ELSEIF</keyword>
<keyword>TRY</keyword>
<keyword>THROW</keyword>
<keyword>CATCH</keyword>
<keyword>FINALLY</keyword>
<keyword>WITH OBJECT</keyword>
<keyword>REPLACE</keyword>
<keyword>WITH</keyword>
<keyword>/@</keyword>
<keyword>SAY</keyword>
<keyword>GET</keyword>
<keyword>OF</keyword>
<keyword>SIZE</keyword>
<keyword>WHEN</keyword>
<keyword>DEFINE DIALOG</keyword>
<keyword>TITLE</keyword>
</context>
<context id="types" style-ref="type">
<keyword>DATA</keyword>
<keyword>CONSTRUCTOR</keyword>
<keyword>PROCEDURE</keyword>
<keyword>METHOD</keyword>
<keyword>FUNCTION</keyword>
<keyword>self</keyword>
<keyword>nil</keyword>
</context>
<context id="storage-class" style-ref="storage-class">
<keyword>PUBLIC</keyword>
<keyword>VIRTUAL</keyword>
<keyword>PRIVATE</keyword>
<keyword>STATIC</keyword>
<keyword>EXPORTED:</keyword>
<keyword>PROTECTED:</keyword>
<keyword>HIDDEN:</keyword>
<keyword>GLOBAL</keyword>
</context>
<context id="common-defines" style-ref="common-defines">
<keyword>CRLF</keyword>
<keyword>TRUE</keyword>
<keyword>FALSE</keyword>
</context>
<!-- C99 booleans -->
<context id="boolean" style-ref="boolean">
<keyword>.T.</keyword>
<keyword>.F.</keyword>
</context>
Note that some things aren't working ( eg @, .T., .F. - probably need regular expressions somewhere? Only some keywords included in list. Assignment to the various styles probably not optimal - style choices still the original C ones. Don't want to have to overwrite C style - want to be able to pick up an xBase one and create proper file type recognition in Linux.