From pedjany@fastmail.fm Sat Jun 14 23:25:04 2008
From: Pedja <pedjany@fastmail.fm>
To: textmate@lists.macromates.com
Subject: [TxMt] Setting up syntax highlighting for python scripts embedded	in
 xml files
Date: Sat, 14 Jun 2008 16:25:03 -0700
Message-ID: <1213485903.10344.1258488825@webmail.messagingengine.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6683918977451858674=="

--===============6683918977451858674==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable


Hi,

The project I am currently working on requires me to write xml
configuration files for a custom application for experience sampling.
The files contain embedded python scripts, contained in the following
regions:

<script event=3D"OnLoad">
  <![CDATA[
python script
  ]]>
</script>

I know that TextMate is able to deal with embedded regions that have a
different language deffinition than the main file (like php and
javascript sections in HTML) so I was trying to set this up for XML so I
can have proper syntax highlighting for python. So far, though, I have
not had any luck with this. I tried adding the following in the xml
language definition, both right after the section for embedded java and,
when that didn't work, right after the section for CDATA comments, but
it doesn't seem to work:

{ name =3D 'source.python.embedded.xml';
			begin =3D '<script.*?}>\s*?<!\[CDATA\[';
			end =3D ']]>\s*?<script/>';
			beginCaptures =3D { 0 =3D { name =3D 'punctuation.section.embedded.begin.x=
ml'; }; };
			endCaptures =3D { 0 =3D { name =3D 'punctuation.section.embedded.end.xml';=
 }; };
			patterns =3D ( { include =3D 'source.python'; } );
},

This was based on the example for embedded java, but obviously I either
didn't understand what the java example does, or I didn't specify the
begin and end strings correctly. I also suspect that since there is
already a definition for CDATA comments, this needs to be in a specific
place to override that definition.=20

Any help with getting this to work would be greatly appreciated. The
scripts can be quite long, so having proper syntax highlighting would
make things much easier.=20

Thanks so much,
Pedja

--=20
http://www.fastmail.fm - Faster than the air-speed velocity of an
                          unladen european swallow


--===============6683918977451858674==--


From mailinglist@textmate.org Mon Jun 16 04:30:03 2008
From: Allan Odgaard <mailinglist@textmate.org>
To: textmate@lists.macromates.com
Subject: [TxMt] Re: Setting up syntax highlighting for python scripts	embedded
 in xml files
Date: Mon, 16 Jun 2008 06:30:01 +0200
Message-ID: <20AE5937-649D-4DE1-A592-C0DA2F5EFF5F@textmate.org>
In-Reply-To: <1213485903.10344.1258488825@webmail.messagingengine.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8632934195324055112=="

--===============8632934195324055112==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On 15 Jun 2008, at 01:25, Pedja wrote:

> [...] I was trying to set this up for XML so I can have proper  
> syntax highlighting for python. So far, though, I have not had any  
> luck with this. I tried adding the following in the xml language  
> definition, both right after the section for embedded java and, when  
> that didn't work, right after the section for CDATA comments, but it  
> doesn't seem to work:

Adding _after_ the more general rule e.g. for CDATA, when you match  
CDATA, is not going to work. It is the first rule in the grammar which  
matches a construct, which wins.

> { name = 'source.python.embedded.xml';
> 			begin = '<script.*?}>\s*?<!\[CDATA\[';
> 			end = ']]>\s*?<script/>';
> 			beginCaptures = { 0 = { name =  
> 'punctuation.section.embedded.begin.xml'; }; };
> 			endCaptures = { 0 = { name =  
> 'punctuation.section.embedded.end.xml'; }; };
> 			patterns = ( { include = 'source.python'; } );
> },

The patterns are single-line matches. Your script + CDATA is split  
over two lines, so you will have to change strategy to match this,  
i.e. write an outer rule to match <script> with an inner rule to match  
CDATA (if necessary).


--===============8632934195324055112==--