Re: [ jEdit-users ] any mac users see jedit4pre11 ever spike the cpu usage and not drop?

[Dale A. <da...@gr...>]

Yes, that is correct.  The html parser was hard-coded to use the 
ecmascript parser to parse in-line javascript.  I checked in a change 
for that a couple of weeks ago, but it hasn't made it to release yet, I 
think.  Now the ecmascript parser is only used for in-line javascript if 
it is selected as the default javascript parser.  Note that if the 
javascript parser is selected when parsing an html file with in-line 
javascript, that javascript won't be parsed.

There is an open bug on the CPU spike caused by the ecmascript parser.  
It is proving exceedingly difficult to track down.

Dale


Sarah Cranston wrote:
> I've run into the issue Eric mentions. Also, if you have an html file 
> with javascript in it, the fix below won't work - it will still use 
> ECMA script. At that point, when CPU usage spikes, all I know to do is 
> restart jEdit.
>  
> Fortunately, that isn't much of a chore, as jEdit remembers which 
> files I had open and where I was in them.
>
>  
> On 10/8/07, *Eric Berry* <el...@gm... 
> <mailto:el...@gm...>> wrote:
>
>     There was also an issue mentioned earlier that may have been
>     associated with the javascript parser, the ECMA script parser. If
>     you're using the Sidekick plugin, you may try setting your parser
>     for javascript to "javascript" instead of the  "ecmascript" parser.
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/