|
From: Patric B. <be...@ip...> - 2005-09-16 00:12:00
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alan, don't get me wrong. The trick with the log is something I've done as an additional test. The stdout-catching is the one which I think is most important: That way, every tool capable of printing on the console written in java could be calld in-jvm without spawning another process... tia Patric Alan Ezust schrieb am 16.09.2005 01:13: > Ah, I see. The Error List does not look at the stuff in the Log stream. > I guess ErrorList should add a LogHandler for parsing generic error > messages too. > > Console currently does regex parsing of output from the Console, > but the Log stream is something else entirely. > > I wonder how easy that would be to add... I would have to read a bit > more about how jEdit.Log works. > > On 9/15/05, *Patric Bechtel* <be...@ip... > <mailto:be...@ip...>> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I've checked the CVS code, Rudi's test works. Mine not. As a test, take > this bsh snippet, save it as a makro call it. Only thing I see is > activity logs messages, no error list activity: > > s=view.getBuffer().getPath(); > print(s+":1:test print"); > Log.log(Log.MESSAGE,null,s+":2:test log message"); > > tia, -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: GnuPT 2.5.2 iD8DBQFDKg3EfGgGu8y7ypARApDPAKDGQpxD+WGjwVdoFnmcBZO9OqV1ywCgwBHC 4P+i4LNu/QS1i/dG090SIC4= =798t -----END PGP SIGNATURE----- |