From: Peter Graves <peter@ar...> - 2003-10-13 20:12:21
On Mon, 13 Oct 2003 at 08:29:35 +0200, Houssem BDIOUI wrote:
> Hi Peter,
> I'm using J 0.18.0 ( which is really great of simplicity and
> efficacity) for editing and compiling a C++ project. We're working on
> a Solaris station, but sometimes this station becomes very busy so
> your java editor becomes very slow (some of the drawbacks of Java :)
> ), so in this case, I execute the j.jar from the PC (Windows NT) and
> I connect to the station by FTP and to compile I must execute a very
> long batch command using rexec (by the way, do you know how to avoid
> typing the password every time? ) and it's working, but when I got
> errors during the compilation and when I want to go to the line where
> the error is, your editor does'nt seem to understand that the file is
> remote and not local and it does nothing !
Right. Compilation buffers don't really work with remote files.
> So can you please fix it or give me some tricks to work around it.
There aren't any tricks, and I don't plan to fix this, unless someone
wants to sponsor the work.
> p.s: I'm sorry to annoy you if this is already fixed in later
> releases !
> There is also a bug which is only on Solaris and not on
> the PC: selecting a text and moving it makes J to crashes !
This one I'd like to fix, since selecting text and moving it is a very
basic operation, but I don't have access to a Solaris box...
By any chance is a stack trace written to the log (~/.j/log) when this
Are you using the latest version of Java on the Solaris box in question?