/usr/share/jed/doc/txt/syntax.txt is in jed-common 1:0.99.19-4.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 | JED is now able to do simple syntax highlighting while in C, Fortran, or TeX
mode. To enable syntax highlighting, in your startup file (.jedrc, jed.rc)
set the variable `WANT_SYNTAX_HIGHLIGHT' to 1. On Unix and VMS systems, it
is also necessary to set the variable `USE_ANSI_COLORS' to a non-zero value.
To control how to do color syntax highlight highlighting, use the
`set_color' function. This function takes three parameters: the first says
what to color and the last two specify what foreground and background colors
to use. The `what' parameter can be any one of:
"operator"
"number"
"comment"
"string"
"keyword"
"delimiter"
"preprocess"
What these actually refer to is mode dependent. For C mode, they have the
following meaning:
"operator" : `+', `-', `*', `/', `?', etc.
"number" : 1.23, -3, 0x101, etc...
"comment" : /* c comment */ // c++ comment
"string" : "anything in single or double quotes"
"keyword" : c++ keywords such as `if', `while', `register', `class'
"delimiter" : Braces {}, parenthesis, commas, etc...
"preprocess" : Lines starting with `#'
Fortran mode syntax highlighting is similar to C mode.
In TeX mode only
"number" : a formula: $c^2 = a^2 + b^2$
"comment" : % This is a comment
"keyword" : Anything following a slash(e.g., \begin) and `{', `}',
`&', etc...
have meaning.
Any other object not falling in any of the above categories is not
highlighted.
In C mode, to avoid the task of parsing the buffer on every screen update,
comments must either be confined to a single line, or have the following
format:
/* This is a multi-line
* comment. Note how the lines
* following the initial one
* start with a `*' followed by a
* whitespace character
*/
That is, the second, third, and lines must start with one or more `*'
followed by at least one whitespace character. This means that
*p++ = ' ';
will not be interpreted as comment but
* p++ = ' ';
will be flagged by the editor as a comment line.
Finally, if the screen is panned to the right, syntax highlighting will
sometimes fail. This is because the highlighting is performed based
entirely upon the visible information. This is only a problem when strings
are split with the beginning off to the left of the display (not visible)
and the end lying in the visible portion of the buffer. A similar statement
holds for comments as well.
|