jedit-devel Mailing List for jEdit

Patches item #2814857, was opened at 2009-06-30 14:30
Message generated for change (Tracker Item Submitted) made by servertude
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300588&aid=2814857&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: servertude (servertude)
Assigned to: Nobody/Anonymous (nobody)
Summary: Stop caret timer in text area on dispose

Initial Comment:
This patch calls caretTimer.stop() in removeNotify in TextArea.  Without this, Swing cannot shutdown the event queue when its parent frame is disposed.

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

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

Bugs item #2814850, was opened at 2009-06-30 14:05
Message generated for change (Tracker Item Submitted) made by servertude
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=2814850&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: editor core
Group: minor bug
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: servertude (servertude)
Assigned to: Nobody/Anonymous (nobody)
Summary: Caret Timer keeps event loop running when parent is disposed

Initial Comment:
Normally, if dispose is called on a Swing Frame, and there are no more open frames, the Swing Event loop will shut down and the application will terminate.

The StandaloneTextArea sc of TextArea does not allow this behavior to occur, since the Caret Timer is still running the event loop will not be shutdown.

Fix is to call caretTimer.stop in removeNotify of TextArea 

line 4503 : add    caretTimer.stop();

This allows the Swing event loop to shutdown when all visible frames have been disposed


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

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

Patches item #2664474, was opened at 2009-03-05 09:00
Message generated for change (Comment added) made by goebbe
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300588&aid=2664474&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: goebbe (goebbe)
Assigned to: Nobody/Anonymous (nobody)
Summary: edit mode for Stata

Initial Comment:
Hello,

I would like to propose the attached edit-mode to be integrated in Jedit.
This is only the second time that I submit an edit-mode so if I am missing something or you have any suggestion, please don't hesitate to contact me.

The edit-mode is for Stata - a scripting language that is used by the statistical program with the same name. 
Stata does not offer syntax highlighting by default and I think it would be great if Jedit could provide this for Stata by default.

The attached edit-modes are based on the edit-mode for Stata, that is provided by the jedit-community. I have been in contact with Jesse Hamner, who maintained the community-version and got his approval for submission. 

Stata distinguishes between "user-provided" .do files and "system-provided" .ado files. Both use the same language in principle - but in the .ado files so called macro-language is used heavily. The attached edit-modes should handle both types well. 

The catalog entries should be:
<MODE NAME="stata_do"     FILE="statado.xml"
                FILE_NAME_GLOB="*.{do}" />

<MODE NAME="stata_ado"     FILE="stataado.xml"
                FILE_NAME_GLOB="*.{ado}" />


Kind regards
Christian

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

>Comment By: goebbe (goebbe)
Date: 2009-06-30 11:33

Message:
In order to test the proposed Stata edit mode I installed it manually (on
demand) on the computer of some colleagues that use Stata on a everyday
basis and for large projects.
So far, no complaints or additional suggestions have been raised.

Please let me know if I should provide additional information / changes to
the Stata-edit-modes.

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

Comment By: goebbe (goebbe)
Date: 2009-03-05 09:01

Message:
File Added: stataado.xml

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

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

Bugs item #2808363, was opened at 2009-06-18 17:07
Message generated for change (Comment added) made by sergzhum
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=2808363&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: editor core
Group: normal bug
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Sergey Zhumatiy (sergzhum)
Assigned to: Nobody/Anonymous (nobody)
Summary: jedit freezes on this file

Initial Comment:
File can be succesfully opened, but if I go to lines after 3400 (approx), all windows and controls in jedit freeze. They are shown, I can minimize and restore window and see all content, but cannot move cursor, press buttons, enter text. CPU is concumed at 100% (one core on my double-core machine).


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

Comment By: Sergey Zhumatiy (sergzhum)
Date: 2009-06-30 14:37

Message:
  This regexp is very simple. If you simply delete all backslashes, you'll
get list of "bad" characters, which must be deleted from input by this
regexp... Backslashes are required :)
  Some lines below contains regexps, then comment like this:

  bla-bla-bla  #` comment

  Reverse quote after '#' is placed for mc-editor. I use it sometimes
(like now), but its syntax highlighter does not understand backslashed
quote in regexp and needs dummy "closing" quote...
  May be here some like this is heppening?

  Can I help by modifying highlighter or something? If yes, where can I
find source code for it?

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

Comment By: Matthieu Casanova (kpouer)
Date: 2009-06-18 19:52

Message:
oh I was too slow ;)

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

Comment By: Denis Dzenskevich (leshij)
Date: 2009-06-18 19:14

Message:
Looks like it takes too much time to match against long strings:
  time in nanosec               input string
    69450180 - tr{\;\*\&\\~\?\<\>\|\'\"\`}{}d;    # remove ul
   156558292 - tr{\;\*\&\\~\?\<\>\|\'\"\`}{}d;    # remove uli
   335324459 - tr{\;\*\&\\~\?\<\>\|\'\"\`}{}d;    # remove ulik
   549004122 - tr{\;\*\&\\~\?\<\>\|\'\"\`}{}d;    # remove ulike
  1062590822 - tr{\;\*\&\\~\?\<\>\|\'\"\`}{}d;    # remove uliked
  2280209214 - tr{\;\*\&\\~\?\<\>\|\'\"\`}{}d;    # remove uliked 
  4330749467 - tr{\;\*\&\\~\?\<\>\|\'\"\`}{}d;    # remove uliked s
Time increments by two with each letter added to input.
I don't know perl and I don't know what this regex mean, but is is too
generic to me (only curly and "cds" letters is fixed, possibly regex could
be narrowed in some way?

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

Comment By: Kevin Hunter (hunteke)
Date: 2009-06-18 18:16

Message:
Whoops, same diagnosis.  Looks like I should have refreshed before
commenting.  :-)  You're on it.

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

Comment By: Kevin Hunter (hunteke)
Date: 2009-06-18 18:15

Message:
Hmm, not sure, but just tried a number of things:

$ split cleosupport.pm
   # jEdit opens up xaa, xab, ..., xah just fine, all readable, still
responsive, no cpu spike

$ ln -s cleosupport{.pm,}
  # jEdit opens up cleosupport (no .pm extension) just fine, all readable,
still responsive, no cpu spike

  # further, I'm able to manually change the mode (perl) with no issues,
no cpu spike, etc.

However, the error occurs for me while scrolling down.  The last visible
line is

3,467: "$arg =~ s!/+$!!;   # remove trailing slash(es)"

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

Comment By: Matthieu Casanova (kpouer)
Date: 2009-06-18 18:08

Message:
Same problem for me, it seems it is this perl.xml rule that fails :
<SEQ_REGEXP TYPE="MARKUP" HASH_CHAR="tr"
           
AT_WORD_START="TRUE">tr\s*\{.*?[^\\]\}\s*\{(?:.*?[^\\])*\}[cds]*</SEQ_REGEXP>

when trying to match on tr{\;\*\&\\~\?\<\>\|\'\"\`}{}d;    # remove uliked
symbols #`
the regexp never ends

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

Comment By: Denis Dzenskevich (leshij)
Date: 2009-06-18 17:59

Message:
Possibly a bug in java regex (or simply broken regex in python edit mode).
Matching string from a file against regex results to endless loop in java
regex library:

import java.util.regex.Pattern;

public class FaultyRegex {
    public static void main(String[] args) {
        final String str = "tr{\\;\\*\\&\\\\~\\?\\<\\>\\|\\'\\\"\\`}{}d;  
 # remove uliked symbols #`";
        final String regex =
"tr\\s*\\{.*?[^\\\\]\\}\\s*\\{(?:.*?[^\\\\])*\\}[cds]*";
       
System.out.println(Pattern.compile(regex).matcher(str).lookingAt());
    }
}

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

Comment By: Dale Anson (daleanson)
Date: 2009-06-18 17:40

Message:
I held down the "page down" key until about line 3430, then jEdit locks up
as reported.  I captured this thread dump:

Full thread dump Java HotSpot(TM) Client VM (11.3-b02 mixed mode,
sharing):                                        

"jEdit server daemon [/home/danson/.jedit/server]" daemon prio=10
tid=0x0980c400 nid=0x569 runnable [0xb4f4b000..0xb4f4c0a0]                 
                                                                           
            
   java.lang.Thread.State: RUNNABLE                                       
                                        
        at java.net.PlainSocketImpl.socketAccept(Native Method)           
                                        
        at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)      
                                        
        - locked <0x81732898> (a java.net.SocksSocketImpl)                
                                        
        at java.net.ServerSocket.implAccept(ServerSocket.java:453)        
                                        
        at java.net.ServerSocket.accept(ServerSocket.java:421)            
                                        
        at org.gjt.sp.jedit.EditServer.run(EditServer.java:132)           
                                        

"jEdit I/O #4" prio=10 tid=0x0980b000 nid=0x568 in Object.wait()
[0xb4f9c000..0xb4f9d020]
   java.lang.Thread.State: WAITING (on object monitor)                    
              
        at java.lang.Object.wait(Native Method)                           
              
        - waiting on <0x81797880> (a java.lang.Object)                    
              
        at java.lang.Object.wait(Object.java:485)                         
              
        at org.gjt.sp.util.WorkThread.doRequests(WorkThread.java:198)     
              
        - locked <0x81797880> (a java.lang.Object)                        
              
        at org.gjt.sp.util.WorkThread.run(WorkThread.java:154)            
              

"jEdit I/O #3" prio=10 tid=0x094a8400 nid=0x567 in Object.wait()
[0xb4fed000..0xb4fedfa0]
   java.lang.Thread.State: WAITING (on object monitor)                    
              
        at java.lang.Object.wait(Native Method)                           
              
        - waiting on <0x81797880> (a java.lang.Object)                    
              
        at java.lang.Object.wait(Object.java:485)                         
              
        at org.gjt.sp.util.WorkThread.doRequests(WorkThread.java:198)     
              
        - locked <0x81797880> (a java.lang.Object)                        
              
        at org.gjt.sp.util.WorkThread.run(WorkThread.java:154)            
              

"jEdit I/O #2" prio=10 tid=0x097e0c00 nid=0x566 in Object.wait()
[0xb503e000..0xb503ef20]
   java.lang.Thread.State: WAITING (on object monitor)                    
              
        at java.lang.Object.wait(Native Method)                           
              
        - waiting on <0x81797880> (a java.lang.Object)                    
              
        at java.lang.Object.wait(Object.java:485)                         
              
        at org.gjt.sp.util.WorkThread.doRequests(WorkThread.java:198)     
              
        - locked <0x81797880> (a java.lang.Object)                        
              
        at org.gjt.sp.util.WorkThread.run(WorkThread.java:154)            
              

"jEdit I/O #1" prio=10 tid=0x097e0000 nid=0x565 in Object.wait()
[0xb50ab000..0xb50abea0]
   java.lang.Thread.State: WAITING (on object monitor)                    
              
        at java.lang.Object.wait(Native Method)                           
              
        - waiting on <0x81797880> (a java.lang.Object)                    
              
        at java.lang.Object.wait(Object.java:485)                         
              
        at org.gjt.sp.util.WorkThread.doRequests(WorkThread.java:198)     
              
        - locked <0x81797880> (a java.lang.Object)                        
              
        at org.gjt.sp.util.WorkThread.run(WorkThread.java:154)            
              

"DestroyJavaVM" prio=10 tid=0x0904e800 nid=0x550 waiting on condition
[0x00000000..0xb7eda060]
   java.lang.Thread.State: RUNNABLE                                       
                   

"Thread-3" prio=10 tid=0x093d8800 nid=0x562 waiting on condition
[0xb5126000..0xb5126120]
   java.lang.Thread.State: TIMED_WAITING (sleeping)                       
              
        at java.lang.Thread.sleep(Native Method)                          
              
        at
ise.plugin.bmp.BufferLocalPlugin$2.run(BufferLocalPlugin.java:111)         
  

"Thread-2" prio=10 tid=0x092bf000 nid=0x561 waiting on condition
[0xb5176000..0xb51770a0]
   java.lang.Thread.State: TIMED_WAITING (sleeping)                       
              
        at java.lang.Thread.sleep(Native Method)                          
              
        at
ise.plugin.bmp.BufferLocalPlugin$1.run(BufferLocalPlugin.java:90)          
  

"TimerQueue" daemon prio=10 tid=0x093ab000 nid=0x55f in Object.wait()
[0xb51d3000..0xb51d4020]
   java.lang.Thread.State: TIMED_WAITING (on object monitor)              
                   
        at java.lang.Object.wait(Native Method)                           
                   
        - waiting on <0x81bbc4d8> (a javax.swing.TimerQueue)              
                   
        at javax.swing.TimerQueue.run(TimerQueue.java:236)                
                   
        - locked <0x81bbc4d8> (a javax.swing.TimerQueue)                  
                   
        at java.lang.Thread.run(Thread.java:619)                          
                   

"AWT-EventQueue-0" prio=10 tid=0x092fe800 nid=0x55c runnable
[0xb5281000..0xb5283f20]
   java.lang.Thread.State: RUNNABLE                                       
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4304)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.match(Pattern.java:4295)          
          
        at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227)     
          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168)     
          
        at java.util.regex.Pattern$Loop.matchInit(Pattern.java:4314)      
          
        at java.util.regex.Pattern$Prolog.match(Pattern.java:4251)        
          
        at
java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3366)          
        at java.util.regex.Pattern$Curly.match0(Pattern.java:3789)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3744)         
          
        at
java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3366)          
        at java.util.regex.Pattern$CharProperty.match(Pattern.java:3345)  
          
        at java.util.regex.Pattern$Curly.match1(Pattern.java:3797)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3746)         
          
        at
java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3366)          
        at java.util.regex.Pattern$Curly.match0(Pattern.java:3789)        
          
        at java.util.regex.Pattern$Curly.match(Pattern.java:3744)         
          
        at java.util.regex.Pattern$Slice.match(Pattern.java:3482)         
          
        at java.util.regex.Matcher.match(Matcher.java:1127)               
          
        at java.util.regex.Matcher.lookingAt(Matcher.java:579)            
          
        at
org.gjt.sp.jedit.syntax.TokenMarker.handleRule(TokenMarker.java:420)      
        at
org.gjt.sp.jedit.syntax.TokenMarker.markTokens(TokenMarker.java:162)      
        at
org.gjt.sp.jedit.buffer.JEditBuffer.markTokens(JEditBuffer.java:1333)     
        at
org.gjt.sp.jedit.textarea.ChunkCache.lineToChunkList(ChunkCache.java:794) 
        at
org.gjt.sp.jedit.textarea.ChunkCache.updateChunksUpTo(ChunkCache.java:676)
        at
org.gjt.sp.jedit.textarea.ChunkCache.getLineInfo(ChunkCache.java:261)     
        at
org.gjt.sp.jedit.textarea.TextArea.recalculateLastPhysicalLine(TextArea.java:5481)
        at
org.gjt.sp.jedit.textarea.DisplayManager.notifyScreenLineChanges(DisplayManager.java:557)
        at
org.gjt.sp.jedit.textarea.DisplayManager.setFirstLine(DisplayManager.java:593)
          
        at
org.gjt.sp.jedit.textarea.TextArea.setFirstLine(TextArea.java:567)         
             
        at
org.gjt.sp.jedit.textarea.TextArea.scrollDownPage(TextArea.java:718)       
             
        at
org.gjt.sp.jedit.textarea.TextArea.goToNextPage(TextArea.java:2486)        
             
        at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)   
                         
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   
        at java.lang.reflect.Method.invoke(Method.java:597)               
                         
        at org.gjt.sp.jedit.bsh.Reflect.invokeMethod(Reflect.java:134)    
                         
        at
org.gjt.sp.jedit.bsh.Reflect.invokeObjectMethod(Reflect.java:80)           
             
        at org.gjt.sp.jedit.bsh.Name.invokeMethod(Name.java:855)          
                         
        at
org.gjt.sp.jedit.bsh.BSHMethodInvocation.eval(BSHMethodInvocation.java:75) 
             
        at
org.gjt.sp.jedit.bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:102)
           
        at
org.gjt.sp.jedit.bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:47)
            
        at org.gjt.sp.jedit.bsh.BSHBlock.evalBlock(BSHBlock.java:130)     
                         
        at org.gjt.sp.jedit.bsh.BSHBlock.eval(BSHBlock.java:80)           
                         
        at org.gjt.sp.jedit.bsh.BshMethod.invokeImpl(BshMethod.java:362)  
                         
        at org.gjt.sp.jedit.bsh.BshMethod.invoke(BshMethod.java:258)      
                         
        at org.gjt.sp.jedit.bsh.BshMethod.invoke(BshMethod.java:186)      
                         
        at
org.gjt.sp.jedit.BeanShellFacade.runCachedBlock(BeanShellFacade.java:225)  
             
        at org.gjt.sp.jedit.BeanShell.runCachedBlock(BeanShell.java:423)  
                         
        at
org.gjt.sp.jedit.BeanShellAction.invoke(BeanShellAction.java:73)           
             
        at
org.gjt.sp.jedit.gui.InputHandler.invokeAction(InputHandler.java:352)      
             
        at
org.gjt.sp.jedit.gui.InputHandler.invokeAction(InputHandler.java:317)      
             
        at
org.gjt.sp.jedit.gui.DefaultInputHandler.handleKey(DefaultInputHandler.java:197)
        
        at
org.gjt.sp.jedit.input.AbstractInputHandler.processKeyEventKeyStrokeHandling(AbstractInputHandler.java:405)
                                                                           
                                   
        at
org.gjt.sp.jedit.gui.InputHandler.processKeyEvent(InputHandler.java:151)   
                            
        at
org.gjt.sp.jedit.textarea.TextArea.processKeyEvent(TextArea.java:4528)     
                            
        at java.awt.Component.processEvent(Component.java:5993)           
                                        
        at java.awt.Container.processEvent(Container.java:2041)           
                                        
        at java.awt.Component.dispatchEventImpl(Component.java:4583)      
                                        
        at java.awt.Container.dispatchEventImpl(Container.java:2099)      
                                        
        at java.awt.Component.dispatchEvent(Component.java:4413)          
                                        
        at
java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1848)
                          
        at
java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:704)
            
        at
java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:969)
         
        at
java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:841)
         
        at
java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:668)
               
        at java.awt.Component.dispatchEventImpl(Component.java:4455)      
                                        
        at java.awt.Container.dispatchEventImpl(Container.java:2099)      
                                        
        at java.awt.Window.dispatchEventImpl(Window.java:2475)            
                                        
        at java.awt.Component.dispatchEvent(Component.java:4413)          
                                        
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)         
                                        
        at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
                      
        at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
                         
        at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
                      
        at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)      
                            
        at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)      
                            
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) 
                                        

"AWT-Shutdown" prio=10 tid=0x092fd000 nid=0x55b in Object.wait()
[0xb52d4000..0xb52d4ea0]
   java.lang.Thread.State: WAITING (on object monitor)                    
              
        at java.lang.Object.wait(Native Method)                           
              
        - waiting on <0x814d3960> (a java.lang.Object)                    
              
        at java.lang.Object.wait(Object.java:485)                         
              
        at sun.awt.AWTAutoShutdown.run(AWTAutoShutdown.java:259)          
              
        - locked <0x814d3960> (a java.lang.Object)                        
              
        at java.lang.Thread.run(Thread.java:619)                          
              

"AWT-XAWT" daemon prio=10 tid=0x0917a800 nid=0x559 runnable
[0xb53d9000..0xb53d9da0]
   java.lang.Thread.State: RUNNABLE                                       
         
        at sun.awt.X11.XToolkit.waitForEvents(Native Method)              
         
        at sun.awt.X11.XToolkit.run(XToolkit.java:548)                    
         
        at sun.awt.X11.XToolkit.run(XToolkit.java:523)                    
         
        at java.lang.Thread.run(Thread.java:619)                          
         

"Java2D Disposer" daemon prio=10 tid=0x09116800 nid=0x558 in Object.wait()
[0xb5450000..0xb5451120]
   java.lang.Thread.State: WAITING (on object monitor)                    
                        
        at java.lang.Object.wait(Native Method)                           
                        
        - waiting on <0x814fb010> (a java.lang.ref.ReferenceQueue$Lock)   
                        
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)   
                        
        - locked <0x814fb010> (a java.lang.ref.ReferenceQueue$Lock)       
                        
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)   
                        
        at sun.java2d.Disposer.run(Disposer.java:125)                     
                        
        at java.lang.Thread.run(Thread.java:619)                          
                        

"Low Memory Detector" daemon prio=10 tid=0x09086c00 nid=0x556 runnable
[0x00000000..0x00000000]
   java.lang.Thread.State: RUNNABLE                                       
                    

"CompilerThread0" daemon prio=10 tid=0x09083800 nid=0x555 waiting on
condition [0x00000000..0xb5a7ea58]
   java.lang.Thread.State: RUNNABLE                                       
                            

"Signal Dispatcher" daemon prio=10 tid=0x09082000 nid=0x554 waiting on
condition [0x00000000..0x00000000]
   java.lang.Thread.State: RUNNABLE                                       
                              

"Finalizer" daemon prio=10 tid=0x0907bc00 nid=0x553 in Object.wait()
[0xb5b66000..0xb5b66ea0]
   java.lang.Thread.State: WAITING (on object monitor)                    
                  
        at java.lang.Object.wait(Native Method)                           
                  
        - waiting on <0x814cfb28> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
        - locked <0x814cfb28> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
        at
java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)

"Reference Handler" daemon prio=10 tid=0x09077400 nid=0x552 in
Object.wait() [0xb5bb7000..0xb5bb7e20]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x814cfbb0> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:485)
        at
java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
        - locked <0x814cfbb0> (a java.lang.ref.Reference$Lock)

"VM Thread" prio=10 tid=0x09075800 nid=0x551 runnable

"VM Periodic Task Thread" prio=10 tid=0x0909a800 nid=0x557 waiting on
condition

JNI global references: 1552

Heap
 def new generation   total 3520K, used 2897K [0x80110000, 0x804e0000,
0x814c0000)
  eden space 3136K,  89% used [0x80110000, 0x803ce428, 0x80420000)
  from space 384K,  22% used [0x80420000, 0x804360c8, 0x80480000)
  to   space 384K,   0% used [0x80480000, 0x80480000, 0x804e0000)
 tenured generation   total 46396K, used 43262K [0x814c0000, 0x8420f000,
0x90110000)
   the space 46396K,  93% used [0x814c0000, 0x83eff980, 0x83effa00,
0x8420f000)
 compacting perm gen  total 12288K, used 6606K [0x90110000, 0x90d10000,
0x94110000)
   the space 12288K,  53% used [0x90110000, 0x90783b30, 0x90783c00,
0x90d10000)
    ro space 8192K,  74% used [0x94110000, 0x94708b48, 0x94708c00,
0x94910000)
    rw space 12288K,  58% used [0x94910000, 0x95023df0, 0x95023e00,
0x95510000)


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

Comment By: Dale Anson (daleanson)
Date: 2009-06-18 17:34

Message:
I see the same problem with this file using the latest jEdit 4.3pre17 from
SVN.

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

Comment By: Sergey Zhumatiy (sergzhum)
Date: 2009-06-18 17:10

Message:
I use jedit 4.3pre16, linux Ubuntu Jaunty, sun java 6.

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

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

Feature Requests item #2814425, was opened at 2009-06-30 10:10
Message generated for change (Tracker Item Submitted) made by foolo
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350588&aid=2814425&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: olof andersson (foolo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Verilog (*.v) highlighting even for SystemVerilog (*.sv)

Initial Comment:
When opening systemverilog files, there is no highliting at all.
However, the syntax of Verilog and SystemVerilog are almost identical, so the already-existing verilog highlighting could be used for SystemVerilog aswell.
(proposed soulution:  Add *.sv as a verilog extension)
//Olof Andersson, Linköpings University, Sweden

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

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

Feature Requests item #1653057, was opened at 2007-02-06 08:52
Message generated for change (Comment added) made by goebbe
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350588&aid=1653057&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: goebbe (goebbe)
Assigned to: Nobody/Anonymous (nobody)
>Summary: feature request: extend possibilites of regexp

Initial Comment:
The following feature request is the outcome of bug:
"[ 1094078 ] Repeated REGEXP per line"

If I understood right than the regexp-feature for syntax-highlighting has the following properties:
1. don't expand over more than two line
2. don't allow overlapping sequences (end sequence is ignored for the next matching expression)

I would like to have the possibility (optional) to: 
- span over more than one line and (option1)
- allow for overlapping sequences in the text (option2)

Use case: I tried to implement syntax highlighting for SAS-statistics package. With the present feature set of  Jedit I couldn't implement the underlying rules.

Here is a short description of the syntax highlighting for SAS:

Test case:
3*4+4; *comment1; 3*4*4; *comment2; *comment3;*comment4;		
3 * 4 + 4 ; *comment1; 3 * 4 + 4 ; *comment2; 	
*
comment3
;
      *comment4; this is * no comment;

Now I try to describe expected behaviour with my own words:
If there is only space (only space and/or newline) between the last ";"
sign and 
the "*" sign, then the "*" sign starts a multi-line comment. The end of
the comment is always the next ";" sign.

>From the comment on bug  1094078 I concluded that at the moment it is not possible to define corresponding rules in Jedit.



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

>Comment By: goebbe (goebbe)
Date: 2009-06-30 07:52

Message:
Most of the cases that are described in the example above (for the SAS
language) are solved now, by using Jedit syntax highlighting and regexp.
See bug: 
http://sourceforge.net/tracker/?func=detail&atid=300588&aid=2793540&group_id=588

However there are some cases for the described range comments that cannot
be implemented by Jedit syntax highlighting. 
I will attach a testfile (for SAS-mode) that contain such cases, in order
to illustrate the problems. 

As described above the feature request boils down to (optionally) allow
the regexp feature in syntax-highlighting to: 
- span over more than one line and (option1)
- allow for overlapping sequences in the text (option2)


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

Comment By: goebbe (goebbe)
Date: 2007-09-24 17:29

Message:
Logged In: YES 
user_id=1050273
Originator: YES

I am grateful to Redoute to provide the following code which is able to 
reproduce the correct highlighting for the SAS-rules.

However I tried to implement a more complete highlighting mode for SAS
and
failed when I tried to implement HIGHLIGHT_DIGITS="TRUE" and KEYWORDS
since the
first keyword or digit is not recognised when the "COMMAND" rules apply.

Possibly this is due to my limited knowledge of Java/Jedit but I suspect
this is due to the design
of syntax highlighting in Jedit.
I would be glad if anybody knows a solution to this within the current
Jedit syntax highlighting
possibilities.

Anyway here is the code from Redoute which produces correct
SAS-highlighting. Just in case somebody
can live without coherent keyword-highlighting and digit highlighting,
this might be useful:

<?xml version="1.0"?>
<!DOCTYPE MODE SYSTEM "xmode.dtd">
<MODE>
   <RULES>
      <SEQ TYPE="COMMENT1" DELEGATE="COMMENT">*</SEQ>
      <SEQ_REGEXP TYPE="KEYWORD1"
      DELEGATE="COMMAND">\S</SEQ_REGEXP> 
   </RULES>
   <RULES SET="COMMENT" DEFAULT="COMMENT1">
      <SEQ TYPE="OPERATOR" DELEGATE="MAIN">;</SEQ>
   </RULES>
   <RULES SET="COMMAND" DEFAULT="KEYWORD1">
      <SEQ TYPE="OPERATOR" DELEGATE="MAIN">;</SEQ>
   </RULES>
</MODE>


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

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

Bugs item #1094078, was opened at 2005-01-01 15:03
Message generated for change (Comment added) made by goebbe
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1094078&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: text area and syntax packages
Group: None
Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: goebbe (goebbe)
Assigned to: Nobody/Anonymous (nobody)
Summary: Repeated REGEXP per line

Initial Comment:
Hello,
I tried to extend the SAS edit mode in the following way:
everything between a * and a ; is a comment if there is
only white space between the preceding ; (in the same
line) and the beginning * .

Example:
i=3*j; *comment1; *comment2;

Here I want the signs till the first ; not to be
considered as comment. The two following parts between
* and ; should be considered as comments since there is
white space between the preceding ; and the *.

I defined the following RULE with the SPAN_REGEXP command:
<SPAN_REGEXP TYPE="COMMENT1" HASH_CHAR=";">
<BEGIN>[;][[:space:]]+[*]</BEGIN>
<END>;</END>
</SPAN_REGEXP>

but highlighting works only for the first comment in
the line. Somehow the ending ; of the first comment is
not considered as the begin of  the new comment.
When I introduce a second ; in my example like follows:
i=3*j; *comment1;; *comment2;
both comments are considered.

Thanks a lot for Jedit.

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

Comment By: goebbe (goebbe)
Date: 2009-06-30 07:43

Message:
Just for the record: 
Finally I found a solution to cover most of the described cases.
The file has already been submitted in svn, see: 
http://sourceforge.net/tracker/?func=detail&atid=300588&aid=2793540&group_id=588

Attached to this bug there is also an extended list of test cases - that
contains some remaining cases that are not yet covered.

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

Comment By: goebbe (goebbe)
Date: 2007-02-06 08:55

Message:
Logged In: YES 
user_id=1050273
Originator: YES

Thanks a lot for your answer!

I submitted a feature request: bug [ 1653057 ] 

And I will close this bug.


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

Comment By: Robert Schwenn (rschwenn)
Date: 2007-02-05 23:21

Message:
Logged In: YES 
user_id=1486645
Originator: NO

What rules! ;-)
Now that I (hopefully) understand Your goal, I can't find a solution. But
here are two points:

1. For all of the RegExp-variants of mode definition tags the help says:
"The regular expression match cannot span more than one line". So, though
it's not very nice, ignoring of NewLines is not a bug - its by design.

2. As You decribed: The tags "SPAN", "SPAN_REGEXP", "SEQ" and "SEQ_REGEXP"
cannot match overlapping sequences of text. And I'm afraid this is by
design too :-(

=> So, Your're completely right, but this seems not to be a report of an
existing bug in jEdit 4.2final or 4.3pre9.
May be these things should be filed as feature reqests (not sure about the
chance to get it realized). 


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

Comment By: goebbe (goebbe)
Date: 2007-02-05 14:15

Message:
Logged In: YES 
user_id=1050273
Originator: YES

I guess that I have to complete the test-cases to show what I mean:

3*4+4; *comment1; 3*4*4; *comment2; *comment3;*comment4;		
3 * 4 + 4 ; *comment1; 3 * 4 + 4 ; *comment2; 	
*
comment3
;
      *comment4; this is * no comment;

Now I try to describe expected behaviour with my own words:
If there is only space (only space and/or newline) between the last ";"
sign and 
the "*" sign, then the "*" sign starts a multi-line comment. The end of
the comment is always the next ";" sign.		

Is it possible to define a command with regexp in Jedit which satisfies
this description and 
which works with the given test-cases (i.e. also with more than one
comment per line)?	

In the original bug-report I try to come up with a solution but if fails
since it seems that the
";" which end a preceding comment is not considered for the regexp for the
a following comment. Consequently comment three and four in the first line
of the new test-cases would not be considered.

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

Comment By: Robert Schwenn (rschwenn)
Date: 2007-02-04 23:16

Message:
Logged In: YES 
user_id=1486645
Originator: NO


I can't see the bug. 
One of the following definitions does the job in both jEdit 4.2final and
4.3pre9. 

1.
<SPAN_REGEXP TYPE="COMMENT1" HASH_CHAR=" ">
	<BEGIN> +\*</BEGIN>
	<END>;</END>
</SPAN_REGEXP>

2.
<!--<SPAN TYPE="COMMENT1">
	<BEGIN> *</BEGIN>
	<END>;</END>
</SPAN>-->




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

Comment By: goebbe (goebbe)
Date: 2005-02-01 15:57

Message:
Logged In: YES 
user_id=1050273

Thanks a lot malyvelky.
It seems like Jedit is not able  to-do the requested task at
it's present state.
I could not figure out how to specify only one
regexp-condition to describe what should be a comment within
Jedit. The
Begin-regexp
End-regexp
structure seems to be fundamental.

Perhaps the parsing-mechanism for regexp should already
start before the end of the preceeding expression (e.g. in
the middle of a comment)?
Perhaps as an option?

Another thing I remarked:
The \n seems also to be ignored when it is put at a
end-condition like follows:
<END>\n</END>
The . is interpreted literally and not like in the
documentation:
<END>.</END>
But perhaps I just don't understand how regexp work?

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

Comment By: Jakub Holý (malyvelky)
Date: 2005-02-01 09:42

Message:
Logged In: YES 
user_id=1046780

Actually, the regexp should actually be
"[*](([^;])|(;\\s+[*]))+;" (and I found java.util.regex
doesn't like [[:space:]] so I replaced it with \\s (or \s if
no need to ecape it)).

If you don't wont line breaks in you comments use:
"[*](([^;\\n])|(;\\s+[*]))+;" 

You definition was "everything between * and ; is a comment"
which applies to *j; in i=3*j too. RegExp cannot distinguish
formulas from other text. You'd need to precise the
condition of comment start (e.g. "no preceeding literal = ...").

If jEdit only let's you define the beginning and end I'm
afraid there's no solution.

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

Comment By: goebbe (goebbe)
Date: 2005-01-29 16:23

Message:
Logged In: YES 
user_id=1050273

Thanks malyvelky,

I played a bit with the regexp - but it didn't work
for me.
Two problems appear :
Either the * in the formula is already considered as the
start of the comment (which should not be the case)
or the end of the comment is not considered like it should -
one the comment starts everything till the end of the document
is considered as a comment.

If I understand right, Jedit allows to specify only the
begin and the end of a comment. 

Here is a more fancy examples for which the comments
don't work:
i=3*j; *comment1;  i=3*j; *comment2; *
comment3;
*comment4; i=3*j
;



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

Comment By: Jakub Holý (malyvelky)
Date: 2005-01-29 14:11

Message:
Logged In: YES 
user_id=1046780

Hi,
 i don't know much about regexps in edit modes but it seems
to me that when jEdit matches the 1st comment '*comment1;' 
it doesn't consider its characters anymore when matching the
rest of the line.
Solution:
Modify your RegExp to match the whole command line, not the
beginning of a subsequent comment. It means you should
modify regexp for the END of a comment as follows:
"End is a ';' not followed by whitespaces and '*'"
A normal RegExp to match such a comment would be ((begin)
(body) (end)):
([*])(([^;]*)|((;[[:space:]]+[*])*))*(;)

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

Comment By: goebbe (goebbe)
Date: 2005-01-01 15:11

Message:
Logged In: YES 
user_id=1050273

Sorry I should add the follwing information:
I use Jedit 4.2final with SUN 1.5.0 JRE on Windows2000pro

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

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

Bugs item #1436322, was opened at 2006-02-22 01:34
Message generated for change (Comment added) made by goebbe
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1436322&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: text area and syntax packages
Group: minor bug
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: SAS Highlighting (multiline REGEXP)

Initial Comment:
The SAS editing mode does not correctly support SAS 
comments. The following line will not be highlighted:

*This is a comment;

Furthermore, these types of comments can span multiple 
lines, and do not necessarily start and the beginning 
of line:
i=3*2; *multi-line
comment; *comment;

Since SPAN_REGEXP does not support multiline matches, I 
do not believe there is not way to fix this currently.

Note that in my experience, the multi-line version of 
this comment is not used ofter (/* */ is used instead). 
I propose the following rule to be added to sas.xml to 
correctly highlight some of these comments:

<SPAN TYPE="COMMENT2" AT_LINE_START="TRUE">
  <BEGIN>*</BEGIN>
  <END>;</END>
</SPAN>

This should correctly highlight the following as a 
comment. Current sas.xml does not, and botches the rest 
of the file (unclosed quote):
*Don't use apostrophes!;

- Xavier (xavier AT noreality [D] net)
jEdit 4.3pre3

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

Comment By: goebbe (goebbe)
Date: 2009-06-30 07:36

Message:
The SAS-mode has received a major rework and has just been submitted: 
http://sourceforge.net/tracker/?func=detail&atid=300588&aid=2793540&group_id=588

The *comment; -types of comments have been implemented for a wide range of
use cases.
This includes the following cases: 
* comment; var= 3 * x ; * comment;
*comment; * comment; var= 3 * x 
var=3 *x; *comment; *comment;

I suggest to close this bug, since the described bug is solved.
 

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

Comment By: goebbe (goebbe)
Date: 2007-09-24 17:08

Message:
Logged In: YES 
user_id=1050273
Originator: NO

I propose to include something similar to the suggested change - even
though this will not work in all 
cases described in feature request #1653057.

The following important (for SAS-programming only) case is covered:
If you have some command in a SAS-programme, as:
command;

Then you can just comment this line out by putting a "*" sign at the start
of the line.
*commented command;

Limitations of the proposed change:
- Note that these type of comments in SAS can normally span multi-line
comments. The requested extension does not cover the case of multi-line
comments of this kind. See bug #14363222 for a discussion.
- multiple comments per line are not highlighted correctly.

Note: Multiple comments per line could be possible if some regexp-guru
could define a rule which makes sure that there is either no space between
the last ; and the *  OR only white space between the last ; and the *

Despite the limitations the proposed extension of the SAS-mode would allow
correct highlighting for an important subcase.

The following modification of the suggestion would also allow white space
before the first comment in a line: 
<SPAN TYPE="COMMENT1" AT_WHITESPACE_END="TRUE" EXCLUDE_MATCH="FALSE">
  <BEGIN>*</BEGIN>
  <END>;</END>
</SPAN>

This would cover for example the following cases:
no comment;
 no comment;
*comment; 
 *comment;


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

Comment By: Robert Schwenn (rschwenn)
Date: 2007-02-15 21:00

Message:
Logged In: YES 
user_id=1486645
Originator: NO

In feature request #1653057
(http://sourceforge.net/tracker/index.php?func=detail&aid=1653057&group_id=588&atid=350588)
a SAS-comment was defined as follows:

If there is only space (only space and/or newline) between the last ";"
sign and the "*" sign, then the "*" sign starts a multi-line comment. The
end of the comment is always the next ";" sign.

It this was correct, Your proposal would highlight a line that is not a
comment, because there's no semicolon and optional whitespace before the
"*".

What to do?


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

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

Bugs item #2814318, was opened at 2009-06-29 18:38
Message generated for change (Tracker Item Submitted) made by basilbourque
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=2814318&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: Basil Bourque (basilbourque)
Assigned to: Nobody/Anonymous (nobody)
Summary: Status bar clock does not respect host OS format

Initial Comment:
On Windows XP SP3 running Java 1.6.0_14-b08 with jEdit 4.3pre16:

I have Windows Region and Language Options set to show time in 24-hour clock instead of the usual US 12-hour clock.

jEdit does not pick up on this setting. The status bar of jEdit shows 12-hour time.

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

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

Patches item #2787012, was opened at 2009-05-04 20:47
Message generated for change (Comment added) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300588&aid=2787012&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: James Nicholl (jnicholl17)
Assigned to: Nobody/Anonymous (nobody)
Summary: plain TeX edit mode

Initial Comment:
Syntax highlighting for plain TeX as described in the TeXbook by Knuth.

I work with this file open, so it may never be totally complete, but I've got it to the point that it is useful. The vocabulary is very large and categorized very well. There are some things I would like to do still, including further refining the categorization, and implementing the detection of macros that are invalid in math mode. A modified version for pdfTeX will probably arise naturally over the course of my work.

It needs further refinement, but what is there is very well done. I would like some feedback from the community if this is a worthwhile side project for me to pursue.

I included the catalog entry, but I'm not sure if it works. In fact, I'm pretty sure it doesn't., at least not from within jEdit 4.3 pre16. I just cut and paste the catalog entry from another mode submission. I don't understand why it doesn't work, or how it's supposed to work... It works well if you rename it latex.xml then overwrite the existing edit mode.

Advice on fixing this situation would be appreciated.

James Nicholl

 jni...@ya...

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

>Comment By: Alan Ezust (ezust)
Date: 2009-06-29 16:10

Message:
what do you suggest the file name glob/first name glob should be? If we
currently have a mode for latex which uses the .tex extension, will we want
to associate this mode with any filename extension?


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

Comment By: James Nicholl (jnicholl17)
Date: 2009-05-04 20:50

Message:
There is lengthy documentation for this highlighting package in the header
of the xml file.

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

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

Plugin Patches item #2766272, was opened at 2009-04-15 12:33
Message generated for change (Comment added) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=997937&aid=2766272&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: 5
Private: No
Submitted By: Matthew Gilbert (voxmea)
Assigned to: Nobody/Anonymous (nobody)
Summary: Updates the tags plugin to use PositionChanging

Initial Comment:
Updates the tags plugin to use PositionChanging instead of CaretChanging.

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

>Comment By: Alan Ezust (ezust)
Date: 2009-06-29 16:08

Message:
I think someone already applied this.


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

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

Plugin Patches item #2659553, was opened at 2009-03-03 18:28
Message generated for change (Comment added) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=997937&aid=2659553&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: Nigel Tamplin (nigelt)
Assigned to: Nobody/Anonymous (nobody)
Summary: AntFarm: Option to control focus after task completion

Initial Comment:
This is a fulfillment of feature request

http://sourceforge.net/tracker/index.php?func=detail&aid=2659532&group_id=588&atid=997936

AntFarm now has an option to control whether it grabs focus after running a task.

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

>Comment By: Alan Ezust (ezust)
Date: 2009-06-29 16:04

Message:
Moving this to plugin patches. 
Antfarm has no current maintainer. Would you like to assist in closing
some other bugs too?


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

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

Patches item #2653404, was opened at 2009-03-01 18:55
Message generated for change (Settings changed) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300588&aid=2653404&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: Uwe (donovaly)
Assigned to: Nobody/Anonymous (nobody)
>Summary: update for the nsis2 mode

Initial Comment:
Attached is an update for the nsis2.xml plugin.

There is a new NSIS2 keyword.

Attached is a patch to current nsis2.xml and the patched nsis2.xml.

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

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

Patches item #2811404, was opened at 2009-06-24 02:30
Message generated for change (Comment added) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300588&aid=2811404&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: Olivier Chafik (opentator)
Assigned to: Nobody/Anonymous (nobody)
Summary: "Whole word" search option

Initial Comment:
Right now is a pain to look for variable "i" in jEdit, as a plain text search will match all occurrences of "i" inside words.
Using a carefully crafted regex can provide a workaround but is not user-friendly (e.g. "(^|\W)i($|\W)").
Many other editors support a "whole word" search option that does the job.

This patch adds this checkbox to both the search dialog and the search bar in both plain text and regex search.
Compatible with the ignore case option.
Reverse search mode only supported for plain text search for now, I need help to debug the reverse + wholeWord + regex mode.

jEdit rulez !

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

>Comment By: Alan Ezust (ezust)
Date: 2009-06-29 16:02

Message:
Wow, the second patch that offers this. See # 1905574.

XSearch plugin has it too, by the way, and since I use XSearch most of the
time, I don't miss this patch.
But I suppose either this one or the other one should be rolled into core
at some point after some review.



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

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

Patches item #2793540, was opened at 2009-05-18 13:44
Message generated for change (Settings changed) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300588&aid=2793540&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: 5
Private: No
Submitted By: goebbe (goebbe)
Assigned to: Alan Ezust (ezust)
Summary: updated edit mode for SAS

Initial Comment:
The attached file contains a small update for the latest version of SAS edit mode that has been updated by ezust in revision 15306.

The update only concerns range comments that start with * and that end with ;  
Previous versions (revision 15306) did not allow rows of these range comments. The new version allows up to two range comments of these type in a row - this is likely to cover all common use-cases. 

In order to implement this I define a new comment2 that defines a "full range-comment plus the start of the second range comment" as the beginning of the second range comment. 
This is the first time that I use regexp seriously - so please check carefully. 

I will also attach a file with testcases that are now all covered.

Note that I do not intend to implement more than two comment2 range comments in a row since this seems not worth the effort - and computation time.  
  

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

>Comment By: Alan Ezust (ezust)
Date: 2009-06-29 15:23

Message:
Transmitting file data .
Committed revision 15611.


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

Comment By: goebbe (goebbe)
Date: 2009-06-29 15:14

Message:
@ezust:
The remaining cases in attached sas_comment_test.sas file cannot be
covered easily within Jedit.
Since the latest version of sas.xml fixes most of the missing cases at
least compared to the version that is currently in svn I suggest to apply
the changes.

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

Comment By: goebbe (goebbe)
Date: 2009-05-19 02:29

Message:
O.k. now I also checked some rather complicated real-world examples - and I
did not 
find any issues. 

@ezust: I suggest to submit this version to complete the clean up of the
SAS-edit mode.

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

Comment By: goebbe (goebbe)
Date: 2009-05-19 02:05

Message:
Seems that the first version did no cover the case of two range comments at
the start of a line. The new upload fixed this. 

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

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

Patches item #2793540, was opened at 2009-05-18 20:44
Message generated for change (Comment added) made by goebbe
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300588&aid=2793540&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: goebbe (goebbe)
Assigned to: Alan Ezust (ezust)
Summary: updated edit mode for SAS

Initial Comment:
The attached file contains a small update for the latest version of SAS edit mode that has been updated by ezust in revision 15306.

The update only concerns range comments that start with * and that end with ;  
Previous versions (revision 15306) did not allow rows of these range comments. The new version allows up to two range comments of these type in a row - this is likely to cover all common use-cases. 

In order to implement this I define a new comment2 that defines a "full range-comment plus the start of the second range comment" as the beginning of the second range comment. 
This is the first time that I use regexp seriously - so please check carefully. 

I will also attach a file with testcases that are now all covered.

Note that I do not intend to implement more than two comment2 range comments in a row since this seems not worth the effort - and computation time.  
  

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

>Comment By: goebbe (goebbe)
Date: 2009-06-29 22:14

Message:
@ezust:
The remaining cases in attached sas_comment_test.sas file cannot be
covered easily within Jedit.
Since the latest version of sas.xml fixes most of the missing cases at
least compared to the version that is currently in svn I suggest to apply
the changes.

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

Comment By: goebbe (goebbe)
Date: 2009-05-19 09:29

Message:
O.k. now I also checked some rather complicated real-world examples - and I
did not 
find any issues. 

@ezust: I suggest to submit this version to complete the clean up of the
SAS-edit mode.

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

Comment By: goebbe (goebbe)
Date: 2009-05-19 09:05

Message:
Seems that the first version did no cover the case of two range comments at
the start of a line. The new upload fixed this. 

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

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

I just moved it back. That's where I put it originally, and vampire moved it
out into its own project, but that was before the plugins in jars/ used it.

I'm going to remove the build-support top-level directory now.


On Thu, Jun 25, 2009 at 12:16 PM, Shlomy Reinstein <sre...@gm...>wrote:

> From what I know, the 'build-support' directory is a sibling of
> 'jEdit' and 'plugins', and it's been that way for a very long time. Am
> I out-of-date? :)
> Shlomy
>
> On Thu, Jun 25, 2009 at 9:22 PM, Alan Ezust<ala...@gm...> wrote:
> > build-support has been moved around a bit in svn. I don't like its
> current
> > location. For one thing, there is no need to have branches/tags/trunk
> there,
> > since it is never going to be "released" or branched.
> >
> > At one time, it was under the jedit source tree.
> >
> > Now it seems, the build.xml of jedit itself does depend on build-support
> > files to build the plugins, so I think it might be a good idea to move it
> > into the jedit source tree, so that any time someone checks it out from
> svn,
> > they already have it.
> >
> > What do you think?
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> >
> > --
> > -----------------------------------------------
> > jEdit Developers' List
> > jEd...@li...
> > https://lists.sourceforge.net/lists/listinfo/jedit-devel
> >
> >
>

Plugin Bugs item #2813701, was opened at 2009-06-29 01:59
Message generated for change (Comment added) made by kerik-sf
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=565475&aid=2813701&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
Private: No
Submitted By: Greg Knittl (gknittl)
Assigned to: Nobody/Anonymous (nobody)
Summary: XMLPlugin XercesParserImpl.endElement() invalid prefix

Initial Comment:
relax-ng branch.
I am trying to use http://www.w3.org/2007/schema-for-xslt20.xsd.
elements taken from this schema show up with an extra : in the completion list, e.g. xsl::for-each
I have traced this to XercesParserImpl.endElement()
//get the prefix
String prefix=qName.substring(0,qName.length()-sName.length());
gets the prefix and the following :
It should be something like:
String prefix;
if (qName.length() == sName.length())
	prefix = "";
else
prefix=qName.substring(0,qName.length()-sName.length()-1);


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

>Comment By: kerik (kerik-sf)
Date: 2009-06-29 20:43

Message:
Bah : my mistake ! thanks for reporting.
fixed in r15604

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

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

I think it's time to remove the old plugins/XML/trunk and move
branches/relax-ng to trunk.
If I do that, then we all need to stop using that old branch at the same
time.

Any objections?

>
>> I think the same goes with plugin dockables - currently a dockable
>> will be in the plugin menu only if it's explicitly specified on the
>> menu of the plugin in the props file. If it is not specified there, it
>> will only be in Global Options -> Docking (or otherwise available as
>> actions, but who knows the available actions...).
>
>
> It is the responsibility of the plugin designer to add actions to the
> plugin menu.
>

And, you can see all the actions for the plugin in the Shortcuts option
pane.

That was my thought.

On Mon, Jun 29, 2009 at 4:13 AM, Romain Francois <rom...@db...
> wrote:

> This is a great idea.
> What do you call "macros in any of the supported macro languages" ? Do you
> refer to the ScriptEngine plugin ?
>

On Mon, Jun 29, 2009 at 1:23 AM, Shlomy Reinstein <sre...@gm...>wrote:

> Just a small question, where would you place plugin macros in the menus?
> Create a new "plugins" sub-menu under "macros", or a "macros" sub-menu
> under each plugin's menu, or something else (e.g. append them
> automatically to the end of the plugin menu, with a separator)?
>

The menus can be determined by the .menu properties as they currently are.
Nothing needs to be changed there.

All the support of  macros in a plugin jar  needs to do is cause jedit to
scan the jar for macros, and define the actions in the same action group as
the plugin's other actions from actions.xml.


> I think the same goes with plugin dockables - currently a dockable
> will be in the plugin menu only if it's explicitly specified on the
> menu of the plugin in the props file. If it is not specified there, it
> will only be in Global Options -> Docking (or otherwise available as
> actions, but who knows the available actions...).


It is the responsibility of the plugin designer to add actions to the plugin
menu.


>
>
> Shlomy
>
> On Mon, Jun 29, 2009 at 9:28 AM, Eric Berry<el...@gm...> wrote:
> > I love this idea!
> >
> > +1 from me!
> >
> > On Fri, Jun 26, 2009 at 10:19 AM, Alan Ezust <ala...@gm...>
> wrote:
> >>
> >> Slightly related to an earlier thread about modes being supplied by
> >> plugins,
> >> I think that plugins should also be able to provide actions that are
> >> specified as
> >> beanshell macros (or perhaps macros in any of the supported macro
> >> languages),
> >> instead of being forced to put code in an XML file.
> >>
> >> If a plugin provides these scripts in a "macros" directory, I think that
> >> each of these scripts should be added as an action to the actionset of
> that
> >> plugin, as if it was appearing between <code> and </code> elements in
> the
> >> actions.xml.
> >>
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >>
> >> --
> >> -----------------------------------------------
> >> jEdit Developers' List
> >> jEd...@li...
> >> https://lists.sourceforge.net/lists/listinfo/jedit-devel
> >>
> >
> >
> >
> > --
> > Learn from the past. Live in the present. Plan for the future.
> > 11101000
> > http://www.townsfolkdesigns.com/blogs/elberry
> >
> >
> ------------------------------------------------------------------------------
> >
> > --
> > -----------------------------------------------
> > jEdit Developers' List
> > jEd...@li...
> > https://lists.sourceforge.net/lists/listinfo/jedit-devel
> >
> >
>

This is a great idea.
What do you call "macros in any of the supported macro languages" ? Do 
you refer to the ScriptEngine plugin ?

Romain

On 06/29/2009 10:23 AM, Shlomy Reinstein wrote:
> Just a small question, where would you place plugin macros in the menus?
> Create a new "plugins" sub-menu under "macros", or a "macros" sub-menu
> under each plugin's menu, or something else (e.g. append them
> automatically to the end of the plugin menu, with a separator)?
>
> I think the same goes with plugin dockables - currently a dockable
> will be in the plugin menu only if it's explicitly specified on the
> menu of the plugin in the props file. If it is not specified there, it
> will only be in Global Options ->  Docking (or otherwise available as
> actions, but who knows the available actions...).
>
> Shlomy
>
> On Mon, Jun 29, 2009 at 9:28 AM, Eric Berry<el...@gm...>  wrote:
>    
>> I love this idea!
>>
>> +1 from me!
>>
>> On Fri, Jun 26, 2009 at 10:19 AM, Alan Ezust<ala...@gm...>  wrote:
>>      
>>> Slightly related to an earlier thread about modes being supplied by
>>> plugins,
>>> I think that plugins should also be able to provide actions that are
>>> specified as
>>> beanshell macros (or perhaps macros in any of the supported macro
>>> languages),
>>> instead of being forced to put code in an XML file.
>>>
>>> If a plugin provides these scripts in a "macros" directory, I think that
>>> each of these scripts should be added as an action to the actionset of that
>>> plugin, as if it was appearing between<code>  and</code>  elements in the
>>> actions.xml.
>>>
>>>        

-- 
Romain Francois
Independent R Consultant
+33(0) 6 28 91 30 30
http://romainfrancois.blog.free.fr

Just a small question, where would you place plugin macros in the menus?
Create a new "plugins" sub-menu under "macros", or a "macros" sub-menu
under each plugin's menu, or something else (e.g. append them
automatically to the end of the plugin menu, with a separator)?

I think the same goes with plugin dockables - currently a dockable
will be in the plugin menu only if it's explicitly specified on the
menu of the plugin in the props file. If it is not specified there, it
will only be in Global Options -> Docking (or otherwise available as
actions, but who knows the available actions...).

Shlomy

On Mon, Jun 29, 2009 at 9:28 AM, Eric Berry<el...@gm...> wrote:
> I love this idea!
>
> +1 from me!
>
> On Fri, Jun 26, 2009 at 10:19 AM, Alan Ezust <ala...@gm...> wrote:
>>
>> Slightly related to an earlier thread about modes being supplied by
>> plugins,
>> I think that plugins should also be able to provide actions that are
>> specified as
>> beanshell macros (or perhaps macros in any of the supported macro
>> languages),
>> instead of being forced to put code in an XML file.
>>
>> If a plugin provides these scripts in a "macros" directory, I think that
>> each of these scripts should be added as an action to the actionset of that
>> plugin, as if it was appearing between <code> and </code> elements in the
>> actions.xml.
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> --
>> -----------------------------------------------
>> jEdit Developers' List
>> jEd...@li...
>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>
>
>
>
> --
> Learn from the past. Live in the present. Plan for the future.
> 11101000
> http://www.townsfolkdesigns.com/blogs/elberry
>
> ------------------------------------------------------------------------------
>
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>
>

I love this idea!

+1 from me!

On Fri, Jun 26, 2009 at 10:19 AM, Alan Ezust <ala...@gm...> wrote:

> Slightly related to an earlier thread about modes being supplied by
> plugins,
> I think that plugins should also be able to provide actions that are
> specified as
> beanshell macros (or perhaps macros in any of the supported macro
> languages),
> instead of being forced to put code in an XML file.
>
> If a plugin provides these scripts in a "macros" directory, I think that
> each of these scripts should be added as an action to the actionset of that
> plugin, as if it was appearing between <code> and </code> elements in the
> actions.xml.
>
>
>
>
> ------------------------------------------------------------------------------
>
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>
>


-- 
Learn from the past. Live in the present. Plan for the future.
11101000
http://www.townsfolkdesigns.com/blogs/elberry