jedit-devel Mailing List for jEdit

Bugs item #409740, was opened at 2001-03-19 06:32
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=100588&aid=409740&group_id=588

Category: text area and syntax packages
Group: None
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Word Wrap Is Too Zealous

Initial Comment:
The word wrap feature is annoying when working with source code.  I am working with a Perl file, 
and JEdit keeps on breaking my end of line comments onto a new line.

I have set the word wrap width to 20000, that did not work.  so i tried 0, and i got the same 
result.

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

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

Done.

On Fri, Jun 29, 2001 at 01:41:35PM +0200, Dirk Moebius wrote:
> Hi Slava,
> 
> on the download pages, the link "Latest development version: 3.2pre4" at the
> top of the page links to NEWS31.txt instead of NEWS32.txt.
> 
> But what I would like better is that it links to the detailled ChangeLog of
> the current version. Could you please change that?
> 
> Thanks,
> Dirk.
> 
> -- 
> GMX - Die Kommunikationsplattform im Internet.
> http://www.gmx.net
> 
> --
> GMX Tipp:
> 
> Machen Sie Ihr Hobby zu Geld bei unserem Partner 1&1!
> http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a
> 
> 
> -- 
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> http://lists.sourceforge.net/lists/listinfo/jedit-devel

Dirk,

Unfortunately, HTML does allow tags inside <pre> tags, so this change
would make the syntax highlighting rather misleading.

Slava

On Fri, Jun 29, 2001 at 12:27:17PM +0200, Dirk Moebius wrote:
> Hi,
> 
> would it be possible to change the java mode file, so that text inside <pre>
> tags in JavaDoc comments is _not_ highlighted as html?
> 
> E.g. the following:
> 
> 1) change java.xml, so that javadoc comments do not delegate to xml:TAGS,
> but to html:TAGS.
> 2) change html.xml, so that <pre> tags delegate to text.xml
> 
> I don't know enough about the delegate mechanism. Is it possible?
> 
> Thank,
> Dirk.
> 
> -- 
> GMX - Die Kommunikationsplattform im Internet.
> http://www.gmx.net
> 
> --
> GMX Tipp:
> 
> Machen Sie Ihr Hobby zu Geld bei unserem Partner 1&1!
> http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a
> 
> 
> -- 
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> http://lists.sourceforge.net/lists/listinfo/jedit-devel

Hi Slava,

on the download pages, the link "Latest development version: 3.2pre4" at the
top of the page links to NEWS31.txt instead of NEWS32.txt.

But what I would like better is that it links to the detailled ChangeLog of
the current version. Could you please change that?

Thanks,
Dirk.

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

--
GMX Tipp:

Machen Sie Ihr Hobby zu Geld bei unserem Partner 1&1!
http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a

Hi,

would it be possible to change the java mode file, so that text inside <pre>
tags in JavaDoc comments is _not_ highlighted as html?

E.g. the following:

1) change java.xml, so that javadoc comments do not delegate to xml:TAGS,
but to html:TAGS.
2) change html.xml, so that <pre> tags delegate to text.xml

I don't know enough about the delegate mechanism. Is it possible?

Thank,
Dirk.

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

--
GMX Tipp:

Machen Sie Ihr Hobby zu Geld bei unserem Partner 1&1!
http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a

Hi Sergey,

> There is one question about beautifiers:
> Currently we have 2 plugins: JavaStyle and AStyle. Could anybody explain
> what is the difference (definitely, I mean the for Java code).
> Feature-by-feature (bug-by-bug:). What are limits for each of them? Any
> recommendations?

The main difference is complexity.

AStyle is a line-by-line beautifier, that looks for certain keywords and
structure characters like '{', remembers the current indent level and indents
each line one a one-by-one basis. This is a fast and simple approach, but you
cannot do certain things, like sorting methods etc.

JavaStyle is much more complex. It contains a full blown Java parser,
similar to the javac compiler. It reads in the Java source code as a whole, builds
an object tree, and effectively "redraws" the whole source code from scratch.
The advantage is that you can to a lot more to the object tree before it is
written out, for example sort methods by access modifier (public methods
first), automatically generate JavaDoc tags etc. You'll notice that JavaStyle has
much more options than AStyle. 

So, if you want simply to reindent your code with tabs or spaces, I would go
for AStyle. But if you want to enforce a certain structure on your code, I
would use JavaStyle. Some users complained, that sometimes JavaStyle does "too
much", and that it cannot be switched off. For them I created the AStyle
plugin.

> This ambiguity is not covered in the documentation. And I could not find
> any hints in the mailing list. 

I'll add this to the next release.

I'd really like to have more documentation for the AStyle plugin options,
including examples like in JavaStyle. But I didn't had the time. 

Does anybody want to contribute documentation?

Dirk.



-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

--
GMX Tipp:

Machen Sie Ihr Hobby zu Geld bei unserem Partner 1&1!
http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a

Hi all

There is one question about beautifiers:
Currently we have 2 plugins: JavaStyle and AStyle. Could anybody explain
what is the difference (definitely, I mean the for Java code).
Feature-by-feature (bug-by-bug:). What are limits for each of them? Any
recommendations?

This ambiguity is not covered in the documentation. And I could not find
any hints in the mailing list. 

Regards,

Sergey

testing, testing

Hi,

I am afraid the jEdit logo is going to have to be either a
transparent PNG or transparent GIF. Browsers correct PNGs
they display to a certain 'gamma' which depends on the
browser and OS, and because of this it is not possible to
get the colors between an image and the web page to match
up precisely. If you don't believe me, I can post a
screenshot of IE on a windows machine.

Andrew, since Netscape 4 has problems with transparent
PNGs, could you make the logo a transparent GIF please?

Slava

Hi Stefan,

> I was very pleased to hear from the new plugin. It really works very good,
> producing exactly the same results as the original AStyle program but
> being much more convenient. Great work.

Thanks!

> I have some issues concerning the formatting but as they are the same as
> in the orginal, I guess you are not the right one to address to?!?

Right. As the plugin help states:

"[AStyle] is, however, written in C++, so I had to port it to Java to make
it run inside jEdit. (Backport actually, because Artistic Style was originally
written in Java three years ago.) This porting process may have introduced
some new errors.

If you think you have found a bug in AStyle Plugin, please try to find out
whether this is a bug in the Artistic Style code beautifier, or in the AStyle
Plugin itself. You can check this by comparing the formatted results of your
file with the output of the native version of Artistic Style (available at
http://astyle.sf.net).

* If you are sure the bug lies in the Artistic Style code beautifier, please
inform Tal Davidson (dav...@bi...).
* If you are sure the bug lies in the AStyle Plugin itself, please inform
me, that is, Dirk Möbius (dmo...@gm...).
* If you are too unskilled, or too lazy, or otherwise unable to tell the
difference ;-), please inform me, that is, Dirk Möbius (dmo...@gm...)."


Dirk.

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

--
GMX Tipp:

Machen Sie Ihr Hobby zu Geld bei unserem Partner 1&1!
http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a

HI Carlos,

> Is not working for me. Instead I get this!!!
> 
> Configuration Windows 2000, Sun's JDK 1.3
> 
> [error] Exception while sending message on EditBus:
> [error] java.lang.NullPointerException
> [error]         at
> astyleplugin.AStylePlugin.handleMessage(AStylePlugin.java:60)

Thanks, fixed.

As a workaround, please open "Global Options>Plugins>AStyle Beautifier" and
close the dialog again with "Ok."

Dirk.

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

--
GMX Tipp:

Machen Sie Ihr Hobby zu Geld bei unserem Partner 1&1!
http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a

Is not working for me. Instead I get this!!!

Configuration Windows 2000, Sun's JDK 1.3

[error] Exception while sending message on EditBus:
[error] java.lang.NullPointerException
[error]         at
astyleplugin.AStylePlugin.handleMessage(AStylePlugin.java:60)

[error]         at org.gjt.sp.jedit.EditBus.send(EditBus.java:102)
[error]         at org.gjt.sp.jedit.Buffer.save(Buffer.java:653)
[error]         at java.lang.reflect.Method.invoke(Native Method)
[error]         at bsh.Reflect.invokeMethod(Reflect.java:217)
[error]         at bsh.Reflect.invokeObjectMethod(Reflect.java:46)
[error]         at bsh.Name.invokeMethod(Name.java:431)
[error]         at
bsh.BSHMethodInvocation.eval(BSHMethodInvocation.java:29)
[error]         at
bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:48)
[error]         at bsh.BSHBlock.eval(BSHBlock.java:29)
[error]         at
bsh.BshMethod.invokeDeclaredMethod(BshMethod.java:101)
[error]         at bsh.BshMethod.invokeDeclaredMethod(BshMethod.java:47)
[error]         at
org.gjt.sp.jedit.BeanShell.invokeMethod(BeanShell.java:317)
[error]         at
org.gjt.sp.jedit.BeanShellAction.invoke(BeanShellAction.java:
60)
[error]         at
org.gjt.sp.jedit.gui.InputHandler.invokeAction(InputHandler.j
ava:188)
[error]         at
org.gjt.sp.jedit.gui.DefaultInputHandler.keyPressed(DefaultIn
putHandler.java:197)
[error]         at
org.gjt.sp.jedit.textarea.JEditTextArea.processKeyEvent(JEdit
TextArea.java:3979)
[error]         at java.awt.Component.processEvent(Component.java:3553)
[error]         at java.awt.Container.processEvent(Container.java:1164)
[error]         at
java.awt.Component.dispatchEventImpl(Component.java:2593)
[error]         at
java.awt.Container.dispatchEventImpl(Container.java:1213)
[error]         at java.awt.Component.dispatchEvent(Component.java:2497)
[error]         at
java.awt.LightweightDispatcher.processKeyEvent(Container.java
:2155)
[error]         at
java.awt.LightweightDispatcher.dispatchEvent(Container.java:2
135)
[error]         at
java.awt.Container.dispatchEventImpl(Container.java:1200)
[error]         at java.awt.Window.dispatchEventImpl(Window.java:914)
[error]         at java.awt.Component.dispatchEvent(Component.java:2497)
[error]         at
java.awt.EventQueue.dispatchEvent(EventQueue.java:339)
[error]         at
java.awt.EventDispatchThread.pumpOneEvent(EventDispatchThread
.java:103)
[error]         at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.j
ava:93)
[error]         at
java.awt.EventDispatchThread.run(EventDispatchThread.java:84)

Hi Dirk,

I was very pleased to hear from the new plugin. It really works very good, producing exactly the same results as the original AStyle program but being much more convenient. Great work.

I have some issues concerning the formatting but as they are the same as in the orginal, I guess you are not the right one to address to?!?

Thanks,
Stefan

>>Hi,
>>
>>today I finally finished the first release of the new AStyle
>>Beautifier plugin.

Hi Dirk,

On Sat, 23 Jun 2001 11:46:04 +0200, Dirk Möbius wrote:

>Hi,
>
>today I finally finished the first release of the new AStyle
>Beautifier plugin.

Thank you very much. I find it very useful. 

Cheers,
  Manfred

-- 
________________________________________________________________________
Manfred Usselmann                              uss...@ic...

Hi Stuart,

I haven't studied or tried your code yet, but I have a few thoughts on the
items in your to do list.

>
> To do...
> 1. Decide if 6 is a good number? Im sure that people have other ideas.

With the startup script feature, you can make you macros configurable. For
example, you can put this in a startup script:

openJavaSourceDepth = 6;
openJavaSourceRoot = "/src";

These of course can be changed by the user. Then in your macro, you can
supply a default value if the macro has not been customized:

if(openJavaSourceDepth == null)
	openJavaSourceDepth = 6;

You could take this a step further and include for use of another
configuration variable that would trigger a file search in a set of
arbitrary directories.

> 2. Decide what to do if the file has not been found? Maybe pop up a
>      dir browser so the user could provide another directory to search in?

I would suggest a simple error message:

Macros.error(view, "Could not find source file for " + classname);

Ctrl-O is easily available to open a file.

> 3. Can this macro be added to the jEdit distribution? It seems very useful
>      and the lack of this functionality was a barrier to using
> jEdit as an IDE.

This is not something I would use because of my own habits, so I would like
to hear from others once you you are happy with a revised script.

> 4. Decide on a name for the macro? 'Open Java Class' ?

How about "Open_Java_Source.bsh"?

> 5. It seemed to be an area that the CodeAid should offer. If the CodeAid
>      plugin has list of classes then it could be asked to open a
> buffer for
>      the class selected? But for now it was quicker for me to
> build a macro.

I don't use CodeAid so I can't help you with design questions.  Obviously it
would be great
if you could leverage plugin code to minimize file searching.

> 6. Any other thoughts on this?

That's all for now.  Good luck.

John

Thanks for the macro John.
I have taken the idea you gave me and have extended it to
try and open java files for the selected text.

1. It takes the selection and adds '.java' to the end. The java class
     should be defined in a file called classname.java.
2. Then it gets the path of the current buffer and goes up until
     it meets a directory called 'src' or until it jumps 6 times. 6 seemed
     like a good number.
3. Then it searches the directory tree from that point to try and find
     the file.
4. If it finds the file then it tells jEdit to open it.


START OF PASTE

// Opens selected path name for java files
// jumps up the dir tree until a directory called src is found
// or stops after 6 jumps - seemed like a good number?

String findFile(String directoryPath, String fileName) {
     String retVal = null;
     File directory = new File(directoryPath);

     File[] subFiles = directory.listFiles();
     for (int i = 0; i < subFiles.length; i++) {
         if (subFiles[i].isDirectory()) {
             // recurse into sub dirs
             retVal = findFile(subFiles[i].getAbsolutePath(), fileName);
         }
         else {
             String name = subFiles[i].getName();
             if (name.equals(fileName)) {
                 retVal = subFiles[i].getAbsolutePath();
             }
         }

         // if found then we are done
         if ( retVal != null ) {
                 break;
         }
     }

     return retVal;
}


String path = textArea.getSelectedText();
path += ".java";
if(path == null)
         view.getToolkit().beep();
else {
     File selectedText = buffer.getFile();
     File dirToSearch = selectedText.getParentFile();
     int numJumps = 0;
     while ( !dirToSearch.getName().equals("src") && numJumps < 6) {
         dirToSearch = dirToSearch.getParentFile();
         numJumps++;
     }

     String foundFile = findFile(dirToSearch.getAbsolutePath(), path);

     // open the found file
     if ( foundFile != null ) {
         System.out.println("found file: " + foundFile);
         jEdit.openFile(view, foundFile);
     }
     else {
         System.out.println("could not find file: " + foundFile);
     }
}

END OF PASTE


To do...
1. Decide if 6 is a good number? Im sure that people have other ideas.
2. Decide what to do if the file has not been found? Maybe pop up a
     dir browser so the user could provide another directory to search in?
3. Can this macro be added to the jEdit distribution? It seems very useful
     and the lack of this functionality was a barrier to using jEdit as an IDE.
4. Decide on a name for the macro? 'Open Java Class' ?
5. It seemed to be an area that the CodeAid should offer. If the CodeAid
     plugin has list of classes then it could be asked to open a buffer for
     the class selected? But for now it was quicker for me to build a macro.
6. Any other thoughts on this?

Thanks.
Stuart.


*************************************************************************
Information in this email is confidential and may be privileged. It is
intended for the named addressee(s) only. If you have received it in
error please notify the sender immediately and delete it from your
system. You should not otherwise copy, retransmit, use or disclose its
contents to anyone.
*************************************************************************

Bugs item #436636, was opened at 2001-06-27 00:54
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=100588&aid=436636&group_id=588

Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Abbreviations lose $ signs

Initial Comment:
JEdit Version : 3.2pre3

Abbreviation Looks like :
_each -> list($key,$val) = each($1) 

And when _each#$myarray# is typed in the result is :

list(key,val) = each($myarray)

note : no $ in front of key and val. If you modify the 
abbr. to be  :
_each -> list($$key,$$val) = each($1) 

then it works fine.


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

>Comment By: Slava Pestov (spestov)
Date: 2001-06-28 00:32

Message:
Logged In: YES 
user_id=2280

fixed in 3.2pre4

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

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

Bugs item #436471, was opened at 2001-06-26 12:25
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=100588&aid=436471&group_id=588

Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Dave Walend (dwalend)
Assigned to: Nobody/Anonymous (nobody)
Summary: Better deprecation notes:JEditTextArea

Initial Comment:
You've deprecated some API in JEditTextArea, and added
deprecation tags, which is great. 

Please add some advice about how to get the same
functionality in the code we've written using the new
API. Replace the "Do not use." with "Use <some other
method call> instead."

Thanks,

Dave


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

>Comment By: Slava Pestov (spestov)
Date: 2001-06-28 00:32

Message:
Logged In: YES 
user_id=2280

done in 3.2pre4

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

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

Bugs item #436443, was opened at 2001-06-26 10:48
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=100588&aid=436443&group_id=588

Category: text area and syntax packages
Group: normal bug
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bracket matching thrown off (Perl)

Initial Comment:
When using brackets to dereference in Perl, like so:

@{$arrayref}

The leading '{' gets lost to the bracket matcher, 
throwing the bracket matching off for the rest of the 
document.  I have also confirmed that it happens with 
${ ... } and %{ ... }

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

>Comment By: Slava Pestov (spestov)
Date: 2001-06-28 00:31

Message:
Logged In: YES 
user_id=2280

fixed in 3.2pre4

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

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

Bugs item #434253, was opened at 2001-06-18 11:36
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=100588&aid=434253&group_id=588

Category: editor core
Group: severe bug
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: jEdit won't run more than 3 times

Initial Comment:
After I run jEdit 2 times, when I close the editor, my
console tells me:

[error] 	at
org.gjt.sp.jedit.EditPlugin$JAR.addPlugin(EditPlugin.java:147)
[error] 	at
org.gjt.sp.jedit.JARClassLoader.loadPluginClass(JARClassLoader.java:236)
[error] 	at
org.gjt.sp.jedit.JARClassLoader.loadAllPlugins(JARClassLoader.java:170)
[error] 	at org.gjt.sp.jedit.jEdit.main(jEdit.java:303)
[error] Error saving user defined global variables


And it does not run again. when I try to run it.. a
blank box appears and my system hangs. 

I am running RedHat 7.1, Blackdown Java Port 1.3.0FCS
and jEdit 3.1 and 3.2pre3. it happens over and over,
and I can only run jEdit if I reinstall it. 

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

>Comment By: Slava Pestov (spestov)
Date: 2001-06-28 00:30

Message:
Logged In: YES 
user_id=2280

this bug report was very vague and the submitter never
provided any more information, so I will close it. If this
bug occurs again, please submit it with an activity log.

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

Comment By: Slava Pestov (spestov)
Date: 2001-06-20 03:39

Message:
Logged In: YES 
user_id=2280

This is caused by a plugin's start() method failing. Care to
send your entire activity log? ($HOME/.jedit/activity.log)

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

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

Bugs item #431792, was opened at 2001-06-10 05:45
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=100588&aid=431792&group_id=588

Category: None
Group: normal bug
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: button in f.browser expa. outside screen

Initial Comment:
When i hit the more button in the file browser view it 
expands and shows a list of options. However, if the 
file browser view is not wide enough it will expand in 
a way that leaves half of the meny outside the screen.

I am running jEdit 3.1 on windows 2000 sp2 with Java 2 
runtime enviroment, standard edition 1.3.0_02. No 
plugins are installed.

I have attached a screenshot of what it looks like. 

Tobias Brandvik
to...@ev...

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

>Comment By: Slava Pestov (spestov)
Date: 2001-06-28 00:29

Message:
Logged In: YES 
user_id=2280

fixed in 3.2pre4.

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

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

Bugs item #223469, was opened at 2000-11-26 00:16
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=100588&aid=223469&group_id=588

Category: text area and syntax packages
Group: minor bug
>Status: Closed
>Resolution: Works For Me
Priority: 3
Submitted By: Slava Pestov (spestov)
Assigned to: Slava Pestov (spestov)
Summary: Focus bug

Initial Comment:
This occurs with JDK 1.1.7. Start jEdit. Split the view. Press C+e C+j. Note how the caret blinks. Now enter some text. It won't be entered until you click in the text area.

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

>Comment By: Slava Pestov (spestov)
Date: 2001-06-28 00:27

Message:
Logged In: YES 
user_id=2280

no longer occurs with 3.2pre4. since i was the only one who
ever reported this bug, i am going to close it.

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

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

Bugs item #436759, was opened at 2001-06-27 09:17
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=100588&aid=436759&group_id=588

Category: text area and syntax packages
Group: normal bug
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: syntax highlighting erratic

Initial Comment:
Version: jEdit 3.2pre3
This is entirely reproducable for me.  The following steps cause the syntax highlighter to incorrectly highlight PHP code:

1) Load a file in PHP mode
2) Page down to the middle of the file
3) Close it
4) Reopen it

The editor will have reopened the file with the cursor at the last place you were in the file.  But the syntax highlighting is wrong.  All PHP code is now black, and HTML tags are blue (or whatever your color choice is set to.)  

If you page up to the top of the file, then start pageing back down, the syntax highlighting is magically corrected.


BTW: the size of the summary text field in this bug report form is too small and you can't search the bug system.  Whoever wrote this bug tracker is an idiot.  My 2 cents... =)



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

>Comment By: Slava Pestov (spestov)
Date: 2001-06-28 00:23

Message:
Logged In: YES 
user_id=2280

I will add a configurable flag to jEdit to parse the entire
file on startup, instead of only visible regions. It will
solve this problem.

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

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

Bugs item #436789, was opened at 2001-06-27 10:37
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=100588&aid=436789&group_id=588

Category: None
Group: minor bug
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: ollie rutherfurd (fruhstuck)
Assigned to: Nobody/Anonymous (nobody)
Summary: Browse System Macros browses user macros

Initial Comment:
Selecting 'Browse System Macros' and 'Browser User 
Macros' both browse 'User Macros'.

Looks like line 120 of Macros.java should be:

browser.setDirectory(systemMacroPath);

instead of:

browser.setDirectory(userMacroPath);


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

>Comment By: Slava Pestov (spestov)
Date: 2001-06-28 00:20

Message:
Logged In: YES 
user_id=2280

fixed in 3.2pre4.

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

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

Bugs item #436829, was opened at 2001-06-27 12:54
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=100588&aid=436829&group_id=588

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Ron Gilson (macgyver13)
Assigned to: Nobody/Anonymous (nobody)
Summary: ZIP file must have at least one entry

Initial Comment:
when I try to run cdbbuild to build the .cdb files I 
can not get past the following exception with certain 
files.  I am trying to create a .cdb for servlet 
classes, is there a specific .jar file that I should 
use?  

C:\Program Files\jEdit 3.1\jars\CodeAid>cdbbuild -s 
jsdk23.jar -o neservlet.cdb

java.util.zip.ZipException: ZIP file must have at 
least one entry
at java.util.zip.ZipOutputStream.finish(Unknown Source)
at codeaid.info.ClassTable.write(ClassTable.java:534)
at codeaid.tools.DBWriter.run(DBWriter.java:57)
at codeaid.tools.CDBBuilder.run(CDBBuilder.java:182)
at codeaid.tools.CDBBuilder.main(CDBBuilder.java:76)

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

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