From: Alan E. <ala...@gm...> - 2006-12-21 18:03:12
|
On 12/21/06, Stan Berka <sb...@po...> wrote: > Hi there, > > I have recently updated from jEdit 4.2final to 4.3pre8 (I'm using > jdk1.5.0_05). The new version is good. I like it. A big THANK YOU to > all developers and contributors! However, I see a few problems. I > wonder if it is just me... > > * When I compile with AntFarm, I used to get a red marker on the > vertical scroll bar for each error location. It was very usefull, but > it's gone. Are you talking about XML or Java or Console error highlighting? As far as I understand, Antfarm is not involved with error highlighting. XML error highlighting is broken. I'm not sure why yet, but it's here: http://sourceforge.net/tracker/index.php?func=detail&aid=1597017&group_id=588&atid=565475 Console and JavaSideKick also sometimes send errors to the ErrorList and indirectly cause red errors to show up on the editpane. > * SOLVED: The StructureBrowser for Java sources showed a full signature > of a method, down in the status line, but the Sidekick, which I believe > uses JavaSideKick, doesn't show method arguments. Plugin Options - JavaSideKick - show arguments, generics types. > * Question: why do we have Beauty and JavaStyle plugins if they do > the same for Java? Beauty doesn't do anything for java, unless the JavaSideKick is installed, which plugs into the Beauty API. JavaStyle is for older versions (pre 4.3) of jedit. > * JSwatPlugin plainly doesn't start and shows an error about a > TextArea.getBuffer() not found. Is JSwatPlugin dead? It's the only > debugger in this jEdit version and also it's a good debugger (except for > some glitches). I think it needs a new maintainer. > * ERROR: once a while, the whole jEdit gets into some error condition, > takes all CPU, and although it functions, there is no way to bring it > back to be a nice citizen, but to restart it. This happens just while > editing. me too. I'm not sure what causes it but I think it's the Java regular expression engine. There are so many regexes in jEDit though, it's sometimes hard to know where it is coming from. |