[ jEdit-devel ] [ jedit-Bugs-1235126 ] c multiline strings not correctly highlighted

[SourceForge.net <no...@so...>]

Bugs item #1235126, was opened at 2005-07-09 03:44
Message generated for change (Comment added) made by vanza
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1235126&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: text area and syntax packages
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: c multiline strings not correctly highlighted

Initial Comment:
For the c syntax multiline line strings i.e. strings
separated with \ like " hello\
world! "  are not correctly colored.

----------------------------------------------------------------------

>Comment By: Marcelo Vanzin (vanza)
Date: 2006-04-21 00:21

Message:
Logged In: YES 
user_id=75113

Removing the "NO_LINE_BREAK" attribute will make it
highlight the escaped multi-line string just fine, but it
will also highlight non-escaped multi-line strings which are
illegal.

I actually played with several different ways of doing it
and couldn't find one that highlighted the valid strings but
not the invalid ones... but again, vi doesn't flag the
invalid string either, so maybe we should just go with the
easy approach.

----------------------------------------------------------------------

Comment By: Jon (infinitejobu)
Date: 2006-04-20 23:33

Message:
Logged In: YES 
user_id=1484536

There is a simple workaround for this.  In the modes
directory there is a file called c.xml.  This file defines
the syntax highlighting rules for jEdit.  The rule for
string literal highlighting begins on line 49 in the current
cvs version 4.3pre4.  Here is the rule as provided:

<SPAN TYPE="LITERAL1" NO_LINE_BREAK="TRUE">
  <BEGIN>"</BEGIN>
  <END>"</END>
</SPAN>

When I remove the NO_LINE_BREAK="TRUE" The syntax
highlighting is returned to it's normal behavior.  There may
be something wrong with the NO_LINE_BREAK="TRUE" in the
syntax highlighting engine.  I have not seen any adverse
conditions arising from the removal of NO_LINE_BREAK="TRUE".
 Then again I don't really know exactly what it does.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1235126&group_id=588