It is nearly impossible to detect |proc_arg| and to distinguish it from e.g. a | b | c
as an expression - currently the proc_arg hiliter assumes that there are no spaces around
the proc_arg which is too narrow. Yesterday I encountered a buggy site effect that |i1| the
1 is hilited like a number... so I should disable this feature which is currently not enabled
by default completely.
The main features of Haml can be correctly parsed according to
http://haml-lang.com/docs/yardoc/file.HAML_REFERENCE.html.
There exist some limitations inherently comming from the limitations
of state machine based highlighters (without side effects)... this parsers
sucks with multiline comments, strings etc since the indent based grouping
can't be evaluated.
Newer Rubies (appearently 1.7 and above) do not accept floating point literals
like .5 anymore with the following error:
no .<digit> floating literal anymore; put 0 before dot
From the spec ? and ! are only allow at the _end_ of _method_ names. The current highlighter accepts ? and ! in _all_ identifiers (since they could be e.g. method calls), too.
New features are:
- TODO (and FIXME, BUG, XXX) highlight in oneline comments (bold green)
- :symbols support (red)
- proc block argument highlight for e.g. |arg,val| (yellow, disabled)
- class member highlight for e.g. @field (brown, disabled)
- additional quasi-keywords
Disabled features may be enabled by setting a color in the header.
