From: SourceForge.net <no...@so...> - 2007-06-20 22:28:45
|
Patches item #1740618, was opened at 2007-06-21 00:28 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: daniel hahler (blueyed) Assigned to: Nobody/Anonymous (nobody) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |
From: SourceForge.net <no...@so...> - 2007-06-20 22:29:41
|
Patches item #1740618, was opened at 2007-06-21 00:28 Message generated for change (Comment added) made by blueyed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: daniel hahler (blueyed) Assigned to: Nobody/Anonymous (nobody) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- >Comment By: daniel hahler (blueyed) Date: 2007-06-21 00:29 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |
From: SourceForge.net <no...@so...> - 2007-06-21 01:02:37
|
Patches item #1740618, was opened at 2007-06-20 15:28 Message generated for change (Comment added) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None Status: Open Resolution: None >Priority: 7 Private: No Submitted By: daniel hahler (blueyed) >Assigned to: Matthieu Casanova (kpouer) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- >Comment By: Alan Ezust (ezust) Date: 2007-06-20 18:02 Message: Logged In: YES user_id=935841 Originator: NO assigning to matthieu, since I know he uses PHP a lot more than I do :-) ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-20 15:29 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |
From: SourceForge.net <no...@so...> - 2007-06-21 08:48:33
|
Patches item #1740618, was opened at 2007-06-21 00:28 Message generated for change (Comment added) made by kpouer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: daniel hahler (blueyed) Assigned to: Matthieu Casanova (kpouer) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- >Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 10:48 Message: Logged In: YES user_id=285591 Originator: NO Hi, that's not bad but there is something that I don't like when having a function call or declaration the () have the same color as the function name. Is it possible to fix that ? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2007-06-21 03:02 Message: Logged In: YES user_id=935841 Originator: NO assigning to matthieu, since I know he uses PHP a lot more than I do :-) ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 00:29 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |
From: SourceForge.net <no...@so...> - 2007-06-21 09:40:33
|
Patches item #1740618, was opened at 2007-06-21 00:28 Message generated for change (Comment added) made by kpouer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: daniel hahler (blueyed) Assigned to: Matthieu Casanova (kpouer) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- >Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 11:40 Message: Logged In: YES user_id=285591 Originator: NO And the if, while ... keywords are not keywords anymore, they are highlighted as functions ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 10:48 Message: Logged In: YES user_id=285591 Originator: NO Hi, that's not bad but there is something that I don't like when having a function call or declaration the () have the same color as the function name. Is it possible to fix that ? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2007-06-21 03:02 Message: Logged In: YES user_id=935841 Originator: NO assigning to matthieu, since I know he uses PHP a lot more than I do :-) ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 00:29 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |
From: SourceForge.net <no...@so...> - 2007-06-21 10:44:24
|
Patches item #1740618, was opened at 2007-06-21 00:28 Message generated for change (Comment added) made by blueyed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: daniel hahler (blueyed) Assigned to: Matthieu Casanova (kpouer) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- >Comment By: daniel hahler (blueyed) Date: 2007-06-21 12:44 Message: Logged In: YES user_id=663176 Originator: YES Matthieu, that's what I've said. It's the regression I've mentioned. A workaround would be to use SEQ TYPE="KEYWORDX" instead of KEYWORDX, but the drawback here is that it does not get considered for complete-word than. A solution to this might be to not only include KEYWORDX in ParserRuleSet.keywords, but add SEQ[type=KEYWORDX] there, too. Another workaround would be to duplicate everything, so you would have KEYWORDX and SEQs - but that seems stupid. What do you think? I'm attaching the same php.xml file, but with the workaround mentioned above. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 11:40 Message: Logged In: YES user_id=285591 Originator: NO And the if, while ... keywords are not keywords anymore, they are highlighted as functions ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 10:48 Message: Logged In: YES user_id=285591 Originator: NO Hi, that's not bad but there is something that I don't like when having a function call or declaration the () have the same color as the function name. Is it possible to fix that ? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2007-06-21 03:02 Message: Logged In: YES user_id=935841 Originator: NO assigning to matthieu, since I know he uses PHP a lot more than I do :-) ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 00:29 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |
From: SourceForge.net <no...@so...> - 2007-06-21 11:31:51
|
Patches item #1740618, was opened at 2007-06-21 00:28 Message generated for change (Comment added) made by blueyed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: daniel hahler (blueyed) Assigned to: Matthieu Casanova (kpouer) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- >Comment By: daniel hahler (blueyed) Date: 2007-06-21 13:31 Message: Logged In: YES user_id=663176 Originator: YES Sorry, for obvious reasons the SEQ-workaround does not work, because it does not respect "whole words". E.g. something like "infodienew()" gets really colourful. Now I've commented out the delegate to PHP_FUNCS like already suggested in http://sourceforge.net/tracker/index.php?func=detail&aid=1716134&group_id=588&atid=100588 and "ordinary" functions do not get highlighted therefor. Of course, we should find a solution for this. File Added: php.xml ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 12:44 Message: Logged In: YES user_id=663176 Originator: YES Matthieu, that's what I've said. It's the regression I've mentioned. A workaround would be to use SEQ TYPE="KEYWORDX" instead of KEYWORDX, but the drawback here is that it does not get considered for complete-word than. A solution to this might be to not only include KEYWORDX in ParserRuleSet.keywords, but add SEQ[type=KEYWORDX] there, too. Another workaround would be to duplicate everything, so you would have KEYWORDX and SEQs - but that seems stupid. What do you think? I'm attaching the same php.xml file, but with the workaround mentioned above. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 11:40 Message: Logged In: YES user_id=285591 Originator: NO And the if, while ... keywords are not keywords anymore, they are highlighted as functions ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 10:48 Message: Logged In: YES user_id=285591 Originator: NO Hi, that's not bad but there is something that I don't like when having a function call or declaration the () have the same color as the function name. Is it possible to fix that ? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2007-06-21 03:02 Message: Logged In: YES user_id=935841 Originator: NO assigning to matthieu, since I know he uses PHP a lot more than I do :-) ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 00:29 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |
From: SourceForge.net <no...@so...> - 2007-08-11 01:59:47
|
Patches item #1740618, was opened at 2007-06-21 00:28 Message generated for change (Comment added) made by blueyed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: daniel hahler (blueyed) Assigned to: Matthieu Casanova (kpouer) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- >Comment By: daniel hahler (blueyed) Date: 2007-08-11 03:59 Message: Logged In: YES user_id=663176 Originator: YES I've now worked several months with this fixed mode and think I should commit it (I have commit access). If nobody complains about it, I'll do so in a couple of days. It would be nice to have a solution for the cannot-mark-custom-functions problem, but this can get fixed later, if it needs to at all. ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 13:31 Message: Logged In: YES user_id=663176 Originator: YES Sorry, for obvious reasons the SEQ-workaround does not work, because it does not respect "whole words". E.g. something like "infodienew()" gets really colourful. Now I've commented out the delegate to PHP_FUNCS like already suggested in http://sourceforge.net/tracker/index.php?func=detail&aid=1716134&group_id=588&atid=100588 and "ordinary" functions do not get highlighted therefor. Of course, we should find a solution for this. File Added: php.xml ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 12:44 Message: Logged In: YES user_id=663176 Originator: YES Matthieu, that's what I've said. It's the regression I've mentioned. A workaround would be to use SEQ TYPE="KEYWORDX" instead of KEYWORDX, but the drawback here is that it does not get considered for complete-word than. A solution to this might be to not only include KEYWORDX in ParserRuleSet.keywords, but add SEQ[type=KEYWORDX] there, too. Another workaround would be to duplicate everything, so you would have KEYWORDX and SEQs - but that seems stupid. What do you think? I'm attaching the same php.xml file, but with the workaround mentioned above. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 11:40 Message: Logged In: YES user_id=285591 Originator: NO And the if, while ... keywords are not keywords anymore, they are highlighted as functions ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 10:48 Message: Logged In: YES user_id=285591 Originator: NO Hi, that's not bad but there is something that I don't like when having a function call or declaration the () have the same color as the function name. Is it possible to fix that ? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2007-06-21 03:02 Message: Logged In: YES user_id=935841 Originator: NO assigning to matthieu, since I know he uses PHP a lot more than I do :-) ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 00:29 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |
From: SourceForge.net <no...@so...> - 2007-08-14 10:40:10
|
Patches item #1740618, was opened at 2007-06-21 00:28 Message generated for change (Comment added) made by kpouer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: daniel hahler (blueyed) Assigned to: Matthieu Casanova (kpouer) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- >Comment By: Matthieu Casanova (kpouer) Date: 2007-08-14 12:39 Message: Logged In: YES user_id=285591 Originator: NO Hi, it seems better but there is still something that I dislike : the functions aren't highlighted (that's not very important), and most important : the parens for the class methods call are highlighted like the function name : $A->B(); B() have the same color ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-11 03:59 Message: Logged In: YES user_id=663176 Originator: YES I've now worked several months with this fixed mode and think I should commit it (I have commit access). If nobody complains about it, I'll do so in a couple of days. It would be nice to have a solution for the cannot-mark-custom-functions problem, but this can get fixed later, if it needs to at all. ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 13:31 Message: Logged In: YES user_id=663176 Originator: YES Sorry, for obvious reasons the SEQ-workaround does not work, because it does not respect "whole words". E.g. something like "infodienew()" gets really colourful. Now I've commented out the delegate to PHP_FUNCS like already suggested in http://sourceforge.net/tracker/index.php?func=detail&aid=1716134&group_id=588&atid=100588 and "ordinary" functions do not get highlighted therefor. Of course, we should find a solution for this. File Added: php.xml ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 12:44 Message: Logged In: YES user_id=663176 Originator: YES Matthieu, that's what I've said. It's the regression I've mentioned. A workaround would be to use SEQ TYPE="KEYWORDX" instead of KEYWORDX, but the drawback here is that it does not get considered for complete-word than. A solution to this might be to not only include KEYWORDX in ParserRuleSet.keywords, but add SEQ[type=KEYWORDX] there, too. Another workaround would be to duplicate everything, so you would have KEYWORDX and SEQs - but that seems stupid. What do you think? I'm attaching the same php.xml file, but with the workaround mentioned above. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 11:40 Message: Logged In: YES user_id=285591 Originator: NO And the if, while ... keywords are not keywords anymore, they are highlighted as functions ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 10:48 Message: Logged In: YES user_id=285591 Originator: NO Hi, that's not bad but there is something that I don't like when having a function call or declaration the () have the same color as the function name. Is it possible to fix that ? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2007-06-21 03:02 Message: Logged In: YES user_id=935841 Originator: NO assigning to matthieu, since I know he uses PHP a lot more than I do :-) ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 00:29 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |
From: SourceForge.net <no...@so...> - 2007-08-15 20:37:53
|
Patches item #1740618, was opened at 2007-06-21 00:28 Message generated for change (Comment added) made by blueyed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: daniel hahler (blueyed) Assigned to: Matthieu Casanova (kpouer) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- >Comment By: daniel hahler (blueyed) Date: 2007-08-15 22:37 Message: Logged In: YES user_id=663176 Originator: YES kpouer, I've now fixed the most important issue: the parens for class methods are now highlighted as functions. The other issue is fixed, too. So this should be the most sweetest php.xml ever :) Please test it and provide feedback - I've only tested it against the test file now really. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-08-14 12:39 Message: Logged In: YES user_id=285591 Originator: NO Hi, it seems better but there is still something that I dislike : the functions aren't highlighted (that's not very important), and most important : the parens for the class methods call are highlighted like the function name : $A->B(); B() have the same color ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-11 03:59 Message: Logged In: YES user_id=663176 Originator: YES I've now worked several months with this fixed mode and think I should commit it (I have commit access). If nobody complains about it, I'll do so in a couple of days. It would be nice to have a solution for the cannot-mark-custom-functions problem, but this can get fixed later, if it needs to at all. ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 13:31 Message: Logged In: YES user_id=663176 Originator: YES Sorry, for obvious reasons the SEQ-workaround does not work, because it does not respect "whole words". E.g. something like "infodienew()" gets really colourful. Now I've commented out the delegate to PHP_FUNCS like already suggested in http://sourceforge.net/tracker/index.php?func=detail&aid=1716134&group_id=588&atid=100588 and "ordinary" functions do not get highlighted therefor. Of course, we should find a solution for this. File Added: php.xml ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 12:44 Message: Logged In: YES user_id=663176 Originator: YES Matthieu, that's what I've said. It's the regression I've mentioned. A workaround would be to use SEQ TYPE="KEYWORDX" instead of KEYWORDX, but the drawback here is that it does not get considered for complete-word than. A solution to this might be to not only include KEYWORDX in ParserRuleSet.keywords, but add SEQ[type=KEYWORDX] there, too. Another workaround would be to duplicate everything, so you would have KEYWORDX and SEQs - but that seems stupid. What do you think? I'm attaching the same php.xml file, but with the workaround mentioned above. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 11:40 Message: Logged In: YES user_id=285591 Originator: NO And the if, while ... keywords are not keywords anymore, they are highlighted as functions ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 10:48 Message: Logged In: YES user_id=285591 Originator: NO Hi, that's not bad but there is something that I don't like when having a function call or declaration the () have the same color as the function name. Is it possible to fix that ? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2007-06-21 03:02 Message: Logged In: YES user_id=935841 Originator: NO assigning to matthieu, since I know he uses PHP a lot more than I do :-) ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 00:29 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |
From: SourceForge.net <no...@so...> - 2007-08-15 22:01:38
|
Patches item #1740618, was opened at 2007-06-21 00:28 Message generated for change (Comment added) made by kpouer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: daniel hahler (blueyed) Assigned to: Matthieu Casanova (kpouer) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- >Comment By: Matthieu Casanova (kpouer) Date: 2007-08-16 00:01 Message: Logged In: YES user_id=285591 Originator: NO Hi, there are still some inconsistency with the classes (the -> and :: colors in fact are different if a field or a method is accessed for example) but that's not very important and I think this version is good. Do you want to commit it ? ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-15 22:37 Message: Logged In: YES user_id=663176 Originator: YES kpouer, I've now fixed the most important issue: the parens for class methods are now highlighted as functions. The other issue is fixed, too. So this should be the most sweetest php.xml ever :) Please test it and provide feedback - I've only tested it against the test file now really. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-08-14 12:39 Message: Logged In: YES user_id=285591 Originator: NO Hi, it seems better but there is still something that I dislike : the functions aren't highlighted (that's not very important), and most important : the parens for the class methods call are highlighted like the function name : $A->B(); B() have the same color ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-11 03:59 Message: Logged In: YES user_id=663176 Originator: YES I've now worked several months with this fixed mode and think I should commit it (I have commit access). If nobody complains about it, I'll do so in a couple of days. It would be nice to have a solution for the cannot-mark-custom-functions problem, but this can get fixed later, if it needs to at all. ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 13:31 Message: Logged In: YES user_id=663176 Originator: YES Sorry, for obvious reasons the SEQ-workaround does not work, because it does not respect "whole words". E.g. something like "infodienew()" gets really colourful. Now I've commented out the delegate to PHP_FUNCS like already suggested in http://sourceforge.net/tracker/index.php?func=detail&aid=1716134&group_id=588&atid=100588 and "ordinary" functions do not get highlighted therefor. Of course, we should find a solution for this. File Added: php.xml ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 12:44 Message: Logged In: YES user_id=663176 Originator: YES Matthieu, that's what I've said. It's the regression I've mentioned. A workaround would be to use SEQ TYPE="KEYWORDX" instead of KEYWORDX, but the drawback here is that it does not get considered for complete-word than. A solution to this might be to not only include KEYWORDX in ParserRuleSet.keywords, but add SEQ[type=KEYWORDX] there, too. Another workaround would be to duplicate everything, so you would have KEYWORDX and SEQs - but that seems stupid. What do you think? I'm attaching the same php.xml file, but with the workaround mentioned above. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 11:40 Message: Logged In: YES user_id=285591 Originator: NO And the if, while ... keywords are not keywords anymore, they are highlighted as functions ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 10:48 Message: Logged In: YES user_id=285591 Originator: NO Hi, that's not bad but there is something that I don't like when having a function call or declaration the () have the same color as the function name. Is it possible to fix that ? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2007-06-21 03:02 Message: Logged In: YES user_id=935841 Originator: NO assigning to matthieu, since I know he uses PHP a lot more than I do :-) ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 00:29 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |
From: SourceForge.net <no...@so...> - 2007-08-16 10:25:24
|
Patches item #1740618, was opened at 2007-06-21 00:28 Message generated for change (Comment added) made by blueyed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: daniel hahler (blueyed) Assigned to: Matthieu Casanova (kpouer) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- >Comment By: daniel hahler (blueyed) Date: 2007-08-16 12:25 Message: Logged In: YES user_id=663176 Originator: YES Yes, I would be happy to commit it. I think I've just fixed the issue you're mentioning (the "->" gets highlighted as function and the "::" as KEYWORD4). I've also changed the default for set OBJECT_PHP to KEYWORD4, so "$A->as()::asas" looks good now. See the new php.xml file. I will commit it this evening. Thanks for your feedback! File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-08-16 00:01 Message: Logged In: YES user_id=285591 Originator: NO Hi, there are still some inconsistency with the classes (the -> and :: colors in fact are different if a field or a method is accessed for example) but that's not very important and I think this version is good. Do you want to commit it ? ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-15 22:37 Message: Logged In: YES user_id=663176 Originator: YES kpouer, I've now fixed the most important issue: the parens for class methods are now highlighted as functions. The other issue is fixed, too. So this should be the most sweetest php.xml ever :) Please test it and provide feedback - I've only tested it against the test file now really. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-08-14 12:39 Message: Logged In: YES user_id=285591 Originator: NO Hi, it seems better but there is still something that I dislike : the functions aren't highlighted (that's not very important), and most important : the parens for the class methods call are highlighted like the function name : $A->B(); B() have the same color ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-11 03:59 Message: Logged In: YES user_id=663176 Originator: YES I've now worked several months with this fixed mode and think I should commit it (I have commit access). If nobody complains about it, I'll do so in a couple of days. It would be nice to have a solution for the cannot-mark-custom-functions problem, but this can get fixed later, if it needs to at all. ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 13:31 Message: Logged In: YES user_id=663176 Originator: YES Sorry, for obvious reasons the SEQ-workaround does not work, because it does not respect "whole words". E.g. something like "infodienew()" gets really colourful. Now I've commented out the delegate to PHP_FUNCS like already suggested in http://sourceforge.net/tracker/index.php?func=detail&aid=1716134&group_id=588&atid=100588 and "ordinary" functions do not get highlighted therefor. Of course, we should find a solution for this. File Added: php.xml ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 12:44 Message: Logged In: YES user_id=663176 Originator: YES Matthieu, that's what I've said. It's the regression I've mentioned. A workaround would be to use SEQ TYPE="KEYWORDX" instead of KEYWORDX, but the drawback here is that it does not get considered for complete-word than. A solution to this might be to not only include KEYWORDX in ParserRuleSet.keywords, but add SEQ[type=KEYWORDX] there, too. Another workaround would be to duplicate everything, so you would have KEYWORDX and SEQs - but that seems stupid. What do you think? I'm attaching the same php.xml file, but with the workaround mentioned above. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 11:40 Message: Logged In: YES user_id=285591 Originator: NO And the if, while ... keywords are not keywords anymore, they are highlighted as functions ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 10:48 Message: Logged In: YES user_id=285591 Originator: NO Hi, that's not bad but there is something that I don't like when having a function call or declaration the () have the same color as the function name. Is it possible to fix that ? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2007-06-21 03:02 Message: Logged In: YES user_id=935841 Originator: NO assigning to matthieu, since I know he uses PHP a lot more than I do :-) ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 00:29 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |
From: SourceForge.net <no...@so...> - 2007-08-16 23:01:33
|
Patches item #1740618, was opened at 2007-06-21 00:28 Message generated for change (Comment added) made by blueyed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: daniel hahler (blueyed) Assigned to: Matthieu Casanova (kpouer) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- >Comment By: daniel hahler (blueyed) Date: 2007-08-17 01:01 Message: Logged In: YES user_id=663176 Originator: YES So, here's a new php.xml file again, with some more fixes and cleanup. I've even documented the use of keywords in there.. :p The test file has also been improved a lot. I think it's fine now, but want to use it tomorrow at work first and would like to get some feedback again, of course.. :) Thanks. File Added: php.xml ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-16 12:25 Message: Logged In: YES user_id=663176 Originator: YES Yes, I would be happy to commit it. I think I've just fixed the issue you're mentioning (the "->" gets highlighted as function and the "::" as KEYWORD4). I've also changed the default for set OBJECT_PHP to KEYWORD4, so "$A->as()::asas" looks good now. See the new php.xml file. I will commit it this evening. Thanks for your feedback! File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-08-16 00:01 Message: Logged In: YES user_id=285591 Originator: NO Hi, there are still some inconsistency with the classes (the -> and :: colors in fact are different if a field or a method is accessed for example) but that's not very important and I think this version is good. Do you want to commit it ? ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-15 22:37 Message: Logged In: YES user_id=663176 Originator: YES kpouer, I've now fixed the most important issue: the parens for class methods are now highlighted as functions. The other issue is fixed, too. So this should be the most sweetest php.xml ever :) Please test it and provide feedback - I've only tested it against the test file now really. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-08-14 12:39 Message: Logged In: YES user_id=285591 Originator: NO Hi, it seems better but there is still something that I dislike : the functions aren't highlighted (that's not very important), and most important : the parens for the class methods call are highlighted like the function name : $A->B(); B() have the same color ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-11 03:59 Message: Logged In: YES user_id=663176 Originator: YES I've now worked several months with this fixed mode and think I should commit it (I have commit access). If nobody complains about it, I'll do so in a couple of days. It would be nice to have a solution for the cannot-mark-custom-functions problem, but this can get fixed later, if it needs to at all. ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 13:31 Message: Logged In: YES user_id=663176 Originator: YES Sorry, for obvious reasons the SEQ-workaround does not work, because it does not respect "whole words". E.g. something like "infodienew()" gets really colourful. Now I've commented out the delegate to PHP_FUNCS like already suggested in http://sourceforge.net/tracker/index.php?func=detail&aid=1716134&group_id=588&atid=100588 and "ordinary" functions do not get highlighted therefor. Of course, we should find a solution for this. File Added: php.xml ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 12:44 Message: Logged In: YES user_id=663176 Originator: YES Matthieu, that's what I've said. It's the regression I've mentioned. A workaround would be to use SEQ TYPE="KEYWORDX" instead of KEYWORDX, but the drawback here is that it does not get considered for complete-word than. A solution to this might be to not only include KEYWORDX in ParserRuleSet.keywords, but add SEQ[type=KEYWORDX] there, too. Another workaround would be to duplicate everything, so you would have KEYWORDX and SEQs - but that seems stupid. What do you think? I'm attaching the same php.xml file, but with the workaround mentioned above. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 11:40 Message: Logged In: YES user_id=285591 Originator: NO And the if, while ... keywords are not keywords anymore, they are highlighted as functions ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 10:48 Message: Logged In: YES user_id=285591 Originator: NO Hi, that's not bad but there is something that I don't like when having a function call or declaration the () have the same color as the function name. Is it possible to fix that ? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2007-06-21 03:02 Message: Logged In: YES user_id=935841 Originator: NO assigning to matthieu, since I know he uses PHP a lot more than I do :-) ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 00:29 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |
From: SourceForge.net <no...@so...> - 2007-08-16 23:02:25
|
Patches item #1740618, was opened at 2007-06-21 00:28 Message generated for change (Comment added) made by blueyed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: daniel hahler (blueyed) Assigned to: Matthieu Casanova (kpouer) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- >Comment By: daniel hahler (blueyed) Date: 2007-08-17 01:02 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-17 01:01 Message: Logged In: YES user_id=663176 Originator: YES So, here's a new php.xml file again, with some more fixes and cleanup. I've even documented the use of keywords in there.. :p The test file has also been improved a lot. I think it's fine now, but want to use it tomorrow at work first and would like to get some feedback again, of course.. :) Thanks. File Added: php.xml ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-16 12:25 Message: Logged In: YES user_id=663176 Originator: YES Yes, I would be happy to commit it. I think I've just fixed the issue you're mentioning (the "->" gets highlighted as function and the "::" as KEYWORD4). I've also changed the default for set OBJECT_PHP to KEYWORD4, so "$A->as()::asas" looks good now. See the new php.xml file. I will commit it this evening. Thanks for your feedback! File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-08-16 00:01 Message: Logged In: YES user_id=285591 Originator: NO Hi, there are still some inconsistency with the classes (the -> and :: colors in fact are different if a field or a method is accessed for example) but that's not very important and I think this version is good. Do you want to commit it ? ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-15 22:37 Message: Logged In: YES user_id=663176 Originator: YES kpouer, I've now fixed the most important issue: the parens for class methods are now highlighted as functions. The other issue is fixed, too. So this should be the most sweetest php.xml ever :) Please test it and provide feedback - I've only tested it against the test file now really. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-08-14 12:39 Message: Logged In: YES user_id=285591 Originator: NO Hi, it seems better but there is still something that I dislike : the functions aren't highlighted (that's not very important), and most important : the parens for the class methods call are highlighted like the function name : $A->B(); B() have the same color ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-11 03:59 Message: Logged In: YES user_id=663176 Originator: YES I've now worked several months with this fixed mode and think I should commit it (I have commit access). If nobody complains about it, I'll do so in a couple of days. It would be nice to have a solution for the cannot-mark-custom-functions problem, but this can get fixed later, if it needs to at all. ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 13:31 Message: Logged In: YES user_id=663176 Originator: YES Sorry, for obvious reasons the SEQ-workaround does not work, because it does not respect "whole words". E.g. something like "infodienew()" gets really colourful. Now I've commented out the delegate to PHP_FUNCS like already suggested in http://sourceforge.net/tracker/index.php?func=detail&aid=1716134&group_id=588&atid=100588 and "ordinary" functions do not get highlighted therefor. Of course, we should find a solution for this. File Added: php.xml ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 12:44 Message: Logged In: YES user_id=663176 Originator: YES Matthieu, that's what I've said. It's the regression I've mentioned. A workaround would be to use SEQ TYPE="KEYWORDX" instead of KEYWORDX, but the drawback here is that it does not get considered for complete-word than. A solution to this might be to not only include KEYWORDX in ParserRuleSet.keywords, but add SEQ[type=KEYWORDX] there, too. Another workaround would be to duplicate everything, so you would have KEYWORDX and SEQs - but that seems stupid. What do you think? I'm attaching the same php.xml file, but with the workaround mentioned above. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 11:40 Message: Logged In: YES user_id=285591 Originator: NO And the if, while ... keywords are not keywords anymore, they are highlighted as functions ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 10:48 Message: Logged In: YES user_id=285591 Originator: NO Hi, that's not bad but there is something that I don't like when having a function call or declaration the () have the same color as the function name. Is it possible to fix that ? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2007-06-21 03:02 Message: Logged In: YES user_id=935841 Originator: NO assigning to matthieu, since I know he uses PHP a lot more than I do :-) ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 00:29 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |
From: SourceForge.net <no...@so...> - 2007-08-17 23:41:57
|
Patches item #1740618, was opened at 2007-06-21 00:28 Message generated for change (Comment added) made by blueyed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&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: None Group: None >Status: Closed >Resolution: Accepted Priority: 7 Private: No Submitted By: daniel hahler (blueyed) Assigned to: Matthieu Casanova (kpouer) Summary: Improved php.xml file Initial Comment: Please find attached a thoroughly improved php.xml mode file. I've been using this at work and home now for a long time and have tried to keep in sync with the patches to the php.xml file from jEdit SVN. Because there are a lot of changes, I will provide the new file rather than a patch. If necessary, I can put a list together of things that have been improved. There's only one regression I'm aware of currently: internal PHP functions or e.g. "empty()" do not get highlighted as KEYWORD1 anymore, but just like any function. This is caused, because now e.g. "foo ()" also gets correctly handled as a function. IIRC there has been a fix/suggestion posted in the bug tracker for this - so this could get fixed without changing jEdit's syntax parser. This mode requires jEdit 4.3pre10 (SVN trunk). I will keep this tracker item up-to-date with the latest version. To test/use it, copy it into ~/.jedit/modes/ and create/change ~/.jedit/modes/catalog to actually use it (take a look at the "catalog" file in jEdit's "modes" directory in the program folder). ---------------------------------------------------------------------- >Comment By: daniel hahler (blueyed) Date: 2007-08-18 01:41 Message: Logged In: YES user_id=663176 Originator: YES Committed in r10397. ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-17 01:02 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-17 01:01 Message: Logged In: YES user_id=663176 Originator: YES So, here's a new php.xml file again, with some more fixes and cleanup. I've even documented the use of keywords in there.. :p The test file has also been improved a lot. I think it's fine now, but want to use it tomorrow at work first and would like to get some feedback again, of course.. :) Thanks. File Added: php.xml ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-16 12:25 Message: Logged In: YES user_id=663176 Originator: YES Yes, I would be happy to commit it. I think I've just fixed the issue you're mentioning (the "->" gets highlighted as function and the "::" as KEYWORD4). I've also changed the default for set OBJECT_PHP to KEYWORD4, so "$A->as()::asas" looks good now. See the new php.xml file. I will commit it this evening. Thanks for your feedback! File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-08-16 00:01 Message: Logged In: YES user_id=285591 Originator: NO Hi, there are still some inconsistency with the classes (the -> and :: colors in fact are different if a field or a method is accessed for example) but that's not very important and I think this version is good. Do you want to commit it ? ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-15 22:37 Message: Logged In: YES user_id=663176 Originator: YES kpouer, I've now fixed the most important issue: the parens for class methods are now highlighted as functions. The other issue is fixed, too. So this should be the most sweetest php.xml ever :) Please test it and provide feedback - I've only tested it against the test file now really. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-08-14 12:39 Message: Logged In: YES user_id=285591 Originator: NO Hi, it seems better but there is still something that I dislike : the functions aren't highlighted (that's not very important), and most important : the parens for the class methods call are highlighted like the function name : $A->B(); B() have the same color ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-08-11 03:59 Message: Logged In: YES user_id=663176 Originator: YES I've now worked several months with this fixed mode and think I should commit it (I have commit access). If nobody complains about it, I'll do so in a couple of days. It would be nice to have a solution for the cannot-mark-custom-functions problem, but this can get fixed later, if it needs to at all. ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 13:31 Message: Logged In: YES user_id=663176 Originator: YES Sorry, for obvious reasons the SEQ-workaround does not work, because it does not respect "whole words". E.g. something like "infodienew()" gets really colourful. Now I've commented out the delegate to PHP_FUNCS like already suggested in http://sourceforge.net/tracker/index.php?func=detail&aid=1716134&group_id=588&atid=100588 and "ordinary" functions do not get highlighted therefor. Of course, we should find a solution for this. File Added: php.xml ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 12:44 Message: Logged In: YES user_id=663176 Originator: YES Matthieu, that's what I've said. It's the regression I've mentioned. A workaround would be to use SEQ TYPE="KEYWORDX" instead of KEYWORDX, but the drawback here is that it does not get considered for complete-word than. A solution to this might be to not only include KEYWORDX in ParserRuleSet.keywords, but add SEQ[type=KEYWORDX] there, too. Another workaround would be to duplicate everything, so you would have KEYWORDX and SEQs - but that seems stupid. What do you think? I'm attaching the same php.xml file, but with the workaround mentioned above. File Added: php.xml ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 11:40 Message: Logged In: YES user_id=285591 Originator: NO And the if, while ... keywords are not keywords anymore, they are highlighted as functions ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2007-06-21 10:48 Message: Logged In: YES user_id=285591 Originator: NO Hi, that's not bad but there is something that I don't like when having a function call or declaration the () have the same color as the function name. Is it possible to fix that ? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2007-06-21 03:02 Message: Logged In: YES user_id=935841 Originator: NO assigning to matthieu, since I know he uses PHP a lot more than I do :-) ---------------------------------------------------------------------- Comment By: daniel hahler (blueyed) Date: 2007-06-21 00:29 Message: Logged In: YES user_id=663176 Originator: YES File Added: _test_jedit_editmode.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1740618&group_id=588 |