[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jedit-users
Subject:    Re: [ jEdit-users ] any mac users see jedit4pre11 ever spike the
From:       "Alan Ezust" <alan.ezust () gmail ! com>
Date:       2007-10-09 23:39:40
Message-ID: f377591c0710091639q3b6f3b7avd9f1b3d7c7f604c6 () mail ! gmail ! com
[Download RAW message or body]

Hi Dale,

I just released XML 2.0.7 yesterday with your fix, which will help
users avoid this issue until you can fix it.

--alan


On 10/9/07, Dale Anson <danson@grafidog.com> wrote:
> 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* <elberry@gmail.com
> > <mailto:elberry@gmail.com>> 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/
>
> -------------------------------------------------------------------------
> 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/
> --
> -----------------------------------------------
> jEdit Users' List
> jEdit-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jedit-users
>

-------------------------------------------------------------------------
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/
-- 
-----------------------------------------------
jEdit Users' List
jEdit-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-users
[prev in list] [next in list] [prev in thread] [next in thread]