RE: [ jEdit-users ] Re: installing

[John G. <jge...@ny...>]

> Not to be picky...but would there be a way to disable this automatic
> native installation stuff?  Having tried both, I like the simplicity of
> jEditOpener over the jEditLauncher.  I don't need COM scriptability,
> etc., and I have been doing my own file association stuff for a long
> time...so it would be cool to be able to run the normal java install as
> I usually do, sans any native registration that I might already have done
> myself.
>
> Aaron

You're not being picky - you can continue using the Java installer.  As I've
said before, it works very well, and I have no desire to replace it.  Anyone
who wants more features can use jEditLauncher.  I like being able to
right-click any file or group of files into jEdit without doing anything to
existing file associations, and you can send a whole directory of *.java
files, for example, into the editor with one click.  I also like being able
to dump the output of a script file directly into my favorite text editor.

In the earlier posts on this topic, we've been talking about a second option
for installation that takes advantages of system-specific services (like rpm
under Red Hat Linux).  That's the kind of simplicity that most Windows users
can appreciate.  My own belief is that jEdit will be more popular with
Windows users (especially those who don't like to hack) if installation and
configuration can take place in a manner consistent with the Windows
"look-and-feel".

John