From: Brian C. <B.C...@po...> - 2004-05-16 21:34:25
|
On Sun, May 16, 2004 at 03:23:43PM -0400, ja...@av... wrote: > This and the above should now be fixed in the latest CVS version. Can do a > "cvs update ." in the joe-current directory and try it? You have to begin > with "aclocal" etc. Will do. > >It still does not work well though; it appears to be the same as with > >joe-3.0. Using the 'test.xml' which I posted before, I get cyan for strings: > > Oh, I had forgotten that the released joe 3.0 had the xml highlighter. It didn't - I just pulled the xml.jsf from CVS and tried it with 3.0 before trying it with the CVS version of the binary. > Ok, I looked at it. > > The problem is that you can't have options after strings- you really need > recolor and noeat to do what you want. Thanks. Actually I realised that shortly after posting, and tried introducing an intermediate state to get around it: :decl Decl * decl strings "!--" comment_fix <<<<<<<< "![CDATA[" cdata_fix <<<<<<<< done "<" decl_nest ">" start :cdata_fix CdataStart <<<<<< * cdata_start noeat recolor=-9 <<<<<< :cdata_start CdataStart * cdata noeat ...etc :comment_fix CommentStart <<<<<< * comment_start noeat recolor=-4 <<<<<< :comment_start CommentStart * comment noeat ...etc The full .jsf is attached if you'd like to try it. What I now get is an off-by-one error, for example <!--testing--> < is cyan (wrong) !-- is green underlined (ok) t is green underlined (wrong) esting is green (ok) It looks like "recolor" works from the position *after* the matched character, even if "noeat" was specified. Is that intentional? If so, I can't see how to work around this. > It's a good idea, so I will change > the highlighter code to allow for options. It should be ready later today > or tomorrow: I'll send mail to you again. Excellent, thanks. Best wishes, Brian. |