On Jan 10, 2:42 pm, Gil Shwartz <[email protected]> wrote: > While I did came up with this solution, there is one drawback to this > that I need to stress. Overriding the rulesDict of php_main (from > rulesDict1 to rulesDict4) means that for text/code following a closing > PHP tag (?>), e.g. HTML, the colorizer WILL still attempt to color it > as if it is PHP, unless the Leo user will put a specific @language > directive following the closing PHP tag.
I am aware of this problem and others. Here is the checkin log for rev 2649: QQQ Added disabled hack to php.py. To enable the hack, set use_php_hack to True at the start of the file. This enables some code at the very end of the file. At present, this does not seem to be satisfactory. The php test node in test.leo is not colored properly. I'm upping this change now so that Gil can play with it. QQQ I think I've put in place a framework in which you can add hacks safely. Feel free to experiment as you like. Certainly you are more aware of the coloring you would like to see for php. I'll be happy to answer questions or add support for new features if you like, but it would be great if just changing php.py would suffice. Good luck :-) Edward
-- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
