Re: [ jEdit-devel ] Eclipse/jEdit interface

[Michael H <cm...@gm...>]

In about March 2016, I updated from jedit 4.x to jEdit 5.2.0 to see a new
way to manage modes.

Soon after that (maybe congruent, but I didn't note it immediately,) macros
(really just a long list of search/replace) that took 1-3 minutes to
process 5 megabytes of data started taking 10-12 hours to complete. While I
was willing to deal with the minutes of processing to allow for fluidity of
code, I can't deal with days.

I've made changes to the macros in question that did add to the processing,
but nothing that I can see should have introduced this massive increase in
time to completion.  I've also performed similar searches on the same text
in other editors and they return results in seconds. (Jedit was always
slower than text wrangler, but not this crawl it is now.)

Anyone have any advice what happened this year to the response time for
search/replace?

I know there were also changes in Java (Upgraded OSX from 10.9 - 10.10 at
about the same time).

Is there a known within Jedit that slowed down search/replace processing?
If I downgrade to 4.2 will it improve?  If I keep 5.2 and force an older
JRE?....



On Thu, Sep 29, 2016 at 9:41 AM, Steve Pritchard <spr...@re...>
wrote:

> Hi jEdit Deleopers
>
> I recently switched from UltraEdit (6 months) and MultiEdit (20 years) to
> jEdit.
>
> The impetus was to have context editing for Java classes similar to the
> Eclipse IDE where the methods and parameters pop up. jEdit provides a good
> foundation for what I want but that is for another day.
>
> Task 1 was to provide single key cut/copy/paste.  MultiEdit, as a hold
> over from Brief, used the NumPad-DASH, NumPad-PLUS and INSERT key to do
> this.  With a little trickery I was able to get jEdit to do this.
>
> I realized that the great architecture of jEdit would allow me to build an
> interface for compiles between Eclipse and jEdit.  The rationale is that
> for jEdit to compete with Eclipse on incremental builds is a longshot.
> However, Eclipse does provide a mechanism to listen for compile errors and
> warnings. I built an Eclipse plugin that listens for these errors and
> format a UDP message to ship them out.
>
> I then built a jEdit plugin that listens for the UDP messages and creates
> and populates the ErrorList window.
>
> Since I also save on taskswitch, to edit/compile/correct I do:
>
>    1. do edits
>    2. taskswitch (Alt-tab)to Eclipse.
>    3. Press F5 to do incremental build
>    4. click on error list to make corrections.
>
> I would like to share this with the jEdit community but do not know how.
> I do have a GitHub account.
>
> Steve
>
>
>
>
>
>
>
> ------------------------------------------------------------
> ------------------
>
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>
>