An update to the 1.0 file from Carsten Eckelmann. It adds indent for yaml blocks (> |) and highlighting of quotes (" and ') and strings (!).

A couple small improvements over the old version.
- Fixed handling of primes
- Proper highlighting of namespaces

Based on the Matlab Edit Mode by Chris Rose - slightly modified.

Update:

• The mode is now compatible with 4.3pre5+.
• DOCTYPE highlighted
• highlighted
• Highlighting of multiline tags improved (but not perfect).
• Highlighting of numbers improved.
• Some other bugs fixed.

This is the most featured HTML color mode arround. It has almost all of the functionality you need when developing web content. Recognizes CSS,PHP,Javascript (delegates to the existing modes).

features (what highlights):

1. extended tag/attributes recognition
2. some error recognition
3. inline CSS (requires mode - CSS v2.2 by John Paul Taylor II [updated])
4. inline Javascript
5. PHP

limitations (to do):

1. no asp and vbs support

known bugs (hard to fix):

1. The first atribute must be preceded by space/tab, new line is not enough, the rest work ok.
2. there is small chance, but it is possible an invalid attribute to highlight as "event", it is caused of the impossibility of matching line-starts (or EOLs) in regex (due to limitations)
3. There is a bug in jedit if background for color syntax is set. That background incorrectly applies to other tokens which doesn't have a background color set. By default the "invalid" type have a background and the other types doesn't. So the mode may look like it doesnt work. To fix that, set a background to all types or remove the background of the "invalid" type.

installation:
follow the usual steps for installing a mode definition:

1. overwrite the original html.xml in jedit installation directory, or save it to .jedit/modes directory, and modify .jedit/modes/catalog to include
   <MODE NAME="html" FILE="html.xml" FILE_NAME_GLOB="*.{html,htm}" />
   
2. Install the fixed PHP mode (original) included in the package by overwriting or adding definition into the "catalog": <MODE NAME="php" FILE="php.xml" FILE_NAME_GLOB="*.{php}" />
3. You may try to use this HTML mode for php files aswell by tricking jEdit to use html.xml to highlight php. This way the html code outside <?php?> will be highlighted. To do it, instead the above definitions (1. & 2.), add the following lines in "catalog" : <MODE NAME="php" FILE="php.xml" FILE_NAME_GLOB="*.{~}" /> <MODE NAME="html" FILE="html.xml" FILE_NAME_GLOB="*.{html,htm,php}" /> (note the "*.{~}" - it must be an invalid extesnsion, because html.xml will be used for the *.php files aswell, but if we replace directly the original php.xml will not be available for delegation)
   I recommed you install the included fixed mode, but the original one should work just fine.
   WARNING:This trick may cause some misbehaviour (on theory), because aftar that step "php" files will become "html" for jedit and plugins that depend on it may cease to work. However I didnt notice any problems.
   
4. Install the CSS mode included by overwriting or adding into "catalog":
   <MODE NAME="css" FILE="css.xml" FILE_NAME_GLOB="*.{css}" />
   
5. fix your syntax colours from "general options": set a background color to all types or remove the background of the "invalid" type.
   

used colors:
markup - unknown tag
keyword1 - tag
keyword2 - attribute name, <tr>, </tr>
keyword4 - tag that MUST be included in other tag
keyword3 - deprecated tag
function - unknown attribute
literal1 - attribute value
literal2 - inline css
literal3 - inline javascript
comment1 - comment
comment2 - m$ conditional definition (IE)

Another update of the Ruby mode file, which enhances v0.2 auto-indenting by adding indenting for the following: while, for, until, loop do, module, begin, unless. It also adds highlighting of class and instance variables, which was missing from the original mode file.

Use in combination with the Ruby auto indent and insert end macro to solve most of your Ruby indenting needs!

nVidia C for graphics (Cg) is the basic programming language of the NVIDIA Cg Toolkit. This is a C-like language used for programming graphic cards.
This is based on the "cplusplus" template, but with only valid Cg keywords and all basic built-in functions and data types present.

v0.2 Contains a few more keywords.

Significantly more detailed than the previously posted ChangeLog mode. It closely mimics how Vim colors ChangeLog files.

An update of the original Ruby mode file, which adds auto-indenting which was missing from the original file. I hope it could replace the original Ruby mode file, if no one objects to it.

Correctly highlights single-character accents, most notably \", whether or not the character is in {}. v1.1 required the character to be in {}.

Edit mode for the programming language Objective Caml (http://www.ocaml.org ).

An updated version based on the javacc.xml v0.1 by Tom Wilczak. It highlightes used TOKENs better (based on a regexp), so that stuff like <MY_TOKEN> gets highlighted, but TOKEN definitions, which often include string literals, are displayed as normal. Also makes )?, )* and )+ as KEYWORD3.

Fully compatible with Cherrypy syntax. See www.cherrypy.org

The Advanced HTML Edit Mode v1 by Brad Mace contained various typos and syntactical errors. This is a fixed version with a few extra tweaks. Next thing to do is set it up so that highlighting for any quoted string in a tag is delegated to JavaScript... This mode delegates to PHP where appropriate.

This version fixes some problems pointed out by a user: notably, it now handles text in {} as well as "", and nested ""s and {}s. See web page for details.

Highlights all environments, commands, and counters from Lamport's LaTeX2e and some of amstex and other popular packages. The five principal modes (normal, math, tabbing, tabular, and picture) are distinguished, mode transitions handled, and each mode's commands highlighted separately. Approximately 970 items are covered.

Edit mode for files using RDoc markup. Useful if you are writing RDoc content for RubLog, a Ruby weblog application. Perhaps these edit rules can be incorporated into the Ruby edit mode file eventually.

In VHDL, a single apostrophe ' is used in the following case: <signal name>'event where <signal name> can be any predifined signal (its like a variable). The bug is of course that the VHD highlighter thinks this is a single quote opeing a string, thus highlighting the rest of the line.

An easy rule would be to just check for the word "event" after a single quote. Here is the required update for vhd.xml - the following should replace the single quote span:
<SPAN_REGEXP HASH_CHAR="'" NO_LINE_BREAK="TRUE" TYPE="LITERAL1">
<BEGIN>(?!'event)</BEGIN>
<END>'</END>
</SPAN_REGEXP>

Screenshot of current error

Pieter Kapsenberg

A syntax highlighting mode for the TADS (Text Adventure Design System) interactive fiction authoring system (See this for more details).