jedit-devel Mailing List for jEdit

Plugin Bugs item #1461915, was opened at 2006-03-31 09:50
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=565475&aid=1461915&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
Submitted By: pieroxy (pieroxy)
Assigned to: Nobody/Anonymous (nobody)
Summary: AntFarm doesn't display output when running external ant

Initial Comment:
When the options are set to "Run ant targets using an
external script/build file", one doesn't see the output
of the ant script when double clicking on a target,
because the output goes to the System Console and the
AntFarm Console is displayed. Of course, you can view
the System Console by hand, but that's tiresome. 

I fixed this bug on AntFarm-1.4 on my system by
commenting out two lines in TargetRunner (255 and 267).
These lines force the Console to display the AntFarm
console instead of the System one, hence effectively
hiding the script output since it goes to System.

I dunno if that's the right fix for the bug, but I'd
appreciate a fix for it'd be simpler whenever I
reinstall jEdit on one of my machine.

Thanks a bunch for the hard work.

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

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

Yep, I'm pretty pleased with your last version.  Other than I added + as 
an operator, the rest seems to work very nicely.

Dale


On Thu, 30 Mar 2006, Matthieu Casanova wrote:

> 2006/3/30, Dale Anson <da...@gr...>:
>>
>> Better and better!
>>
>> I added this line to my copy
>>
>>          <SEQ TYPE="OPERATOR">+</SEQ>
>>
>> with the rest of the operators, I saw a few stray +'s weren't getting
>> highlighted correctly.
>>
>> What do you think about something like this:
>>
>> <DO_ADD, ADD_REQUIRED_DIGIT> MORE:
>> {
>>     < ["0"-"9"] > : DO_ADD
>> }
>>
>> Should the angle brackets on < ["0"-"9"] > be highlighted like the angle
>> brackets on <DO_ADD, ADD_REQUIRED_DIGIT> ?  Right now, they are not.
>
>
>
> Ok but the problem is how to do that without highlighting the bracket too ?
> I'm not an expert in edit mode.
> Do you have an idea ? Or maybe I should commit now and we change that when
> somebody has an idea ?
> the rule <"blabla"> has the same problem.
>
> Is it possible that when a token is found by a SPAN if there is a delegation
> the parsing in delegation starts at the start of the found token ?
>
> And to change the subject a bit -- I've updated JavaSideKick to work with
>> javacc files, seems to be working pretty well.  Want to give it a try?
>> I'll post a copy on the community site if you're interested.
>
>
>
> Oh yes I can try
>
>
> Matthieu
>

Ah, the problem was that the kappalayout.jar somehow ended up on a
"blacklist" of plugins that do not get loaded on startup.

I think this may have happened by "deselecting" the plugin in the
plugin manager. Perhaps there is a bug in jedit's plugin mgr that does
not remove the blacklist item when I re-select it. When I can
reproduce it, I will file a bug report.


On 3/29/06, Alan Ezust <ala...@gm...> wrote:
> I've been having problems with commoncontrols not loading on jedit
> startup. I get this message every time:
> [error] ErrorListDialog$ErrorEntry:
> /home/ezust/workspace/jEdit/jars/CommonControls.jar:
> [error] ErrorListDialog$ErrorEntry: Requires JAR file
> /home/ezust/workspace/jEdit/jars/kappalayout.jar.
> [error] ErrorListDialog$ErrorEntry: This JAR file is part of this
> plugin, but it cannot be found.
> [error] ErrorListDialog$ErrorEntry: Try reinstalling this plugin.
> [error] ErrorListDialog$ErrorEntry: /home/ezust/workspace/jEdit/jars/Dock=
er.jar:
> [error] ErrorListDialog$ErrorEntry: Requires CommonControlsPlugin, but
> CommonControlsPlugin
> [error] ErrorListDialog$ErrorEntry: could not be loaded.
> [error] ErrorListDialog$ErrorEntry:
> /home/ezust/workspace/jEdit/jars/ProjectViewer.jar:
> [error] ErrorListDialog$ErrorEntry: Requires CommonControlsPlugin, but
> CommonControlsPlugin
> [error] ErrorListDialog$ErrorEntry: could not be loaded.
>
> If I go into plugin manager, and can restart the CommonControls
> plugin, then I can restart the others (proejctviewer and alll the
> others that depend on CommonControls). But it seems i have to do this
> every time I start up jedit.
>
> Why is it not finding kappalayout on startup, when it is clearly there?
>

I posted an update to JavaSideKick at:
http://community.jedit.org/?q=queue/2576

Direct link to download:
http://community.jedit.org/?q=filestore/download/2576

This versions lets JavaSideKick handle javacc files (.jj) as well as java 
files.  It does jjtree files (.jjt) also.  You'll need to have the javacc 
mode installed, and then in the plugin options for SideKick, select the 
javacc parser for the javacc mode.

Dale



On Thu, 30 Mar 2006, Matthieu Casanova wrote:

> 2006/3/30, Dale Anson <da...@gr...>:
>>
>> Better and better!
>>
>> I added this line to my copy
>>
>>          <SEQ TYPE="OPERATOR">+</SEQ>
>>
>> with the rest of the operators, I saw a few stray +'s weren't getting
>> highlighted correctly.
>>
>> What do you think about something like this:
>>
>> <DO_ADD, ADD_REQUIRED_DIGIT> MORE:
>> {
>>     < ["0"-"9"] > : DO_ADD
>> }
>>
>> Should the angle brackets on < ["0"-"9"] > be highlighted like the angle
>> brackets on <DO_ADD, ADD_REQUIRED_DIGIT> ?  Right now, they are not.
>
>
>
> Ok but the problem is how to do that without highlighting the bracket too ?
> I'm not an expert in edit mode.
> Do you have an idea ? Or maybe I should commit now and we change that when
> somebody has an idea ?
> the rule <"blabla"> has the same problem.
>
> Is it possible that when a token is found by a SPAN if there is a delegation
> the parsing in delegation starts at the start of the found token ?
>
> And to change the subject a bit -- I've updated JavaSideKick to work with
>> javacc files, seems to be working pretty well.  Want to give it a try?
>> I'll post a copy on the community site if you're interested.
>
>
>
> Oh yes I can try
>
>
> Matthieu
>

I say check it in and we'll call it good.  I'm no expert on writing edit 
modes either, so I'm sure there are tricks that I don't know about.  This 
looks pretty darn good now.  I'm thinking it won't be a particularly 
popular mode anyway, since no one has bothered to write one until now!

Dale


On Thu, 30 Mar 2006, Matthieu Casanova wrote:

> 2006/3/30, Dale Anson <da...@gr...>:
>>
>> Better and better!
>>
>> I added this line to my copy
>>
>>          <SEQ TYPE="OPERATOR">+</SEQ>
>>
>> with the rest of the operators, I saw a few stray +'s weren't getting
>> highlighted correctly.
>>
>> What do you think about something like this:
>>
>> <DO_ADD, ADD_REQUIRED_DIGIT> MORE:
>> {
>>     < ["0"-"9"] > : DO_ADD
>> }
>>
>> Should the angle brackets on < ["0"-"9"] > be highlighted like the angle
>> brackets on <DO_ADD, ADD_REQUIRED_DIGIT> ?  Right now, they are not.
>
>
>
> Ok but the problem is how to do that without highlighting the bracket too ?
> I'm not an expert in edit mode.
> Do you have an idea ? Or maybe I should commit now and we change that when
> somebody has an idea ?
> the rule <"blabla"> has the same problem.
>
> Is it possible that when a token is found by a SPAN if there is a delegation
> the parsing in delegation starts at the start of the found token ?
>
> And to change the subject a bit -- I've updated JavaSideKick to work with
>> javacc files, seems to be working pretty well.  Want to give it a try?
>> I'll post a copy on the community site if you're interested.
>
>
>
> Oh yes I can try
>
>
> Matthieu
>

2006/3/30, Dale Anson <da...@gr...>:
>
> Better and better!
>
> I added this line to my copy
>
>          <SEQ TYPE=3D"OPERATOR">+</SEQ>
>
> with the rest of the operators, I saw a few stray +'s weren't getting
> highlighted correctly.
>
> What do you think about something like this:
>
> <DO_ADD, ADD_REQUIRED_DIGIT> MORE:
> {
>     < ["0"-"9"] > : DO_ADD
> }
>
> Should the angle brackets on < ["0"-"9"] > be highlighted like the angle
> brackets on <DO_ADD, ADD_REQUIRED_DIGIT> ?  Right now, they are not.



Ok but the problem is how to do that without highlighting the bracket too ?
I'm not an expert in edit mode.
Do you have an idea ? Or maybe I should commit now and we change that when
somebody has an idea ?
the rule <"blabla"> has the same problem.

Is it possible that when a token is found by a SPAN if there is a delegatio=
n
the parsing in delegation starts at the start of the found token ?

And to change the subject a bit -- I've updated JavaSideKick to work with
> javacc files, seems to be working pretty well.  Want to give it a try?
> I'll post a copy on the community site if you're interested.



Oh yes I can try


Matthieu

Better and better!

I added this line to my copy

         <SEQ TYPE="OPERATOR">+</SEQ>

with the rest of the operators, I saw a few stray +'s weren't getting 
highlighted correctly.

What do you think about something like this:

<DO_ADD, ADD_REQUIRED_DIGIT> MORE:
{
    < ["0"-"9"] > : DO_ADD
}

Should the angle brackets on < ["0"-"9"] > be highlighted like the angle 
brackets on <DO_ADD, ADD_REQUIRED_DIGIT> ?  Right now, they are not.

And to change the subject a bit -- I've updated JavaSideKick to work with 
javacc files, seems to be working pretty well.  Want to give it a try? 
I'll post a copy on the community site if you're interested.

Thanks,

Dale


On Thu, 30 Mar 2006, Matthieu Casanova wrote:

> 2006/3/30, Dale Anson <da...@gr...>:
>>
>> Looking better!  I do see a couple of inconsistencies:
>>
>> 1. In this one,
>>    < STRING_LITERAL:
>>        "\""
>>        (   (~["\"","\\","\n","\r"])
>>          | ("\\"
>>              ( ["n","t","b","r","f","\\","'","\""]
>>              | ["0"-"7"] ( ["0"-"7"] )?
>>              | ["0"-"3"] ["0"-"7"] ["0"-"7"]
>>              )
>>            )
>>        )*
>>        "\""
>>   >
>>
>> the commas in the first row with commas are different color than the
>> commas in the second row with commas.
>>
>> 2. In this one,
>>    < INTEGER_LITERAL:
>>          <DECIMAL_LITERAL> (["l","L"])?
>>        | <HEX_LITERAL> (["l","L"])?
>>        | <OCTAL_LITERAL> (["l","L"])?
>>   >
>>
>> the question marks are different color than the question marks in #1.
>> Also, the leading < is different color than the trailing >.
>>
>> 3.  In this one,
>> void ExpressionList() :
>> {
>>      String s;
>> }
>> {
>>      {
>>          System.out.println("Please type in an expression followed by a
>> \";\" or ^D to quit:");
>>          System.out.println("");
>>      }
>>      ( s=Expression() ";"
>>      {
>>          System.out.println(s);
>>          System.out.println("");
>>          System.out.println("Please type in another expression followed by
>> a \";\" or ^D to quit:");
>>          System.out.println("");
>>      }
>>      )*
>>      <EOF>
>> }
>>
>> string highlighting missed the escaped double quote in the first
>> System.out.println, so the text following the first \" is not right.
>>
>> This is looking much better!
>
>
> Ok I think this one is good :)
>
> <?xml version="1.0"?>
> <!DOCTYPE MODE SYSTEM "xmode.dtd">
> <MODE>
>    <PROPS>
>        <PROPERTY NAME="commentStart" VALUE="/*" />
>        <PROPERTY NAME="commentEnd" VALUE="*/" />
>        <PROPERTY NAME="lineComment" VALUE="//" />
>        <PROPERTY NAME="wordBreakChars" VALUE=",+-=&lt;&gt;/?^&amp;*" />
>
>               <!-- Auto indent -->
>        <PROPERTY NAME="indentOpenBrackets" VALUE="{" />
>        <PROPERTY NAME="indentCloseBrackets" VALUE="}" />
>        <PROPERTY NAME="unalignedOpenBrackets" VALUE="(" />
>        <PROPERTY NAME="unalignedCloseBrackets" VALUE=")" />
>        <PROPERTY NAME="indentNextLine"
> VALUE="\s*(((if|while)\s*\(|else\s*|else\s+if\s*\(|for\s*\(.*\))[^{;]*)"/>
>        <PROPERTY NAME="unindentThisLine"
> VALUE="^.*(default:\s*|case.*:.*)$" />
>        <PROPERTY NAME="electricKeys" VALUE=":" />
>    </PROPS>
>    <RULES IGNORE_CASE="FALSE" ESCAPE="\">
>        <IMPORT DELEGATE="java::MAIN"/>
>  <SEQ_REGEXP HASH_CHAR="&lt;"
> TYPE="KEYWORD2">&lt;[[:space:]]*\w+([[:space:]]*[,][[:space:]]*\w+[[:space:]]*)*[[:space:]]*&gt;</SEQ_REGEXP>
>
>      <!--   <SPAN DELEGATE="DEFINITION1">
>            <BEGIN>&lt;</BEGIN>
>            <END>&gt;</END>
>            </SPAN> -->
>
>        <SPAN_REGEXP HASH_CHAR="&lt;" DELEGATE="DEFINITION1"
> TYPE="KEYWORD2">
>            <BEGIN>&lt;[[:space:]]*\w+[[:space:]]*[:]</BEGIN>
>            <END>&gt;</END>
>        </SPAN_REGEXP>
>
>
>        <!-- regular expression definitions -->
>     <!--    <SEQ_REGEXP HASH_CHAR="&lt;"
> TYPE="KEYWORD2">&lt;[[:space:]]*\w+[[:space:]]*[:]</SEQ_REGEXP> -->
>
>        <!-- regular expression label(s) -->
>
>        <!-- private regular expression labels -->
>        <SEQ_REGEXP HASH_CHAR="#" TYPE="KEYWORD2">[#]\w+[:]</SEQ_REGEXP>
>
>        <KEYWORDS>
>            <!-- javacc keywords -->
>            <KEYWORD1>EOF</KEYWORD1>
>            <KEYWORD1>IGNORE_CASE</KEYWORD1>
>            <KEYWORD1>JAVACODE</KEYWORD1>
>            <KEYWORD1>LOOKAHEAD</KEYWORD1>
>            <KEYWORD1>MORE</KEYWORD1>
>            <KEYWORD1>PARSER_BEGIN</KEYWORD1>
>            <KEYWORD1>PARSER_END</KEYWORD1>
>            <KEYWORD1>SKIP</KEYWORD1>
>            <KEYWORD1>SPECIAL_TOKEN</KEYWORD1>
>            <KEYWORD1>TOKEN</KEYWORD1>
>            <KEYWORD1>TOKEN_MGR_DECLS</KEYWORD1>
>            <KEYWORD1>options</KEYWORD1>
>
>            <!-- DEFAULT is the standard lexical state -->
>            <KEYWORD2>DEFAULT</KEYWORD2>
>        </KEYWORDS>
>
>    </RULES>
>
>     <RULES SET="DEFINITION1" DEFAULT="KEYWORD2" ESCAPE="\">
>        <SPAN TYPE="COMMENT1">
>            <BEGIN>/*</BEGIN>
>            <END>*/</END>
>        </SPAN>
>        <SPAN TYPE="LITERAL1" NO_LINE_BREAK="TRUE">
>            <BEGIN>"</BEGIN>
>            <END>"</END>
>        </SPAN>
>        <SEQ TYPE="OPERATOR">,</SEQ>
>        <SEQ TYPE="OPERATOR">-</SEQ>
>        <SEQ TYPE="OPERATOR">?</SEQ>
>        <SEQ TYPE="OPERATOR">:</SEQ>
>        <SEQ TYPE="OPERATOR">|</SEQ>
>        <SEQ TYPE="OPERATOR">[</SEQ>
>        <SEQ TYPE="OPERATOR">]</SEQ>
>        <SEQ TYPE="OPERATOR">(</SEQ>
>        <SEQ TYPE="OPERATOR">)</SEQ>
>        <SEQ TYPE="OPERATOR">*</SEQ>
>        <SEQ TYPE="OPERATOR">~</SEQ>
>        <SEQ TYPE="OPERATOR">&lt;</SEQ>
>        <SEQ TYPE="OPERATOR">&gt;</SEQ>
>
>
>    </RULES>
> </MODE>
>

2006/3/30, Dale Anson <da...@gr...>:
>
> Looking better!  I do see a couple of inconsistencies:
>
> 1. In this one,
>    < STRING_LITERAL:
>        "\""
>        (   (~["\"","\\","\n","\r"])
>          | ("\\"
>              ( ["n","t","b","r","f","\\","'","\""]
>              | ["0"-"7"] ( ["0"-"7"] )?
>              | ["0"-"3"] ["0"-"7"] ["0"-"7"]
>              )
>            )
>        )*
>        "\""
>    >
>
> the commas in the first row with commas are different color than the
> commas in the second row with commas.
>
> 2. In this one,
>    < INTEGER_LITERAL:
>          <DECIMAL_LITERAL> (["l","L"])?
>        | <HEX_LITERAL> (["l","L"])?
>        | <OCTAL_LITERAL> (["l","L"])?
>    >
>
> the question marks are different color than the question marks in #1.
> Also, the leading < is different color than the trailing >.
>
> 3.  In this one,
> void ExpressionList() :
> {
>      String s;
> }
> {
>      {
>          System.out.println("Please type in an expression followed by a
> \";\" or ^D to quit:");
>          System.out.println("");
>      }
>      ( s=3DExpression() ";"
>      {
>          System.out.println(s);
>          System.out.println("");
>          System.out.println("Please type in another expression followed b=
y
> a \";\" or ^D to quit:");
>          System.out.println("");
>      }
>      )*
>      <EOF>
> }
>
> string highlighting missed the escaped double quote in the first
> System.out.println, so the text following the first \" is not right.
>
> This is looking much better!


Ok I think this one is good :)

<?xml version=3D"1.0"?>
<!DOCTYPE MODE SYSTEM "xmode.dtd">
<MODE>
    <PROPS>
        <PROPERTY NAME=3D"commentStart" VALUE=3D"/*" />
        <PROPERTY NAME=3D"commentEnd" VALUE=3D"*/" />
        <PROPERTY NAME=3D"lineComment" VALUE=3D"//" />
        <PROPERTY NAME=3D"wordBreakChars" VALUE=3D",+-=3D&lt;&gt;/?^&amp;*"=
 />

               <!-- Auto indent -->
        <PROPERTY NAME=3D"indentOpenBrackets" VALUE=3D"{" />
        <PROPERTY NAME=3D"indentCloseBrackets" VALUE=3D"}" />
        <PROPERTY NAME=3D"unalignedOpenBrackets" VALUE=3D"(" />
        <PROPERTY NAME=3D"unalignedCloseBrackets" VALUE=3D")" />
        <PROPERTY NAME=3D"indentNextLine"
VALUE=3D"\s*(((if|while)\s*\(|else\s*|else\s+if\s*\(|for\s*\(.*\))[^{;]*)"/=
>
        <PROPERTY NAME=3D"unindentThisLine"
VALUE=3D"^.*(default:\s*|case.*:.*)$" />
        <PROPERTY NAME=3D"electricKeys" VALUE=3D":" />
    </PROPS>
    <RULES IGNORE_CASE=3D"FALSE" ESCAPE=3D"\">
        <IMPORT DELEGATE=3D"java::MAIN"/>
  <SEQ_REGEXP HASH_CHAR=3D"&lt;"
TYPE=3D"KEYWORD2">&lt;[[:space:]]*\w+([[:space:]]*[,][[:space:]]*\w+[[:spac=
e:]]*)*[[:space:]]*&gt;</SEQ_REGEXP>

      <!--   <SPAN DELEGATE=3D"DEFINITION1">
            <BEGIN>&lt;</BEGIN>
            <END>&gt;</END>
            </SPAN> -->

        <SPAN_REGEXP HASH_CHAR=3D"&lt;" DELEGATE=3D"DEFINITION1"
TYPE=3D"KEYWORD2">
            <BEGIN>&lt;[[:space:]]*\w+[[:space:]]*[:]</BEGIN>
            <END>&gt;</END>
        </SPAN_REGEXP>


        <!-- regular expression definitions -->
     <!--    <SEQ_REGEXP HASH_CHAR=3D"&lt;"
TYPE=3D"KEYWORD2">&lt;[[:space:]]*\w+[[:space:]]*[:]</SEQ_REGEXP> -->

        <!-- regular expression label(s) -->

        <!-- private regular expression labels -->
        <SEQ_REGEXP HASH_CHAR=3D"#" TYPE=3D"KEYWORD2">[#]\w+[:]</SEQ_REGEXP=
>

        <KEYWORDS>
            <!-- javacc keywords -->
            <KEYWORD1>EOF</KEYWORD1>
            <KEYWORD1>IGNORE_CASE</KEYWORD1>
            <KEYWORD1>JAVACODE</KEYWORD1>
            <KEYWORD1>LOOKAHEAD</KEYWORD1>
            <KEYWORD1>MORE</KEYWORD1>
            <KEYWORD1>PARSER_BEGIN</KEYWORD1>
            <KEYWORD1>PARSER_END</KEYWORD1>
            <KEYWORD1>SKIP</KEYWORD1>
            <KEYWORD1>SPECIAL_TOKEN</KEYWORD1>
            <KEYWORD1>TOKEN</KEYWORD1>
            <KEYWORD1>TOKEN_MGR_DECLS</KEYWORD1>
            <KEYWORD1>options</KEYWORD1>

            <!-- DEFAULT is the standard lexical state -->
            <KEYWORD2>DEFAULT</KEYWORD2>
        </KEYWORDS>

    </RULES>

     <RULES SET=3D"DEFINITION1" DEFAULT=3D"KEYWORD2" ESCAPE=3D"\">
        <SPAN TYPE=3D"COMMENT1">
            <BEGIN>/*</BEGIN>
            <END>*/</END>
        </SPAN>
        <SPAN TYPE=3D"LITERAL1" NO_LINE_BREAK=3D"TRUE">
            <BEGIN>"</BEGIN>
            <END>"</END>
        </SPAN>
        <SEQ TYPE=3D"OPERATOR">,</SEQ>
        <SEQ TYPE=3D"OPERATOR">-</SEQ>
        <SEQ TYPE=3D"OPERATOR">?</SEQ>
        <SEQ TYPE=3D"OPERATOR">:</SEQ>
        <SEQ TYPE=3D"OPERATOR">|</SEQ>
        <SEQ TYPE=3D"OPERATOR">[</SEQ>
        <SEQ TYPE=3D"OPERATOR">]</SEQ>
        <SEQ TYPE=3D"OPERATOR">(</SEQ>
        <SEQ TYPE=3D"OPERATOR">)</SEQ>
        <SEQ TYPE=3D"OPERATOR">*</SEQ>
        <SEQ TYPE=3D"OPERATOR">~</SEQ>
        <SEQ TYPE=3D"OPERATOR">&lt;</SEQ>
        <SEQ TYPE=3D"OPERATOR">&gt;</SEQ>


    </RULES>
</MODE>

Patches item #1447647, was opened at 03/10/06 16:33
Message generated for change (Comment added) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300588&aid=1447647&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: Fixed
Priority: 5
Submitted By: zubin (zubinmadon)
Assigned to: Alan Ezust (ezust)
Summary: Patch: JavaScriptSideKick sees prototype methods correctly

Initial Comment:
JavaScriptSideKick didn't correctly parse methods
defined as, for example:

MyClass.prototype.myMethod = function(){}

I patched it to do so, but to fix this in a clean way,
I also had to patch PerlSideKick.

The file is a .tar.gz of both patches, the PerlSideKick
one needs to be used first for the JavaScriptSideKick
one to compile

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

>Comment By: SourceForge Robot (sf-robot)
Date: 03/29/06 19:20

Message:
Logged In: YES 
user_id=1312539

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

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

Comment By: Martin Raspe (hertzhaft)
Date: 03/14/06 03:29

Message:
Logged In: YES 
user_id=1037294

The dependency on PerlSidekick was removed by Alan Ezust
some time ago, and I checked in some days ago a new version
0.3 which recognizes the "prototype" idiom. Please check out
tag "release-0_3" and try to compile and install it. I hope
it works (I couldn't get the newest SideKick changes yet).

Martin

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

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

Looking better!  I do see a couple of inconsistencies:

1. In this one,
   < STRING_LITERAL:
       "\""
       (   (~["\"","\\","\n","\r"])
         | ("\\"
             ( ["n","t","b","r","f","\\","'","\""]
             | ["0"-"7"] ( ["0"-"7"] )?
             | ["0"-"3"] ["0"-"7"] ["0"-"7"]
             )
           )
       )*
       "\""
   >

the commas in the first row with commas are different color than the 
commas in the second row with commas.

2. In this one,
   < INTEGER_LITERAL:
         <DECIMAL_LITERAL> (["l","L"])?
       | <HEX_LITERAL> (["l","L"])?
       | <OCTAL_LITERAL> (["l","L"])?
   >

the question marks are different color than the question marks in #1. 
Also, the leading < is different color than the trailing >.

3.  In this one,
void ExpressionList() :
{
     String s;
}
{
     {
         System.out.println("Please type in an expression followed by a 
\";\" or ^D to quit:");
         System.out.println("");
     }
     ( s=Expression() ";"
     {
         System.out.println(s);
         System.out.println("");
         System.out.println("Please type in another expression followed by 
a \";\" or ^D to quit:");
         System.out.println("");
     }
     )*
     <EOF>
}

string highlighting missed the escaped double quote in the first 
System.out.println, so the text following the first \" is not right.

This is looking much better!

On Thu, 30 Mar 2006, Matthieu Casanova wrote:

> 2006/3/28, Dale Anson <da...@gr...>:
>>
>> I'm not seeing how the DOUBLEQUOTE example isn't working.  What are you
>> seeing?
>>
>> And about the trailing > not being the same color as the leading < is
>> true, I couldn't figure out how to either not highlight the leading < or
>> do highlight the trailing > without (mis)coloring everything in between.
>>
>> Dale
>
>
> The problem is here
> <DOUBLEQUOTE : "\""> : IN_STRING
>
> the : IN_STRING is colored as LITERAL
> I maybe have found some fix, could you try this one ?
>
>
> <?xml version="1.0"?>
> <!DOCTYPE MODE SYSTEM "xmode.dtd">
> <MODE>
>    <PROPS>
>        <PROPERTY NAME="commentStart" VALUE="/*" />
>        <PROPERTY NAME="commentEnd" VALUE="*/" />
>        <PROPERTY NAME="lineComment" VALUE="//" />
>        <PROPERTY NAME="wordBreakChars" VALUE=",+-=&lt;&gt;/?^&amp;*" />
>
>               <!-- Auto indent -->
>        <PROPERTY NAME="indentOpenBrackets" VALUE="{" />
>        <PROPERTY NAME="indentCloseBrackets" VALUE="}" />
>        <PROPERTY NAME="unalignedOpenBrackets" VALUE="(" />
>        <PROPERTY NAME="unalignedCloseBrackets" VALUE=")" />
>        <PROPERTY NAME="indentNextLine"
> VALUE="\s*(((if|while)\s*\(|else\s*|else\s+if\s*\(|for\s*\(.*\))[^{;]*)"/>
>        <PROPERTY NAME="unindentThisLine"
> VALUE="^.*(default:\s*|case.*:.*)$" />
>        <PROPERTY NAME="electricKeys" VALUE=":" />
>    </PROPS>
>    <RULES IGNORE_CASE="FALSE">
>        <IMPORT DELEGATE="java::MAIN"/>
>  <SEQ_REGEXP HASH_CHAR="&lt;"
> TYPE="KEYWORD2">&lt;[[:space:]]*\w+([[:space:]]*[,][[:space:]]*\w+[[:space:]]*)*[[:space:]]*&gt;</SEQ_REGEXP>
>
>      <!--   <SPAN DELEGATE="DEFINITION1">
>            <BEGIN>&lt;</BEGIN>
>            <END>&gt;</END>
>            </SPAN> -->
>
>        <SPAN_REGEXP HASH_CHAR="&lt;" DELEGATE="DEFINITION1"
> TYPE="KEYWORD2">
>            <BEGIN>&lt;[[:space:]]*\w+[[:space:]]*[:]</BEGIN>
>            <END>&gt;</END>
>        </SPAN_REGEXP>
>
>
>        <!-- regular expression definitions -->
>     <!--    <SEQ_REGEXP HASH_CHAR="&lt;"
> TYPE="KEYWORD2">&lt;[[:space:]]*\w+[[:space:]]*[:]</SEQ_REGEXP> -->
>
>        <!-- regular expression label(s) -->
>
>        <!-- private regular expression labels -->
>        <SEQ_REGEXP HASH_CHAR="#" TYPE="KEYWORD2">[#]\w+[:]</SEQ_REGEXP>
>
>        <KEYWORDS>
>            <!-- javacc keywords -->
>            <KEYWORD1>EOF</KEYWORD1>
>            <KEYWORD1>IGNORE_CASE</KEYWORD1>
>            <KEYWORD1>JAVACODE</KEYWORD1>
>            <KEYWORD1>LOOKAHEAD</KEYWORD1>
>            <KEYWORD1>MORE</KEYWORD1>
>            <KEYWORD1>PARSER_BEGIN</KEYWORD1>
>            <KEYWORD1>PARSER_END</KEYWORD1>
>            <KEYWORD1>SKIP</KEYWORD1>
>            <KEYWORD1>SPECIAL_TOKEN</KEYWORD1>
>            <KEYWORD1>TOKEN</KEYWORD1>
>            <KEYWORD1>TOKEN_MGR_DECLS</KEYWORD1>
>            <KEYWORD1>options</KEYWORD1>
>
>            <!-- DEFAULT is the standard lexical state -->
>            <KEYWORD2>DEFAULT</KEYWORD2>
>        </KEYWORDS>
>
>    </RULES>
>
>     <RULES SET="DEFINITION1" IGNORE_CASE="FALSE" DEFAULT="KEYWORD2">
>        <SPAN TYPE="COMMENT1">
>            <BEGIN>/*</BEGIN>
>            <END>*/</END>
>        </SPAN>
>        <SEQ TYPE="OPERATOR">:</SEQ>
>        <SEQ TYPE="OPERATOR">|</SEQ>
>        <SEQ TYPE="OPERATOR">[</SEQ>
>        <SEQ TYPE="OPERATOR">]</SEQ>
>        <SEQ TYPE="OPERATOR">(</SEQ>
>        <SEQ TYPE="OPERATOR">)</SEQ>
>        <SEQ TYPE="OPERATOR">*</SEQ>
>        <SEQ TYPE="OPERATOR">~</SEQ>
>        <SEQ TYPE="OPERATOR">&lt;</SEQ>
>        <SEQ TYPE="OPERATOR">&gt;</SEQ>
>        <SPAN TYPE="LITERAL1" NO_LINE_BREAK="TRUE">
>            <BEGIN>"</BEGIN>
>            <END>"</END>
>        </SPAN>
>
>    </RULES>
> </MODE>
>

2006/3/28, Dale Anson <da...@gr...>:
>
> I'm not seeing how the DOUBLEQUOTE example isn't working.  What are you
> seeing?
>
> And about the trailing > not being the same color as the leading < is
> true, I couldn't figure out how to either not highlight the leading < or
> do highlight the trailing > without (mis)coloring everything in between.
>
> Dale


The problem is here
<DOUBLEQUOTE : "\""> : IN_STRING

the : IN_STRING is colored as LITERAL
I maybe have found some fix, could you try this one ?


<?xml version=3D"1.0"?>
<!DOCTYPE MODE SYSTEM "xmode.dtd">
<MODE>
    <PROPS>
        <PROPERTY NAME=3D"commentStart" VALUE=3D"/*" />
        <PROPERTY NAME=3D"commentEnd" VALUE=3D"*/" />
        <PROPERTY NAME=3D"lineComment" VALUE=3D"//" />
        <PROPERTY NAME=3D"wordBreakChars" VALUE=3D",+-=3D&lt;&gt;/?^&amp;*"=
 />

               <!-- Auto indent -->
        <PROPERTY NAME=3D"indentOpenBrackets" VALUE=3D"{" />
        <PROPERTY NAME=3D"indentCloseBrackets" VALUE=3D"}" />
        <PROPERTY NAME=3D"unalignedOpenBrackets" VALUE=3D"(" />
        <PROPERTY NAME=3D"unalignedCloseBrackets" VALUE=3D")" />
        <PROPERTY NAME=3D"indentNextLine"
VALUE=3D"\s*(((if|while)\s*\(|else\s*|else\s+if\s*\(|for\s*\(.*\))[^{;]*)"/=
>
        <PROPERTY NAME=3D"unindentThisLine"
VALUE=3D"^.*(default:\s*|case.*:.*)$" />
        <PROPERTY NAME=3D"electricKeys" VALUE=3D":" />
    </PROPS>
    <RULES IGNORE_CASE=3D"FALSE">
        <IMPORT DELEGATE=3D"java::MAIN"/>
  <SEQ_REGEXP HASH_CHAR=3D"&lt;"
TYPE=3D"KEYWORD2">&lt;[[:space:]]*\w+([[:space:]]*[,][[:space:]]*\w+[[:spac=
e:]]*)*[[:space:]]*&gt;</SEQ_REGEXP>

      <!--   <SPAN DELEGATE=3D"DEFINITION1">
            <BEGIN>&lt;</BEGIN>
            <END>&gt;</END>
            </SPAN> -->

        <SPAN_REGEXP HASH_CHAR=3D"&lt;" DELEGATE=3D"DEFINITION1"
TYPE=3D"KEYWORD2">
            <BEGIN>&lt;[[:space:]]*\w+[[:space:]]*[:]</BEGIN>
            <END>&gt;</END>
        </SPAN_REGEXP>


        <!-- regular expression definitions -->
     <!--    <SEQ_REGEXP HASH_CHAR=3D"&lt;"
TYPE=3D"KEYWORD2">&lt;[[:space:]]*\w+[[:space:]]*[:]</SEQ_REGEXP> -->

        <!-- regular expression label(s) -->

        <!-- private regular expression labels -->
        <SEQ_REGEXP HASH_CHAR=3D"#" TYPE=3D"KEYWORD2">[#]\w+[:]</SEQ_REGEXP=
>

        <KEYWORDS>
            <!-- javacc keywords -->
            <KEYWORD1>EOF</KEYWORD1>
            <KEYWORD1>IGNORE_CASE</KEYWORD1>
            <KEYWORD1>JAVACODE</KEYWORD1>
            <KEYWORD1>LOOKAHEAD</KEYWORD1>
            <KEYWORD1>MORE</KEYWORD1>
            <KEYWORD1>PARSER_BEGIN</KEYWORD1>
            <KEYWORD1>PARSER_END</KEYWORD1>
            <KEYWORD1>SKIP</KEYWORD1>
            <KEYWORD1>SPECIAL_TOKEN</KEYWORD1>
            <KEYWORD1>TOKEN</KEYWORD1>
            <KEYWORD1>TOKEN_MGR_DECLS</KEYWORD1>
            <KEYWORD1>options</KEYWORD1>

            <!-- DEFAULT is the standard lexical state -->
            <KEYWORD2>DEFAULT</KEYWORD2>
        </KEYWORDS>

    </RULES>

     <RULES SET=3D"DEFINITION1" IGNORE_CASE=3D"FALSE" DEFAULT=3D"KEYWORD2">
        <SPAN TYPE=3D"COMMENT1">
            <BEGIN>/*</BEGIN>
            <END>*/</END>
        </SPAN>
        <SEQ TYPE=3D"OPERATOR">:</SEQ>
        <SEQ TYPE=3D"OPERATOR">|</SEQ>
        <SEQ TYPE=3D"OPERATOR">[</SEQ>
        <SEQ TYPE=3D"OPERATOR">]</SEQ>
        <SEQ TYPE=3D"OPERATOR">(</SEQ>
        <SEQ TYPE=3D"OPERATOR">)</SEQ>
        <SEQ TYPE=3D"OPERATOR">*</SEQ>
        <SEQ TYPE=3D"OPERATOR">~</SEQ>
        <SEQ TYPE=3D"OPERATOR">&lt;</SEQ>
        <SEQ TYPE=3D"OPERATOR">&gt;</SEQ>
        <SPAN TYPE=3D"LITERAL1" NO_LINE_BREAK=3D"TRUE">
            <BEGIN>"</BEGIN>
            <END>"</END>
        </SPAN>

    </RULES>
</MODE>

I've been having problems with commoncontrols not loading on jedit
startup. I get this message every time:
[error] ErrorListDialog$ErrorEntry:
/home/ezust/workspace/jEdit/jars/CommonControls.jar:
[error] ErrorListDialog$ErrorEntry: Requires JAR file
/home/ezust/workspace/jEdit/jars/kappalayout.jar.
[error] ErrorListDialog$ErrorEntry: This JAR file is part of this
plugin, but it cannot be found.
[error] ErrorListDialog$ErrorEntry: Try reinstalling this plugin.
[error] ErrorListDialog$ErrorEntry: /home/ezust/workspace/jEdit/jars/Docker=
.jar:
[error] ErrorListDialog$ErrorEntry: Requires CommonControlsPlugin, but
CommonControlsPlugin
[error] ErrorListDialog$ErrorEntry: could not be loaded.
[error] ErrorListDialog$ErrorEntry:
/home/ezust/workspace/jEdit/jars/ProjectViewer.jar:
[error] ErrorListDialog$ErrorEntry: Requires CommonControlsPlugin, but
CommonControlsPlugin
[error] ErrorListDialog$ErrorEntry: could not be loaded.

If I go into plugin manager, and can restart the CommonControls
plugin, then I can restart the others (proejctviewer and alll the
others that depend on CommonControls). But it seems i have to do this
every time I start up jedit.

Why is it not finding kappalayout on startup, when it is clearly there?

Plugin Bugs item #1460349, was opened at 2006-03-28 16:44
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=565475&aid=1460349&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
Submitted By: Philip Steiner (phipster)
Assigned to: Nobody/Anonymous (nobody)
Summary: console 4.2.5 Windows shell commands

Initial Comment:
Brief problem description: 

Console 4.2.5 throws error java.lang.RuntimeException:
Unrecognized command: <command> when trying to execute
Windows built-in shell commands or commands that rely
on "fileexts" settings (e.g. .bat, .pl). 

Did not encounter this problem with Console 4.1.2.

Environment:
- Console 4.2.5
- jEdit 4.3pre3
- java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed
mode, sharing)
- Windows 2000 Pro SP4
- Lotsa RAM, CPU, disk, etc.

Example run ("ccdc" is a Perl script):

C:\NCOT\ccdc> ccdc 
java.lang.RuntimeException: Unrecognized command: ccdc
C:\NCOT\ccdc> ccdc.pl
java.lang.RuntimeException: Unrecognized command: ccdc.pl
C:\NCOT\ccdc> perl ccdc.pl
ccdc v.0.1 (c) 2005 MDA
Usage: ccdc [-p N[,N]] [-g] [-sltp] lesson.ctd

C:\NCOT\ccdc> hello
java.lang.RuntimeException: Unrecognized command: hello
C:\NCOT\ccdc> hello.bat

C:\NCOT\ccdc>echo hello world! 
hello world!
C:\NCOT\ccdc> 

Thanks

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

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

I'm not seeing how the DOUBLEQUOTE example isn't working.  What are you 
seeing?

And about the trailing > not being the same color as the leading < is 
true, I couldn't figure out how to either not highlight the leading < or 
do highlight the trailing > without (mis)coloring everything in between.

Dale


On Tue, 28 Mar 2006, Matthieu Casanova wrote:

> That's better but not yet perfect
> this one
> <DOUBLEQUOTE : "\""> doesnt work properly
> and in that one
> <DOLLARS : "$">
> the > is not in the same color the < is
>
> Matt
>
> 2006/3/28, Dale Anson <da...@gr...>:
>>
>> This seems to work pretty well:
>>
>> <?xml version="1.0"?>
>> <!DOCTYPE MODE SYSTEM "xmode.dtd">
>> <MODE>
>>      <PROPS>
>>          <PROPERTY NAME="commentStart" VALUE="/*" />
>>          <PROPERTY NAME="commentEnd" VALUE="*/" />
>>          <PROPERTY NAME="lineComment" VALUE="//" />
>>          <PROPERTY NAME="wordBreakChars" VALUE=",+-=&lt;&gt;/?^&amp;*" />
>>
>>                 <!-- Auto indent -->
>>          <PROPERTY NAME="indentOpenBrackets" VALUE="{" />
>>          <PROPERTY NAME="indentCloseBrackets" VALUE="}" />
>>          <PROPERTY NAME="unalignedOpenBrackets" VALUE="(" />
>>          <PROPERTY NAME="unalignedCloseBrackets" VALUE=")" />
>>          <PROPERTY NAME="indentNextLine"
>>
>> VALUE="\s*(((if|while)\s*\(|else\s*|else\s+if\s*\(|for\s*\(.*\))[^{;]*)"
>> />
>>          <PROPERTY NAME="unindentThisLine"
>>                  VALUE="^.*(default:\s*|case.*:.*)$" />
>>          <PROPERTY NAME="electricKeys" VALUE=":" />
>>      </PROPS>
>>      <RULES IGNORE_CASE="FALSE">
>>          <IMPORT DELEGATE="java::MAIN"/>
>>
>>          <!-- regular expression definitions -->
>>          <SEQ_REGEXP HASH_CHAR="&lt;"
>> TYPE="KEYWORD2">&lt;[[:space:]]*\w+[[:space:]]*[:]</SEQ_REGEXP>
>>
>>          <!-- regular expression label(s) -->
>>          <SEQ_REGEXP HASH_CHAR="&lt;"
>>
>> TYPE="KEYWORD2">&lt;[[:space:]]*\w+([[:space:]]*[,][[:space:]]*\w+[[:space:]]*)*[[:space:]]*&gt;</SEQ_REGEXP>
>>
>>          <!-- private regular expression labels -->
>>          <SEQ_REGEXP HASH_CHAR="#" TYPE="KEYWORD2">[#]\w+[:]</SEQ_REGEXP>
>>
>>          <KEYWORDS>
>>              <!-- javacc keywords -->
>>              <KEYWORD1>EOF</KEYWORD1>
>>              <KEYWORD1>IGNORE_CASE</KEYWORD1>
>>              <KEYWORD1>JAVACODE</KEYWORD1>
>>              <KEYWORD1>LOOKAHEAD</KEYWORD1>
>>              <KEYWORD1>MORE</KEYWORD1>
>>              <KEYWORD1>PARSER_BEGIN</KEYWORD1>
>>              <KEYWORD1>PARSER_END</KEYWORD1>
>>              <KEYWORD1>SKIP</KEYWORD1>
>>              <KEYWORD1>SPECIAL_TOKEN</KEYWORD1>
>>              <KEYWORD1>TOKEN</KEYWORD1>
>>              <KEYWORD1>TOKEN_MGR_DECLS</KEYWORD1>
>>              <KEYWORD1>options</KEYWORD1>
>>
>>              <!-- DEFAULT is the standard lexical state -->
>>              <KEYWORD2>DEFAULT</KEYWORD2>
>>          </KEYWORDS>
>>
>>      </RULES>
>> </MODE>
>>
>> On Tue, 28 Mar 2006, Dale Anson wrote:
>>
>>> I'm looking at better syntax highlighting also.  It's okay now, but
>> could be
>>> nicer.
>>>
>>> Dale
>>>
>>>
>>> On Tue, 28 Mar 2006, Matthieu Casanova wrote:
>>>
>>>>  you're right I removed it until a solution is found
>>>>
>>>>  Matthieu
>>>>
>>>>  2006/3/28, Dale Anson <da...@gr...>:
>>>>>
>>>>>  No, that has problems too.  If there is a < as a 'less than' in some
>>>>>  code
>>>>>  in the PARSER block, all subsequent code is colored as keyword2
>> until
>>>>>  the
>>>>>  next >, which could be quite a long way.
>>>>>
>>>>>  On Tue, 28 Mar 2006, Matthieu Casanova wrote:
>>>>>
>>>>>>  you're right, the delegation is not good it was a too quick copy
>> past.
>>>>>>  What do you think about
>>>>>>  <SPAN TYPE="KEYWORD2">
>>>>>>                         <BEGIN>&lt;</BEGIN>
>>>>>>                         <END>&gt;</END>
>>>>>>                 </SPAN>
>>>>>>
>>>>>>  2006/3/28, Dale Anson <da...@gr...>:
>>>>>>>
>>>>>>>  This part causes problems:
>>>>>>>
>>>>>>>           <SPAN TYPE="KEYWORD2" DELEGATE="xml::DTD-TAGS">
>>>>>>>                          <BEGIN>&lt;</BEGIN>
>>>>>>>                          <END>&gt;</END>
>>>>>>>                  </SPAN>
>>>>>>>
>>>>>>>  A lot of the markup in a javacc file sort of looks like xml, but
>>>>>>>  it's
>>>>>  not.
>>>>>>>  The rest seems to be good.
>>>>>>>
>>>>>>>  Dale
>>>>>>>
>>>>>>>
>>>>>>>  On Mon, 27 Mar 2006, Matthieu Casanova wrote:
>>>>>>>
>>>>>>>>  Hi, I added the props of java.xml into javacc.xml (hope I
>> missed
>>>>>>>  nothing) to
>>>>>>>>  allow addexplicitfold, comment line to work
>>>>>>>>
>>>>>>>>  Matthieu
>>>>>>>>
>>>>>>>>  2006/3/27, Dale Anson <da...@gr...>:
>>>>>>>>>
>>>>>>>>>  Thanks!
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>  On Sun, 26 Mar 2006, Matthieu Casanova wrote:
>>>>>>>>>
>>>>>>>>>>  Hi, I just added it into CVS, thanks
>>>>>>>>>>
>>>>>>>>>>  Matthieu
>>>>>>>>>>
>>>>>>>>>>  2006/3/26, Dale Anson <da...@gr...>:
>>>>>>>>>>>
>>>>>>>>>>>  Below is a new mode for javacc files.  Mostly this just
>> adds
>>>>>  keywords
>>>>>>>>>  to
>>>>>>>>>>>  the java mode that are specific to javacc.
>>>>>>>>>>>
>>>>>>>>>>>  <?xml version="1.0"?>
>>>>>>>>>>>  <!DOCTYPE MODE SYSTEM "xmode.dtd">
>>>>>>>>>>>  <MODE>
>>>>>>>>>>>       <RULES IGNORE_CASE="FALSE">
>>>>>>>>>>>           <IMPORT DELEGATE="java::MAIN"/>
>>>>>>>>>>>           <KEYWORDS>
>>>>>>>>>>>               <KEYWORD1>EOF</KEYWORD1>
>>>>>>>>>>>               <KEYWORD1>IGNORE_CASE</KEYWORD1>
>>>>>>>>>>>               <KEYWORD1>JAVACODE</KEYWORD1>
>>>>>>>>>>>               <KEYWORD1>LOOKAHEAD</KEYWORD1>
>>>>>>>>>>>               <KEYWORD1>MORE</KEYWORD1>
>>>>>>>>>>>               <KEYWORD1>PARSER_BEGIN</KEYWORD1>
>>>>>>>>>>>               <KEYWORD1>PARSER_END</KEYWORD1>
>>>>>>>>>>>               <KEYWORD1>SKIP</KEYWORD1>
>>>>>>>>>>>               <KEYWORD1>SPECIAL_TOKEN</KEYWORD1>
>>>>>>>>>>>               <KEYWORD1>TOKEN</KEYWORD1>
>>>>>>>>>>>               <KEYWORD1>TOKEN_MGR_DECLS</KEYWORD1>
>>>>>>>>>>>               <KEYWORD1>options</KEYWORD1>
>>>>>>>>>>>           </KEYWORDS>
>>>>>>>>>>>       </RULES>
>>>>>>>>>>>  </MODE>
>>>>>>>>>>>
>>>>>>>>>>>  Here is the catalog entry for this mode:
>>>>>>>>>>>
>>>>>>>>>>>       <MODE NAME="javacc" FILE="javacc.xml"
>>>>>>>>>  FILE_NAME_GLOB="*.{jj,jjt}"/>
>>>>>>>>>>>
>>>>>>>>>>>  I'd like to request that this be added as a standard
>> mode.
>>>>>>>>>>>  I've
>>>>>  been
>>>>>>>>>>>  using this mode in the development of JavaSideKick, and
>> find
>>>>>>>>>>>  it
>>>>>>>  handy.
>>>>>>>>>>>  Further, I've written a "javacc" sidekick and built it
>> into
>>>>>>>>>  JavaSideKick,
>>>>>>>>>>>  this mode needs to be installed so that SideKick will
>> pick
>>>>>>>>>>>  the
>>>>>  proper
>>>>>>>>>>>  parser for javacc files.
>>>>>>>>>>>
>>>>>>>>>>>  Let me know if it would be easier if I just checked this
>> in
>>>>>>>>>>>  myself.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>  Thanks,
>>>>>>>>>>>
>>>>>>>>>>>  Dale
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>  -------------------------------------------------------
>>>>>>>>>>>  This SF.Net email is sponsored by xPML, a groundbreaking
>>>>>>>>>>>  scripting
>>>>>>>>>>>  language
>>>>>>>>>>>  that extends applications into web and mobile media.
>> Attend
>>>>>>>>>>>  the
>>>>>  live
>>>>>>>>>>>  webcast
>>>>>>>>>>>  and join the prime developer group breaking into this
>> new
>>>>>>>>>>>  coding
>>>>>>>>>>>  territory!
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>>>>>>>>>>>  --
>>>>>>>>>>>  -----------------------------------------------
>>>>>>>>>>>  jEdit Developers' List
>>>>>>>>>>>  jEd...@li...
>>>>>>>>>>>  https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>  -------------------------------------------------------
>>>>>>>  This SF.Net email is sponsored by xPML, a groundbreaking
>> scripting
>>>>>>>  language
>>>>>>>  that extends applications into web and mobile media. Attend the
>> live
>>>>>>>  webcast
>>>>>>>  and join the prime developer group breaking into this new coding
>>>>>>>  territory!
>>>>>>>
>>>>>
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>>>>>>>  --
>>>>>>>  -----------------------------------------------
>>>>>>>  jEdit Developers' List
>>>>>>>  jEd...@li...
>>>>>>>  https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
>> language
>>> that extends applications into web and mobile media. Attend the live
>> webcast
>>> and join the prime developer group breaking into this new coding
>> territory!
>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>>> --
>>> -----------------------------------------------
>>> jEdit Developers' List
>>> jEd...@li...
>>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>>
>>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
>> language
>> that extends applications into web and mobile media. Attend the live
>> webcast
>> and join the prime developer group breaking into this new coding
>> territory!
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>> --
>> -----------------------------------------------
>> jEdit Developers' List
>> jEd...@li...
>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>
>

This seems to work pretty well:

<?xml version="1.0"?>
<!DOCTYPE MODE SYSTEM "xmode.dtd">
<MODE>
     <PROPS>
         <PROPERTY NAME="commentStart" VALUE="/*" />
         <PROPERTY NAME="commentEnd" VALUE="*/" />
         <PROPERTY NAME="lineComment" VALUE="//" />
         <PROPERTY NAME="wordBreakChars" VALUE=",+-=&lt;&gt;/?^&amp;*" />

 		<!-- Auto indent -->
         <PROPERTY NAME="indentOpenBrackets" VALUE="{" />
         <PROPERTY NAME="indentCloseBrackets" VALUE="}" />
         <PROPERTY NAME="unalignedOpenBrackets" VALUE="(" />
         <PROPERTY NAME="unalignedCloseBrackets" VALUE=")" />
         <PROPERTY NAME="indentNextLine"

VALUE="\s*(((if|while)\s*\(|else\s*|else\s+if\s*\(|for\s*\(.*\))[^{;]*)" 
/>
         <PROPERTY NAME="unindentThisLine"
                 VALUE="^.*(default:\s*|case.*:.*)$" />
         <PROPERTY NAME="electricKeys" VALUE=":" />
     </PROPS>
     <RULES IGNORE_CASE="FALSE">
         <IMPORT DELEGATE="java::MAIN"/>

         <!-- regular expression definitions -->
         <SEQ_REGEXP HASH_CHAR="&lt;" 
TYPE="KEYWORD2">&lt;[[:space:]]*\w+[[:space:]]*[:]</SEQ_REGEXP>

         <!-- regular expression label(s) -->
         <SEQ_REGEXP HASH_CHAR="&lt;" 
TYPE="KEYWORD2">&lt;[[:space:]]*\w+([[:space:]]*[,][[:space:]]*\w+[[:space:]]*)*[[:space:]]*&gt;</SEQ_REGEXP>

         <!-- private regular expression labels -->
         <SEQ_REGEXP HASH_CHAR="#" TYPE="KEYWORD2">[#]\w+[:]</SEQ_REGEXP>

         <KEYWORDS>
             <!-- javacc keywords -->
             <KEYWORD1>EOF</KEYWORD1>
             <KEYWORD1>IGNORE_CASE</KEYWORD1>
             <KEYWORD1>JAVACODE</KEYWORD1>
             <KEYWORD1>LOOKAHEAD</KEYWORD1>
             <KEYWORD1>MORE</KEYWORD1>
             <KEYWORD1>PARSER_BEGIN</KEYWORD1>
             <KEYWORD1>PARSER_END</KEYWORD1>
             <KEYWORD1>SKIP</KEYWORD1>
             <KEYWORD1>SPECIAL_TOKEN</KEYWORD1>
             <KEYWORD1>TOKEN</KEYWORD1>
             <KEYWORD1>TOKEN_MGR_DECLS</KEYWORD1>
             <KEYWORD1>options</KEYWORD1>

             <!-- DEFAULT is the standard lexical state -->
             <KEYWORD2>DEFAULT</KEYWORD2>
         </KEYWORDS>

     </RULES>
</MODE>

On Tue, 28 Mar 2006, Dale Anson wrote:

> I'm looking at better syntax highlighting also.  It's okay now, but could be 
> nicer.
>
> Dale
>
>
> On Tue, 28 Mar 2006, Matthieu Casanova wrote:
>
>>  you're right I removed it until a solution is found
>>
>>  Matthieu
>>
>>  2006/3/28, Dale Anson <da...@gr...>:
>> > 
>> >  No, that has problems too.  If there is a < as a 'less than' in some 
>> >  code
>> >  in the PARSER block, all subsequent code is colored as keyword2 until 
>> >  the
>> >  next >, which could be quite a long way.
>> > 
>> >  On Tue, 28 Mar 2006, Matthieu Casanova wrote:
>> > 
>> > >  you're right, the delegation is not good it was a too quick copy past.
>> > >  What do you think about
>> > >  <SPAN TYPE="KEYWORD2">
>> > >                         <BEGIN>&lt;</BEGIN>
>> > >                         <END>&gt;</END>
>> > >                 </SPAN>
>> > > 
>> > >  2006/3/28, Dale Anson <da...@gr...>:
>> > > > 
>> > > >  This part causes problems:
>> > > > 
>> > > >           <SPAN TYPE="KEYWORD2" DELEGATE="xml::DTD-TAGS">
>> > > >                          <BEGIN>&lt;</BEGIN>
>> > > >                          <END>&gt;</END>
>> > > >                  </SPAN>
>> > > > 
>> > > >  A lot of the markup in a javacc file sort of looks like xml, but 
>> > > >  it's
>> >  not.
>> > > >  The rest seems to be good.
>> > > > 
>> > > >  Dale
>> > > > 
>> > > > 
>> > > >  On Mon, 27 Mar 2006, Matthieu Casanova wrote:
>> > > > 
>> > > > >  Hi, I added the props of java.xml into javacc.xml (hope I missed
>> > > >  nothing) to
>> > > > >  allow addexplicitfold, comment line to work
>> > > > > 
>> > > > >  Matthieu
>> > > > > 
>> > > > >  2006/3/27, Dale Anson <da...@gr...>:
>> > > > > > 
>> > > > > >  Thanks!
>> > > > > > 
>> > > > > > 
>> > > > > >  On Sun, 26 Mar 2006, Matthieu Casanova wrote:
>> > > > > > 
>> > > > > > >  Hi, I just added it into CVS, thanks
>> > > > > > > 
>> > > > > > >  Matthieu
>> > > > > > > 
>> > > > > > >  2006/3/26, Dale Anson <da...@gr...>:
>> > > > > > > > 
>> > > > > > > >  Below is a new mode for javacc files.  Mostly this just adds
>> >  keywords
>> > > > > >  to
>> > > > > > > >  the java mode that are specific to javacc.
>> > > > > > > > 
>> > > > > > > >  <?xml version="1.0"?>
>> > > > > > > >  <!DOCTYPE MODE SYSTEM "xmode.dtd">
>> > > > > > > >  <MODE>
>> > > > > > > >       <RULES IGNORE_CASE="FALSE">
>> > > > > > > >           <IMPORT DELEGATE="java::MAIN"/>
>> > > > > > > >           <KEYWORDS>
>> > > > > > > >               <KEYWORD1>EOF</KEYWORD1>
>> > > > > > > >               <KEYWORD1>IGNORE_CASE</KEYWORD1>
>> > > > > > > >               <KEYWORD1>JAVACODE</KEYWORD1>
>> > > > > > > >               <KEYWORD1>LOOKAHEAD</KEYWORD1>
>> > > > > > > >               <KEYWORD1>MORE</KEYWORD1>
>> > > > > > > >               <KEYWORD1>PARSER_BEGIN</KEYWORD1>
>> > > > > > > >               <KEYWORD1>PARSER_END</KEYWORD1>
>> > > > > > > >               <KEYWORD1>SKIP</KEYWORD1>
>> > > > > > > >               <KEYWORD1>SPECIAL_TOKEN</KEYWORD1>
>> > > > > > > >               <KEYWORD1>TOKEN</KEYWORD1>
>> > > > > > > >               <KEYWORD1>TOKEN_MGR_DECLS</KEYWORD1>
>> > > > > > > >               <KEYWORD1>options</KEYWORD1>
>> > > > > > > >           </KEYWORDS>
>> > > > > > > >       </RULES>
>> > > > > > > >  </MODE>
>> > > > > > > > 
>> > > > > > > >  Here is the catalog entry for this mode:
>> > > > > > > > 
>> > > > > > > >       <MODE NAME="javacc" FILE="javacc.xml"
>> > > > > >  FILE_NAME_GLOB="*.{jj,jjt}"/>
>> > > > > > > > 
>> > > > > > > >  I'd like to request that this be added as a standard mode. 
>> > > > > > > >  I've
>> >  been
>> > > > > > > >  using this mode in the development of JavaSideKick, and find 
>> > > > > > > >  it
>> > > >  handy.
>> > > > > > > >  Further, I've written a "javacc" sidekick and built it into
>> > > > > >  JavaSideKick,
>> > > > > > > >  this mode needs to be installed so that SideKick will pick 
>> > > > > > > >  the
>> >  proper
>> > > > > > > >  parser for javacc files.
>> > > > > > > > 
>> > > > > > > >  Let me know if it would be easier if I just checked this in 
>> > > > > > > >  myself.
>> > > > > > > > 
>> > > > > > > > 
>> > > > > > > >  Thanks,
>> > > > > > > > 
>> > > > > > > >  Dale
>> > > > > > > > 
>> > > > > > > > 
>> > > > > > > > 
>> > > > > > > >  -------------------------------------------------------
>> > > > > > > >  This SF.Net email is sponsored by xPML, a groundbreaking 
>> > > > > > > >  scripting
>> > > > > > > >  language
>> > > > > > > >  that extends applications into web and mobile media. Attend 
>> > > > > > > >  the
>> >  live
>> > > > > > > >  webcast
>> > > > > > > >  and join the prime developer group breaking into this new 
>> > > > > > > >  coding
>> > > > > > > >  territory!
>> > > > > > > > 
>> > > > > > 
>> > > > 
>> >  http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>> > > > > > > >  --
>> > > > > > > >  -----------------------------------------------
>> > > > > > > >  jEdit Developers' List
>> > > > > > > >  jEd...@li...
>> > > > > > > >  https://lists.sourceforge.net/lists/listinfo/jedit-devel
>> > > > > > > > 
>> > > > > > > 
>> > > > > > 
>> > > > > 
>> > > > 
>> > > > 
>> > > >  -------------------------------------------------------
>> > > >  This SF.Net email is sponsored by xPML, a groundbreaking scripting
>> > > >  language
>> > > >  that extends applications into web and mobile media. Attend the live
>> > > >  webcast
>> > > >  and join the prime developer group breaking into this new coding
>> > > >  territory!
>> > > > 
>> >  http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>> > > >  --
>> > > >  -----------------------------------------------
>> > > >  jEdit Developers' List
>> > > >  jEd...@li...
>> > > >  https://lists.sourceforge.net/lists/listinfo/jedit-devel
>> > > > 
>> > > 
>> > 
>> 
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> -- 
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>
>

Plugin Bugs item #1460179, was opened at 2006-03-28 10:04
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=565475&aid=1460179&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
Submitted By: Alan Ezust (ezust)
Assigned to: Marcelo Vanzin (vanza)
Summary: ProjectViewer should use jedit's file chooser

Initial Comment:
When you open a file, jedit's file chooser pops up and
we can access a favorites list, as well as other
enhanced things.

projectviewer, when you are creating a new project,
should pop up the same file chooser.



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

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

I'm looking at better syntax highlighting also.  It's okay now, but could 
be nicer.

Dale


On Tue, 28 Mar 2006, Matthieu Casanova wrote:

> you're right I removed it until a solution is found
>
> Matthieu
>
> 2006/3/28, Dale Anson <da...@gr...>:
>>
>> No, that has problems too.  If there is a < as a 'less than' in some code
>> in the PARSER block, all subsequent code is colored as keyword2 until the
>> next >, which could be quite a long way.
>>
>> On Tue, 28 Mar 2006, Matthieu Casanova wrote:
>>
>>> you're right, the delegation is not good it was a too quick copy past.
>>> What do you think about
>>> <SPAN TYPE="KEYWORD2">
>>>                        <BEGIN>&lt;</BEGIN>
>>>                        <END>&gt;</END>
>>>                </SPAN>
>>>
>>> 2006/3/28, Dale Anson <da...@gr...>:
>>>>
>>>> This part causes problems:
>>>>
>>>>          <SPAN TYPE="KEYWORD2" DELEGATE="xml::DTD-TAGS">
>>>>                         <BEGIN>&lt;</BEGIN>
>>>>                         <END>&gt;</END>
>>>>                 </SPAN>
>>>>
>>>> A lot of the markup in a javacc file sort of looks like xml, but it's
>> not.
>>>> The rest seems to be good.
>>>>
>>>> Dale
>>>>
>>>>
>>>> On Mon, 27 Mar 2006, Matthieu Casanova wrote:
>>>>
>>>>> Hi, I added the props of java.xml into javacc.xml (hope I missed
>>>> nothing) to
>>>>> allow addexplicitfold, comment line to work
>>>>>
>>>>> Matthieu
>>>>>
>>>>> 2006/3/27, Dale Anson <da...@gr...>:
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>>
>>>>>> On Sun, 26 Mar 2006, Matthieu Casanova wrote:
>>>>>>
>>>>>>> Hi, I just added it into CVS, thanks
>>>>>>>
>>>>>>> Matthieu
>>>>>>>
>>>>>>> 2006/3/26, Dale Anson <da...@gr...>:
>>>>>>>>
>>>>>>>> Below is a new mode for javacc files.  Mostly this just adds
>> keywords
>>>>>> to
>>>>>>>> the java mode that are specific to javacc.
>>>>>>>>
>>>>>>>> <?xml version="1.0"?>
>>>>>>>> <!DOCTYPE MODE SYSTEM "xmode.dtd">
>>>>>>>> <MODE>
>>>>>>>>      <RULES IGNORE_CASE="FALSE">
>>>>>>>>          <IMPORT DELEGATE="java::MAIN"/>
>>>>>>>>          <KEYWORDS>
>>>>>>>>              <KEYWORD1>EOF</KEYWORD1>
>>>>>>>>              <KEYWORD1>IGNORE_CASE</KEYWORD1>
>>>>>>>>              <KEYWORD1>JAVACODE</KEYWORD1>
>>>>>>>>              <KEYWORD1>LOOKAHEAD</KEYWORD1>
>>>>>>>>              <KEYWORD1>MORE</KEYWORD1>
>>>>>>>>              <KEYWORD1>PARSER_BEGIN</KEYWORD1>
>>>>>>>>              <KEYWORD1>PARSER_END</KEYWORD1>
>>>>>>>>              <KEYWORD1>SKIP</KEYWORD1>
>>>>>>>>              <KEYWORD1>SPECIAL_TOKEN</KEYWORD1>
>>>>>>>>              <KEYWORD1>TOKEN</KEYWORD1>
>>>>>>>>              <KEYWORD1>TOKEN_MGR_DECLS</KEYWORD1>
>>>>>>>>              <KEYWORD1>options</KEYWORD1>
>>>>>>>>          </KEYWORDS>
>>>>>>>>      </RULES>
>>>>>>>> </MODE>
>>>>>>>>
>>>>>>>> Here is the catalog entry for this mode:
>>>>>>>>
>>>>>>>>      <MODE NAME="javacc" FILE="javacc.xml"
>>>>>> FILE_NAME_GLOB="*.{jj,jjt}"/>
>>>>>>>>
>>>>>>>> I'd like to request that this be added as a standard mode.  I've
>> been
>>>>>>>> using this mode in the development of JavaSideKick, and find it
>>>> handy.
>>>>>>>> Further, I've written a "javacc" sidekick and built it into
>>>>>> JavaSideKick,
>>>>>>>> this mode needs to be installed so that SideKick will pick the
>> proper
>>>>>>>> parser for javacc files.
>>>>>>>>
>>>>>>>> Let me know if it would be easier if I just checked this in myself.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Dale
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -------------------------------------------------------
>>>>>>>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
>>>>>>>> language
>>>>>>>> that extends applications into web and mobile media. Attend the
>> live
>>>>>>>> webcast
>>>>>>>> and join the prime developer group breaking into this new coding
>>>>>>>> territory!
>>>>>>>>
>>>>>>
>>>>
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>>>>>>>> --
>>>>>>>> -----------------------------------------------
>>>>>>>> jEdit Developers' List
>>>>>>>> jEd...@li...
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
>>>> language
>>>> that extends applications into web and mobile media. Attend the live
>>>> webcast
>>>> and join the prime developer group breaking into this new coding
>>>> territory!
>>>>
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>>>> --
>>>> -----------------------------------------------
>>>> jEdit Developers' List
>>>> jEd...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>>>
>>>
>>
>

you're right I removed it until a solution is found

Matthieu

2006/3/28, Dale Anson <da...@gr...>:
>
> No, that has problems too.  If there is a < as a 'less than' in some code
> in the PARSER block, all subsequent code is colored as keyword2 until the
> next >, which could be quite a long way.
>
> On Tue, 28 Mar 2006, Matthieu Casanova wrote:
>
> > you're right, the delegation is not good it was a too quick copy past.
> > What do you think about
> > <SPAN TYPE=3D"KEYWORD2">
> >                        <BEGIN>&lt;</BEGIN>
> >                        <END>&gt;</END>
> >                </SPAN>
> >
> > 2006/3/28, Dale Anson <da...@gr...>:
> >>
> >> This part causes problems:
> >>
> >>          <SPAN TYPE=3D"KEYWORD2" DELEGATE=3D"xml::DTD-TAGS">
> >>                         <BEGIN>&lt;</BEGIN>
> >>                         <END>&gt;</END>
> >>                 </SPAN>
> >>
> >> A lot of the markup in a javacc file sort of looks like xml, but it's
> not.
> >> The rest seems to be good.
> >>
> >> Dale
> >>
> >>
> >> On Mon, 27 Mar 2006, Matthieu Casanova wrote:
> >>
> >>> Hi, I added the props of java.xml into javacc.xml (hope I missed
> >> nothing) to
> >>> allow addexplicitfold, comment line to work
> >>>
> >>> Matthieu
> >>>
> >>> 2006/3/27, Dale Anson <da...@gr...>:
> >>>>
> >>>> Thanks!
> >>>>
> >>>>
> >>>> On Sun, 26 Mar 2006, Matthieu Casanova wrote:
> >>>>
> >>>>> Hi, I just added it into CVS, thanks
> >>>>>
> >>>>> Matthieu
> >>>>>
> >>>>> 2006/3/26, Dale Anson <da...@gr...>:
> >>>>>>
> >>>>>> Below is a new mode for javacc files.  Mostly this just adds
> keywords
> >>>> to
> >>>>>> the java mode that are specific to javacc.
> >>>>>>
> >>>>>> <?xml version=3D"1.0"?>
> >>>>>> <!DOCTYPE MODE SYSTEM "xmode.dtd">
> >>>>>> <MODE>
> >>>>>>      <RULES IGNORE_CASE=3D"FALSE">
> >>>>>>          <IMPORT DELEGATE=3D"java::MAIN"/>
> >>>>>>          <KEYWORDS>
> >>>>>>              <KEYWORD1>EOF</KEYWORD1>
> >>>>>>              <KEYWORD1>IGNORE_CASE</KEYWORD1>
> >>>>>>              <KEYWORD1>JAVACODE</KEYWORD1>
> >>>>>>              <KEYWORD1>LOOKAHEAD</KEYWORD1>
> >>>>>>              <KEYWORD1>MORE</KEYWORD1>
> >>>>>>              <KEYWORD1>PARSER_BEGIN</KEYWORD1>
> >>>>>>              <KEYWORD1>PARSER_END</KEYWORD1>
> >>>>>>              <KEYWORD1>SKIP</KEYWORD1>
> >>>>>>              <KEYWORD1>SPECIAL_TOKEN</KEYWORD1>
> >>>>>>              <KEYWORD1>TOKEN</KEYWORD1>
> >>>>>>              <KEYWORD1>TOKEN_MGR_DECLS</KEYWORD1>
> >>>>>>              <KEYWORD1>options</KEYWORD1>
> >>>>>>          </KEYWORDS>
> >>>>>>      </RULES>
> >>>>>> </MODE>
> >>>>>>
> >>>>>> Here is the catalog entry for this mode:
> >>>>>>
> >>>>>>      <MODE NAME=3D"javacc" FILE=3D"javacc.xml"
> >>>> FILE_NAME_GLOB=3D"*.{jj,jjt}"/>
> >>>>>>
> >>>>>> I'd like to request that this be added as a standard mode.  I've
> been
> >>>>>> using this mode in the development of JavaSideKick, and find it
> >> handy.
> >>>>>> Further, I've written a "javacc" sidekick and built it into
> >>>> JavaSideKick,
> >>>>>> this mode needs to be installed so that SideKick will pick the
> proper
> >>>>>> parser for javacc files.
> >>>>>>
> >>>>>> Let me know if it would be easier if I just checked this in myself=
.
> >>>>>>
> >>>>>>
> >>>>>> Thanks,
> >>>>>>
> >>>>>> Dale
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> -------------------------------------------------------
> >>>>>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> >>>>>> language
> >>>>>> that extends applications into web and mobile media. Attend the
> live
> >>>>>> webcast
> >>>>>> and join the prime developer group breaking into this new coding
> >>>>>> territory!
> >>>>>>
> >>>>
> >>
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=
=3D121642
> >>>>>> --
> >>>>>> -----------------------------------------------
> >>>>>> jEdit Developers' List
> >>>>>> jEd...@li...
> >>>>>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >>
> >> -------------------------------------------------------
> >> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> >> language
> >> that extends applications into web and mobile media. Attend the live
> >> webcast
> >> and join the prime developer group breaking into this new coding
> >> territory!
> >>
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=
=3D121642
> >> --
> >> -----------------------------------------------
> >> jEdit Developers' List
> >> jEd...@li...
> >> https://lists.sourceforge.net/lists/listinfo/jedit-devel
> >>
> >
>

Plugin Bugs item #1460083, was opened at 2006-03-28 07:25
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=565475&aid=1460083&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
Submitted By: Robbert van Andel (rvanandel)
Assigned to: Nobody/Anonymous (nobody)
Summary: PHPParser doesn't like private keyword

Initial Comment:
When creating a PHP5 class, I get an error when
defining a private class variable. The error is
"unexpected token private".

Example:

class myClass {
   private $myVariable;
   private $mySecondVariable;


   function __construct() {
       //do some thing.
   }
}

The keyword private before $myVariable is marked as an
error and the rest of the file is not processed.


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

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

No, that has problems too.  If there is a < as a 'less than' in some code 
in the PARSER block, all subsequent code is colored as keyword2 until the 
next >, which could be quite a long way.

On Tue, 28 Mar 2006, Matthieu Casanova wrote:

> you're right, the delegation is not good it was a too quick copy past.
> What do you think about
> <SPAN TYPE="KEYWORD2">
>                        <BEGIN>&lt;</BEGIN>
>                        <END>&gt;</END>
>                </SPAN>
>
> 2006/3/28, Dale Anson <da...@gr...>:
>>
>> This part causes problems:
>>
>>          <SPAN TYPE="KEYWORD2" DELEGATE="xml::DTD-TAGS">
>>                         <BEGIN>&lt;</BEGIN>
>>                         <END>&gt;</END>
>>                 </SPAN>
>>
>> A lot of the markup in a javacc file sort of looks like xml, but it's not.
>> The rest seems to be good.
>>
>> Dale
>>
>>
>> On Mon, 27 Mar 2006, Matthieu Casanova wrote:
>>
>>> Hi, I added the props of java.xml into javacc.xml (hope I missed
>> nothing) to
>>> allow addexplicitfold, comment line to work
>>>
>>> Matthieu
>>>
>>> 2006/3/27, Dale Anson <da...@gr...>:
>>>>
>>>> Thanks!
>>>>
>>>>
>>>> On Sun, 26 Mar 2006, Matthieu Casanova wrote:
>>>>
>>>>> Hi, I just added it into CVS, thanks
>>>>>
>>>>> Matthieu
>>>>>
>>>>> 2006/3/26, Dale Anson <da...@gr...>:
>>>>>>
>>>>>> Below is a new mode for javacc files.  Mostly this just adds keywords
>>>> to
>>>>>> the java mode that are specific to javacc.
>>>>>>
>>>>>> <?xml version="1.0"?>
>>>>>> <!DOCTYPE MODE SYSTEM "xmode.dtd">
>>>>>> <MODE>
>>>>>>      <RULES IGNORE_CASE="FALSE">
>>>>>>          <IMPORT DELEGATE="java::MAIN"/>
>>>>>>          <KEYWORDS>
>>>>>>              <KEYWORD1>EOF</KEYWORD1>
>>>>>>              <KEYWORD1>IGNORE_CASE</KEYWORD1>
>>>>>>              <KEYWORD1>JAVACODE</KEYWORD1>
>>>>>>              <KEYWORD1>LOOKAHEAD</KEYWORD1>
>>>>>>              <KEYWORD1>MORE</KEYWORD1>
>>>>>>              <KEYWORD1>PARSER_BEGIN</KEYWORD1>
>>>>>>              <KEYWORD1>PARSER_END</KEYWORD1>
>>>>>>              <KEYWORD1>SKIP</KEYWORD1>
>>>>>>              <KEYWORD1>SPECIAL_TOKEN</KEYWORD1>
>>>>>>              <KEYWORD1>TOKEN</KEYWORD1>
>>>>>>              <KEYWORD1>TOKEN_MGR_DECLS</KEYWORD1>
>>>>>>              <KEYWORD1>options</KEYWORD1>
>>>>>>          </KEYWORDS>
>>>>>>      </RULES>
>>>>>> </MODE>
>>>>>>
>>>>>> Here is the catalog entry for this mode:
>>>>>>
>>>>>>      <MODE NAME="javacc" FILE="javacc.xml"
>>>> FILE_NAME_GLOB="*.{jj,jjt}"/>
>>>>>>
>>>>>> I'd like to request that this be added as a standard mode.  I've been
>>>>>> using this mode in the development of JavaSideKick, and find it
>> handy.
>>>>>> Further, I've written a "javacc" sidekick and built it into
>>>> JavaSideKick,
>>>>>> this mode needs to be installed so that SideKick will pick the proper
>>>>>> parser for javacc files.
>>>>>>
>>>>>> Let me know if it would be easier if I just checked this in myself.
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Dale
>>>>>>
>>>>>>
>>>>>>
>>>>>> -------------------------------------------------------
>>>>>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
>>>>>> language
>>>>>> that extends applications into web and mobile media. Attend the live
>>>>>> webcast
>>>>>> and join the prime developer group breaking into this new coding
>>>>>> territory!
>>>>>>
>>>>
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>>>>>> --
>>>>>> -----------------------------------------------
>>>>>> jEdit Developers' List
>>>>>> jEd...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>>>>>
>>>>>
>>>>
>>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
>> language
>> that extends applications into web and mobile media. Attend the live
>> webcast
>> and join the prime developer group breaking into this new coding
>> territory!
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>> --
>> -----------------------------------------------
>> jEdit Developers' List
>> jEd...@li...
>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>
>

Plugin Bugs item #1460077, was opened at 2006-03-28 17:18
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=565475&aid=1460077&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: 3
Submitted By: Björn Kautler (vampire0)
Assigned to: Nobody/Anonymous (nobody)
Summary: LatestVersion @ Plugin Central

Initial Comment:
The LatestVersion Plugin is only shipped with jEdit-
Installer and not available via Plugin Central.
IF someone deinstalls it and then wants it back (that 
definitely occurs) then the only way is to reinstall 
jEdit, get the jar elsewhere or extract the installer-
jar to get the Plugin-jar from there.
That is inconvenient and should be fixed. :-)

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

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

Plugin Bugs item #1460075, was opened at 2006-03-28 17:17
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=565475&aid=1460075&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: 3
Submitted By: Björn Kautler (vampire0)
Assigned to: Nobody/Anonymous (nobody)
Summary: QuickNotepad @ Plugin Central

Initial Comment:
The QuickNotepad Plugin is only shipped with jEdit-
Installer and not available via Plugin Central.
IF someone deinstalls it and then wants it back (that 
definitely occurs) then the only way is to reinstall 
jEdit, get the jar elsewhere or extract the installer-
jar to get the Plugin-jar from there.
That is inconvenient and should be fixed. :-)

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

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

you're right, the delegation is not good it was a too quick copy past.
What do you think about
<SPAN TYPE=3D"KEYWORD2">
                        <BEGIN>&lt;</BEGIN>
                        <END>&gt;</END>
                </SPAN>

2006/3/28, Dale Anson <da...@gr...>:
>
> This part causes problems:
>
>          <SPAN TYPE=3D"KEYWORD2" DELEGATE=3D"xml::DTD-TAGS">
>                         <BEGIN>&lt;</BEGIN>
>                         <END>&gt;</END>
>                 </SPAN>
>
> A lot of the markup in a javacc file sort of looks like xml, but it's not=
.
> The rest seems to be good.
>
> Dale
>
>
> On Mon, 27 Mar 2006, Matthieu Casanova wrote:
>
> > Hi, I added the props of java.xml into javacc.xml (hope I missed
> nothing) to
> > allow addexplicitfold, comment line to work
> >
> > Matthieu
> >
> > 2006/3/27, Dale Anson <da...@gr...>:
> >>
> >> Thanks!
> >>
> >>
> >> On Sun, 26 Mar 2006, Matthieu Casanova wrote:
> >>
> >>> Hi, I just added it into CVS, thanks
> >>>
> >>> Matthieu
> >>>
> >>> 2006/3/26, Dale Anson <da...@gr...>:
> >>>>
> >>>> Below is a new mode for javacc files.  Mostly this just adds keyword=
s
> >> to
> >>>> the java mode that are specific to javacc.
> >>>>
> >>>> <?xml version=3D"1.0"?>
> >>>> <!DOCTYPE MODE SYSTEM "xmode.dtd">
> >>>> <MODE>
> >>>>      <RULES IGNORE_CASE=3D"FALSE">
> >>>>          <IMPORT DELEGATE=3D"java::MAIN"/>
> >>>>          <KEYWORDS>
> >>>>              <KEYWORD1>EOF</KEYWORD1>
> >>>>              <KEYWORD1>IGNORE_CASE</KEYWORD1>
> >>>>              <KEYWORD1>JAVACODE</KEYWORD1>
> >>>>              <KEYWORD1>LOOKAHEAD</KEYWORD1>
> >>>>              <KEYWORD1>MORE</KEYWORD1>
> >>>>              <KEYWORD1>PARSER_BEGIN</KEYWORD1>
> >>>>              <KEYWORD1>PARSER_END</KEYWORD1>
> >>>>              <KEYWORD1>SKIP</KEYWORD1>
> >>>>              <KEYWORD1>SPECIAL_TOKEN</KEYWORD1>
> >>>>              <KEYWORD1>TOKEN</KEYWORD1>
> >>>>              <KEYWORD1>TOKEN_MGR_DECLS</KEYWORD1>
> >>>>              <KEYWORD1>options</KEYWORD1>
> >>>>          </KEYWORDS>
> >>>>      </RULES>
> >>>> </MODE>
> >>>>
> >>>> Here is the catalog entry for this mode:
> >>>>
> >>>>      <MODE NAME=3D"javacc" FILE=3D"javacc.xml"
> >> FILE_NAME_GLOB=3D"*.{jj,jjt}"/>
> >>>>
> >>>> I'd like to request that this be added as a standard mode.  I've bee=
n
> >>>> using this mode in the development of JavaSideKick, and find it
> handy.
> >>>> Further, I've written a "javacc" sidekick and built it into
> >> JavaSideKick,
> >>>> this mode needs to be installed so that SideKick will pick the prope=
r
> >>>> parser for javacc files.
> >>>>
> >>>> Let me know if it would be easier if I just checked this in myself.
> >>>>
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Dale
> >>>>
> >>>>
> >>>>
> >>>> -------------------------------------------------------
> >>>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> >>>> language
> >>>> that extends applications into web and mobile media. Attend the live
> >>>> webcast
> >>>> and join the prime developer group breaking into this new coding
> >>>> territory!
> >>>>
> >>
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=
=3D121642
> >>>> --
> >>>> -----------------------------------------------
> >>>> jEdit Developers' List
> >>>> jEd...@li...
> >>>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
> >>>>
> >>>
> >>
> >
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=
=3D121642
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>

This part causes problems:

         <SPAN TYPE="KEYWORD2" DELEGATE="xml::DTD-TAGS">
 			<BEGIN>&lt;</BEGIN>
 			<END>&gt;</END>
 		</SPAN>

A lot of the markup in a javacc file sort of looks like xml, but it's not. 
The rest seems to be good.

Dale


On Mon, 27 Mar 2006, Matthieu Casanova wrote:

> Hi, I added the props of java.xml into javacc.xml (hope I missed nothing) to
> allow addexplicitfold, comment line to work
>
> Matthieu
>
> 2006/3/27, Dale Anson <da...@gr...>:
>>
>> Thanks!
>>
>>
>> On Sun, 26 Mar 2006, Matthieu Casanova wrote:
>>
>>> Hi, I just added it into CVS, thanks
>>>
>>> Matthieu
>>>
>>> 2006/3/26, Dale Anson <da...@gr...>:
>>>>
>>>> Below is a new mode for javacc files.  Mostly this just adds keywords
>> to
>>>> the java mode that are specific to javacc.
>>>>
>>>> <?xml version="1.0"?>
>>>> <!DOCTYPE MODE SYSTEM "xmode.dtd">
>>>> <MODE>
>>>>      <RULES IGNORE_CASE="FALSE">
>>>>          <IMPORT DELEGATE="java::MAIN"/>
>>>>          <KEYWORDS>
>>>>              <KEYWORD1>EOF</KEYWORD1>
>>>>              <KEYWORD1>IGNORE_CASE</KEYWORD1>
>>>>              <KEYWORD1>JAVACODE</KEYWORD1>
>>>>              <KEYWORD1>LOOKAHEAD</KEYWORD1>
>>>>              <KEYWORD1>MORE</KEYWORD1>
>>>>              <KEYWORD1>PARSER_BEGIN</KEYWORD1>
>>>>              <KEYWORD1>PARSER_END</KEYWORD1>
>>>>              <KEYWORD1>SKIP</KEYWORD1>
>>>>              <KEYWORD1>SPECIAL_TOKEN</KEYWORD1>
>>>>              <KEYWORD1>TOKEN</KEYWORD1>
>>>>              <KEYWORD1>TOKEN_MGR_DECLS</KEYWORD1>
>>>>              <KEYWORD1>options</KEYWORD1>
>>>>          </KEYWORDS>
>>>>      </RULES>
>>>> </MODE>
>>>>
>>>> Here is the catalog entry for this mode:
>>>>
>>>>      <MODE NAME="javacc" FILE="javacc.xml"
>> FILE_NAME_GLOB="*.{jj,jjt}"/>
>>>>
>>>> I'd like to request that this be added as a standard mode.  I've been
>>>> using this mode in the development of JavaSideKick, and find it handy.
>>>> Further, I've written a "javacc" sidekick and built it into
>> JavaSideKick,
>>>> this mode needs to be installed so that SideKick will pick the proper
>>>> parser for javacc files.
>>>>
>>>> Let me know if it would be easier if I just checked this in myself.
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Dale
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
>>>> language
>>>> that extends applications into web and mobile media. Attend the live
>>>> webcast
>>>> and join the prime developer group breaking into this new coding
>>>> territory!
>>>>
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>>>> --
>>>> -----------------------------------------------
>>>> jEdit Developers' List
>>>> jEd...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>>>
>>>
>>
>

Plugin Bugs item #1459562, was opened at 2006-03-27 19:43
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=565475&aid=1459562&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
Submitted By: aksels (aksels)
Assigned to: Nobody/Anonymous (nobody)
Summary: Console runCommandInConsole

Initial Comment:
the waitForConsole command makes problems since a long
time. I always waited for a new version, but the only
one that does the job correct here is version 4.01 of
the console plugin. I tried all newer versions up to 4.2.5,
but the problem is the same.

currently I am using jedit 4.3pre3 with java 1.5.06.

description:
I have written a macro, that runs various external progs.
I call them like:
runCommandInConsole(view, "System", strCmd);
waitForConsole(view);

thats ok, if I do it with one open buffer.
the problem occurs, if you have more (i.e. 20)
open buffers and run this command for all open buffers.
than you can see, that the waitforconsole does not work,
and the macro / jedit hangs.

as I said, using console v4.01 works.
jedit 4.2x or 4.3x makes no difference. 
java versions 1.5.x makes no difference. 

if you need more input, no problem.

greetings, aksels

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

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