I just took a real quick stab at the cf mode, and you’re probably going to run into a few things with it. First, afae will auto close, but only if the partition type is set to MARKUP. Unless you want cftags and html tags to be the same color you won’t be able to get auto closing on cftags from the present code base.

The other thing is you can only do a regex hash char once and < is being used by the javascript regex rule. So that’ll take some tweaking to get to work.

I put adding cf on my list, it’ll be out on the next release (sometime this week if time allows). You might want to wait till then and then tweak the rules. If you’re tough though, go for it and let me know how you get on.

1) I am going to take a whack at an updated ColdFusion mode file, and will send it to you to review.

2) I /think/ I understand. I will play with it a bit and see if I can get where I want to be…

3) Hmmm. It isn’t the first tag. Create an empty HTML file. Put in a paragraph. It won’t close. Put in a table. It won’t close. Inside the table, put in a tr — that one will auto-close.

1. Ok, I’ll put the coldfusion mode back in the mix (Don’t kill me Mark, I mean you no harm ;D)

2. Not really. When a mode file is loaded, as it is loading the entity references are expanded. So &javascriptrules; becomes the contents of the file inc/javascript_rules.ixml. It’s using an XML feature called “unparsed entities”: http://www.xml.com/pub/a/98/08/xmlqna2.html . So if you want to add javascript support to a coldfusion mode file, you’d make a delegate rule within the coldfusion file and for the body of the rule you’d add &javascript_rules; (see the php.xml mode file)

3. They all should close by default. What you might be running into the small bug of “the first tag in a file wont auto close”. Otherwise, you’ve hit a new bug (if you could sent me the html file that isn’t closing tags properly, please let me know)

1. I am in an odd spot with CFEclipse right now, as there is a bug in it — logged, but not yet fixed — that causes CFEclipse to hang or freeze in specific situations on a very repeatable (and unfortunately, frequent) basis. As a result, I am looking for something to use in the interim — and AFAE looks promising. Hopefully, Mark Drew will be able to get that one resolved, but in the interim I am looking for an alternative. I have spent some time in the past — not recently, though — tweaking the stock jEdit ColdFusion mode to work more like I wanted it to (e.g., delegation of CSS, JS, SQL within CF source files), so the thought of getting the AFAE mode set up in a similar way isn’t too intimidating for me. I’d be more than willing to share whatever I come up with.

2. So does AFAE just load all of the .ixml files? Or is there something there that specifically directs AFEA to load a specific file so that we can reference the rules, etc., defined there?

3. On some tags, AFAE is automagically supplying the closing tag, but not for every tag — which in most cases is cool, but I’d like to make the same thing happen on some of the tags not currently functioning in that manner and I’d like to make the same thing happen in ColdFusion mode for some of the tags. What I’m not seeing is why some do and some don’t (e.g., td vs table in an HTML file).

1) I wasn’t planning on turning on the coldfusion one since it’d make it somewhat in competition with http://cfeclipse.org , but if people want it I’ll update and turn it on.

2) Sure. Eclipse doesn’t really have a notion of delegation – at least that I could find – so in order to allow sub sections to color code correctly (for example a JS section inside an HTML file) the rules are included for each mode individually. Instead of duplicating the rules, the .ixml (include xml) files are used. For example, if you look at html.xml you’ll see an entity reference to javascriptrules which include the javascript rules into that section – same thing in rhtml and php etc. (I am working on a better way to implement this)

I hope that kind of made sense. Another place to use for reference is the xmode.dtd where you can see how they are included.

3) Not sure I understand what you mean. Look at html.ixml in the inc directory, that might clear it up.

1) Any plans to re-do the coldfusion.xml mode file, based on these updates to the mode handling?

2) Can you explain the relationships between the html.xml, inc/html.ixml, and inc/html_spans.ixml files (and the other inc/*.ixml files, for that matter) that comprise the html mode? After looking at them (and being familiar with jEdit), I don’t see anything specific that explicitly defines the delegation and/or where to file the “external” rulesets.

3) What is it that enables “tag matching” for some tags in html mode (e.g., th, td) but not others (e.g., table, p)?