From: Slava P. <sl...@je...> - 2001-12-09 04:31:03
|
Hello everybody, How does everyone feel about the IRC plugin being bundled with the core in 4.0pre3? I think if more people have access to it by default, the jEdit IRC channel (#jedit on irc.openprojects.net) can become a useful alternative to the mailing lists for obtaining support. Slava |
From: Maik S. <bZ...@iq...> - 2001-09-29 20:27:48
|
[Well, it's my birthday today, so I thought I create a gift for you guys (and girls) out there :-)] * Do you feel lonely when you are programming? * You have a question but there's no one around to ask? * Editing some texts and chatting are two mutually exclusive things? Well, if you answered any question of the above with YES, it's time for IRCPlugin! Chat with your friends or colleagues while doing your stuff. IRCPlugin is just as easy as it gets! The IRC plugin uses a dockable window to display an IRC channel's contents, so you can decide where it should dock. No external tools (such as mIRC) are needed. Consult the plugin documentation in jEdit's Help menu for more information. You can find the plugin at http://www.iq-computing.de/IRCPlugin.jar Just throw the Jar file into your <jEdit-home>/jars directory to install it. Remember to change the settings in "Utilities/Global options/Plugin options/IRC" to meet your needs. (Licensed under the GPL. Source code is not included yet, but will follow soon.) -- </Mickey> |
From: Alexander H. <ro...@ao...> - 2001-09-29 20:38:04
|
On Sat, 29 Sep 2001 22:27:53 +0200, "Maik Schreiber" <bZ...@iq...> wrote: > [snip] > * Do you feel lonely when you are programming? > * You have a question but there's no one around to ask? > * Editing some texts and chatting are two mutually exclusive things? > > Well, if you answered any question of the above with YES, it's time for > IRCPlugin! > Chat with your friends or colleagues while doing your stuff. IRCPlugin > is just as easy as it gets! Does this sound like marketroid garbage to anyone else? What is this doing on the jEdit list? > [snip] > (Licensed under the GPL. Source code is not included yet, but will > follow soon.) Breach of contract. The GPL requires you to release the source _NOW_, not when you feel like it. Be glad I'm not a lawyer... Regards, Alex. |
From: John G. <jge...@ny...> - 2001-09-29 21:24:20
|
> -----Original Message----- > From: jed...@li... > [mailto:jed...@li...]On Behalf Of Alexander > Hvostov > Sent: Saturday, September 29, 2001 4:36 PM > To: jed...@li... > Subject: Re: [ jEdit-users ] [PLUGIN] IRC plugin > > > On Sat, 29 Sep 2001 22:27:53 +0200, "Maik Schreiber" > <bZ...@iq...> wrote: > > > [snip] > > * Do you feel lonely when you are programming? > > * You have a question but there's no one around to ask? > > * Editing some texts and chatting are two mutually exclusive things? > > > > Well, if you answered any question of the above with YES, it's time for > > IRCPlugin! > > Chat with your friends or colleagues while doing your stuff. IRCPlugin > > is just as easy as it gets! > > Does this sound like marketroid garbage to anyone else? What is > this doing on > the jEdit list? No, it doesn't. Comments like these serve no useful purpose. In the past I have received inquiries on whether there is an IRC channel for jEdit users or developers. It's not a bad idea, and maybe this plugin will help facilitate it. > > > [snip] > > (Licensed under the GPL. Source code is not included yet, but will > > follow soon.) > > Breach of contract. The GPL requires you to release the source > _NOW_, not when > you feel like it. Be glad I'm not a lawyer... > This is not correct. The GPL imposes source code distribution requirements on licensees, not the copyright owner. A GPL license without source code is self-defeating, because the license effectively prevents redistribution until source code becomes available. Nevetheless, unless the author has assigned copyright to a third party, there is no breach. However, if the plugin incorporates code belonging to others that is subject to the GPL (or any other compatible license), the author must respect the license under which he or she is allowed to use the incorporated code. John |
From: Carlos Q. <car...@we...> - 2001-09-30 08:23:47
|
On Sunday 30 September 2001 00:25, John Gellene wrote: > > No, it doesn't. Comments like these serve no useful purpose. Agreed, you don't get very motivated to do something new > > In the past I have received inquiries on whether there is an IRC channel > for jEdit users or developers. It's not a bad idea, and maybe this plugin > will help facilitate it. This is an excellent idea, I'd love that after the plugin can be tested and released normally we could establish such a channel. It could be even included by the default as a choice Regards |
From: ///o-o\\\\\\ <ja...@ja...> - 2001-09-30 16:45:32
|
man, that's harsh.... you need to chill out... On Sat, 2001-09-29 at 16:36, Alexander Hvostov wrote: > On Sat, 29 Sep 2001 22:27:53 +0200, "Maik Schreiber" <bZ...@iq...> wrote: > > > [snip] > > * Do you feel lonely when you are programming? > > * You have a question but there's no one around to ask? > > * Editing some texts and chatting are two mutually exclusive things? > > > > Well, if you answered any question of the above with YES, it's time for > > IRCPlugin! > > Chat with your friends or colleagues while doing your stuff. IRCPlugin > > is just as easy as it gets! > > Does this sound like marketroid garbage to anyone else? What is this doing on > the jEdit list? > > > [snip] > > (Licensed under the GPL. Source code is not included yet, but will > > follow soon.) > > Breach of contract. The GPL requires you to release the source _NOW_, not when > you feel like it. Be glad I'm not a lawyer... > > Regards, > > Alex. -- ________________________ ///o-o\\\ Jamie LaScolea |
From: mike d. <md...@je...> - 2001-09-29 20:45:28
|
begin Maik Schreiber quotation: > Well, it's my birthday today happy birthday. -md |
From: mike d. <md...@je...> - 2001-09-29 20:50:53
|
begin root quotation: > Does this sound like marketroid garbage to anyone else? What is this > doing on the jEdit list? it sounds like somebody got up on the wrong side of the bed. so Maik may have sounded less hip than you, King Cool; to me, it was obviously meant to be mildly parodious, while still announcing the existence of something he wanted to share. your attitude doesnt' help. > > (Licensed under the GPL. Source code is not included yet, but will > > follow soon.) > > Breach of contract. The GPL requires you to release the source _NOW_, > not when you feel like it. Be glad I'm not a lawyer... who would sue him? the copyright holder is the only eligible party, and i doubt he'll sue himself. he'll release the code when he's able. the code isn't technically released under the GPL, because nobody receiving the binary can actually fulfill the GPL's terms, but it is unlikely anyone has any legal recourse against the author. -md |
From: Alexander H. <ro...@ao...> - 2001-09-29 21:02:28
|
On Sat, 29 Sep 2001 13:50:52 -0700, mike dillon <md...@je...> wrote: > begin root quotation: > > Does this sound like marketroid garbage to anyone else? What is this > > doing on the jEdit list? > > it sounds like somebody got up on the wrong side of the bed. so Maik may > have sounded less hip than you, King Cool; to me, it was obviously meant > to be mildly parodious, while still announcing the existence of > something he wanted to share. your attitude doesnt' help. This has nothing to do with being 'King Cool'. This has to do with what sounds a lot like spam, which I find difficult to stomach _without_ it being sent via a mailing list for Open Source software. There's something I find especially insulting about the fact that it was sent here. I don't find it funny. It looks like spam, not parody, to me. > > > (Licensed under the GPL. Source code is not included yet, but will > > > follow soon.) > > > > Breach of contract. The GPL requires you to release the source _NOW_, > > not when you feel like it. Be glad I'm not a lawyer... > > [snip] > the code isn't technically released under the GPL, because nobody > receiving the binary can actually fulfill the GPL's terms, but it is > unlikely anyone has any legal recourse against the author. The problem with the license part is that I have no way to exercise my rights under the GPL -- namely, to modify the source as I please. How can I do that if I don't _have_ the source? Also, how do you know that there isn't some other GPL'd code in this plugin? If that's true, then you probably do have something to sue him over, since he is now violating someone else's license. Though he may be privileged over his own code, he certainly isn't privileged over anyone else's -- at least, not implicitly (ie, someone may have assigned their copyright to him, but that's unlikely). Regards, Alex. |
From: Maik S. <bZ...@iq...> - 2001-09-29 21:23:10
|
>This has nothing to do with being 'King Cool'. This has to do >with what sounds a lot like spam, which I find difficult to >stomach _without_ it being sent via a mailing list for Open >Source software. There's something I find especially insulting >about the fact that it was sent here. > >I don't find it funny. It looks like spam, not parody, to me. Well, press DEL then. That's just my point of view. >The problem with the license part is that I have no way to >exercise my rights under the GPL -- namely, to modify the >source as I please. How can I do that if I don't _have_ the source? Oh well :-( Hey, do you want to have the code? I think the GPL doesn't say anything about it being commented, cleaned, and other stuff. So if you want to have the code *RIGHT* *NOW*, send me a message and I have it mailed to you! Promised. Boy. What a nice birthday... -- </Mickey> |
From: Daniil V. K. <da...@vs...> - 2001-10-01 17:06:28
|
On 29 =D0=A1=D0=B5=D0=BD=D1=82=D1=8F=D0=B1=D1=80=D1=8C 2001 23:02, Alexan= der Hvostov wrote: > > The problem with the license part is that I have no way to exercise > my rights under the GPL -- namely, to modify the source as I please. > How can I do that if I don't _have_ the source? Okay, get the jad and decompile it :))) --=20 8:18pm up 10 days, 5:34, 13 users, load average: 0.03, 0.07, 0.07 |
From: Maik S. <bZ...@iq...> - 2001-09-29 21:18:26
|
>it sounds like somebody got up on the wrong side of the bed. >so Maik may have sounded less hip than you, King Cool; to me, >it was obviously meant to be mildly parodious, while still >announcing the existence of something he wanted to share. your >attitude doesnt' help. Oh well. I thought I developed something nice to share with you people. I didn't want to start *this* type of "conversation"... >who would sue him? the copyright holder is the only eligible >party, and i doubt he'll sue himself. he'll release the code >when he's able. Well, I will. I have to clean the code a bit, but I certainly will release it under the GPL as well. >the code isn't technically released under the GPL, because >nobody receiving the binary can actually fulfill the GPL's >terms, but it is unlikely anyone has any legal recourse >against the author. I'm not that much into legal things, and I certainly don't want to have that much to do with them. I'm just a bit surprised about that rough tone of Alexander's... :-/ -- </Mickey> |
From: Daniil V. K. <da...@vs...> - 2001-10-01 17:12:30
|
Relax, IRC in text editor is real fun indeed :) And - jEdit seems to be the first one, because you made it be! Sorry I'm unable to test it - I don't want to open the firewall for IRC=20 right now, coz I use it rarely (or even less :)). May I make a feature request? Make the text encoding to be configurable! On 29 =D0=A1=D0=B5=D0=BD=D1=82=D1=8F=D0=B1=D1=80=D1=8C 2001 23:18, Maik S= chreiber wrote: > >it sounds like somebody got up on the wrong side of the bed. > >so Maik may have sounded less hip than you, King Cool; to me, > >it was obviously meant to be mildly parodious, while still > >announcing the existence of something he wanted to share. your > >attitude doesnt' help. > > Oh well. > I thought I developed something nice to share with you people. I > didn't want to start *this* type of "conversation"... > > >who would sue him? the copyright holder is the only eligible > >party, and i doubt he'll sue himself. he'll release the code > >when he's able. > > Well, I will. I have to clean the code a bit, but I certainly will > release it under the GPL as well. > > >the code isn't technically released under the GPL, because > >nobody receiving the binary can actually fulfill the GPL's > >terms, but it is unlikely anyone has any legal recourse > >against the author. > > I'm not that much into legal things, and I certainly don't want to > have that much to do with them. > I'm just a bit surprised about that rough tone of Alexander's... :-/ --=20 8:21pm up 10 days, 5:37, 13 users, load average: 0.03, 0.07, 0.08 |
From: Maik S. <bZ...@iq...> - 2001-10-01 17:31:07
|
>May I make a feature request? Make the text encoding to be >configurable! Well, which text encoding? The IRC protocol is simply text-based, so there's not that much to encode... -- Maik Schreiber IQ Computing - http://www.iq-computing.de mailto: in...@iq... |
From: Daniil V. K. <da...@vs...> - 2001-10-01 18:01:49
|
On 1 =D0=9E=D0=BA=D1=82=D1=8F=D0=B1=D1=80=D1=8C 2001 19:31, Maik Schreibe= r wrote: > >May I make a feature request? Make the text encoding to be > >configurable! > > Well, which text encoding? The IRC protocol is simply text-based, so > there's not that much to encode... Sorry, I meant Charset. --=20 9:14pm up 10 days, 6:29, 13 users, load average: 0.45, 0.44, 0.29 |
From: Alexander H. <ro...@ao...> - 2001-10-01 18:13:23
|
On Mon, 1 Oct 2001 19:31:17 +0200, "Maik Schreiber" <bZ...@iq...> wrote: > > >May I make a feature request? Make the text encoding to be > >configurable! > > Well, which text encoding? The IRC protocol is simply text-based, so > there's not that much to encode... That very text you speak of has to be encoded somehow. RFC 1459 doesn't specify an encoding, but ISO 8859-1 (aka Latin-1) is the de facto standard encoding. IBM code pages 437 and 850 are also common. However, there is no restriction on exactly which encoding you use, so you can use, say, a CJK encoding in a channel where CJK languages are spoken, or a Russian encoding in a Russian channel. This doesn't apply to the IRC protocol messages, however -- just the human readable chat text. The protocol messages are all in ASCII. By 'protocol messages', by the way, I mean 'PRIVMSG' and the like -- parts of the protocol that are supposed to be parsed by the client or server, rather than read by a user. Regards, Alex. |
From: Maik S. <bZ...@iq...> - 2001-10-01 18:39:18
|
>That very text you speak of has to be encoded somehow. RFC >1459 doesn't specify an encoding, but ISO 8859-1 (aka Latin-1) >is the de facto standard encoding. IBM code pages 437 and 850 >are also common. However, there is no restriction on exactly >which encoding you use, so you can use, say, a CJK encoding in >a channel where CJK languages are spoken, or a Russian >encoding in a Russian channel. Oh, I see. Didn't know that... >This doesn't apply to the IRC protocol messages, however -- >just the human readable chat text. The protocol messages are >all in ASCII. By 'protocol messages', by the way, I mean >'PRIVMSG' and the like -- parts of the protocol that are >supposed to be parsed by the client or server, rather than >read by a user. That is quite clear. So I think this should be a matter of using String.String(byte[] bytes, String encoding) to decode incoming text and using String.getBytes(String encoding) to encode outgoing text, right? I'm not that used to support various types of encoding, so some advise on that would be helpful. -- Maik Schreiber IQ Computing - http://www.iq-computing.de mailto: in...@iq... |
From: Alexander H. <ro...@ao...> - 2001-10-02 02:26:19
|
On Mon, 1 Oct 2001 20:39:31 +0200, "Maik Schreiber" <bZ...@iq...> wrote: > > >That very text you speak of has to be encoded somehow. RFC > >1459 doesn't specify an encoding, but ISO 8859-1 (aka Latin-1) > >is the de facto standard encoding. IBM code pages 437 and 850 > >are also common. However, there is no restriction on exactly > >which encoding you use, so you can use, say, a CJK encoding in > >a channel where CJK languages are spoken, or a Russian > >encoding in a Russian channel. > > Oh, I see. Didn't know that... > > >This doesn't apply to the IRC protocol messages, however -- > >just the human readable chat text. The protocol messages are > >all in ASCII. By 'protocol messages', by the way, I mean > >'PRIVMSG' and the like -- parts of the protocol that are > >supposed to be parsed by the client or server, rather than > >read by a user. > > That is quite clear. > > So I think this should be a matter of using String.String(byte[] bytes, > String encoding) to decode incoming text and using > String.getBytes(String encoding) to encode outgoing text, right? > > I'm not that used to support various types of encoding, so some advise > on that would be helpful. That works. So does using a Writer of some kind or another. Consider this: OutputStream out; // initialized elsewhere Writer write = new OutputStreamWriter(out, <encoding>); Writer messageWrite = new OutputStreamWriter(out, "US-ASCII"); messageWrite.write("PRIVMSG nick :"); messageWrite.flush(); write.write(<some message in Unicode>); write.flush(); (Substitute <encoding> for the character encoding to use for chat -- the most common being "ISO-8859-1". Substitute <some message in Unicode> for a message to be sent, encoded in Unicode.) What this does is open _two_ OutputStreamWriters on the same OutputStream. This way, you can write to the same OutputStream using two different character encodings -- 'US-ASCII' for protocol messages ('messageWrite') and some other encoding for the chat ('write'). Note also that you need to call Writer.flush() after writing to one of the Writers, before you start writing to the other. That guarantees that the text will be written to the OutputStream in the correct order. Otherwise you run the risk of having the message turn out like this: hi there!PRIVMSG nick : Instead of what you want, which is this: PRIVMSG nick :hi there! This only matters when the Writer does caching of some kind, but just flush it to be on the safe side. Regards, Alex. |
From: Daniil V. K. <da...@vs...> - 2001-10-02 10:47:56
|
On 1 =D0=9E=D0=BA=D1=82=D1=8F=D0=B1=D1=80=D1=8C 2001 20:39, Maik Schreibe= r wrote: > >That very text you speak of has to be encoded somehow. RFC > >1459 doesn't specify an encoding, but ISO 8859-1 (aka Latin-1) > >is the de facto standard encoding. IBM code pages 437 and 850 > >are also common. However, there is no restriction on exactly > >which encoding you use, so you can use, say, a CJK encoding in > >a channel where CJK languages are spoken, or a Russian > >encoding in a Russian channel. > > Oh, I see. Didn't know that... > > >This doesn't apply to the IRC protocol messages, however -- > >just the human readable chat text. The protocol messages are > >all in ASCII. By 'protocol messages', by the way, I mean > >'PRIVMSG' and the like -- parts of the protocol that are > >supposed to be parsed by the client or server, rather than > >read by a user. > > That is quite clear. > > So I think this should be a matter of using String.String(byte[] > bytes, String encoding) to decode incoming text and using > String.getBytes(String encoding) to encode outgoing text, right? > > I'm not that used to support various types of encoding, so some > advise on that would be helpful. You can convert String to bytes and vice versa with some specific=20 encoding using String.getBytes(String)/new String(byte[], String), or=20 by using Reader/Writer family classes instead of=20 InputStream/OutputStream. And you should make target encoging=20 configurable. For the list of encodings available, I browse i18n.jar ;) --=20 1:57pm up 10 days, 23:13, 13 users, load average: 0.10, 0.10, 0.08 |
From: Alexander H. <ro...@ao...> - 2001-10-01 18:07:17
|
On Mon, 1 Oct 2001 20:25:38 +0200, "Daniil V. Kolpakov" <da...@vs...> wrote: > Relax, IRC in text editor is real fun indeed :) > And - jEdit seems to be the first one, because you made it be! No it's not. GNU Emacs and friends have had IRC clients written in Emacs Lisp for quite a while now. These integrated IRC clients have the same uses, too -- write code and talk about said code in the same editor. Regards, Alex. |
From: Will S. <wil...@ya...> - 2001-10-02 02:22:50
|
> > Relax, IRC in text editor is real fun indeed :) > > And - jEdit seems to be the first one, because you made it be! > > No it's not. GNU Emacs and friends have had IRC clients written > in Emacs Lisp > for quite a while now. These integrated IRC clients have the same > uses, too -- > write code and talk about said code in the same editor. This is true, but IMNSO they were unmaintained and very verbose and kludgy. An IRC client in Swing is far more fun because you have a more advanced GUI to play with. Will. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Alexander H. <ro...@ao...> - 2001-10-02 02:32:28
|
On Mon, 1 Oct 2001 19:22:51 -0700, "Will Sargent" <wil...@ya...> wrote: > > > Relax, IRC in text editor is real fun indeed :) > > > And - jEdit seems to be the first one, because you made it be! > > > > No it's not. GNU Emacs and friends have had IRC clients written > > in Emacs Lisp > > for quite a while now. These integrated IRC clients have the same > > uses, too -- > > write code and talk about said code in the same editor. > > This is true, but IMNSO they were unmaintained and very verbose and kludgy. > An IRC client in Swing is far more fun because you have a more advanced GUI > to play with. I didn't say they were any good, mind you. ;) Regards, Alex. |
From: Todd J. <tb...@to...> - 2001-09-30 04:03:18
|
Happy Birthday, Maik. I, for one, appreciate your gift to the jEdit community. Thanks, and keep coding. TBone Maik Schreiber wrote: >[Well, it's my birthday today, so I thought I create a gift for you guys >(and girls) out there :-)] > > >* Do you feel lonely when you are programming? >* You have a question but there's no one around to ask? >* Editing some texts and chatting are two mutually exclusive things? > >Well, if you answered any question of the above with YES, it's time for >IRCPlugin! >Chat with your friends or colleagues while doing your stuff. IRCPlugin >is just as easy as it gets! > >The IRC plugin uses a dockable window to display an IRC channel's >contents, so you can decide where it should dock. >No external tools (such as mIRC) are needed. > >Consult the plugin documentation in jEdit's Help menu for more >information. > > >You can find the plugin at http://www.iq-computing.de/IRCPlugin.jar >Just throw the Jar file into your <jEdit-home>/jars directory to install >it. > >Remember to change the settings in "Utilities/Global options/Plugin >options/IRC" to meet your needs. > > >(Licensed under the GPL. Source code is not included yet, but will >follow soon.) > |
From: Carlos Q. <car...@we...> - 2001-09-30 18:49:31
|
On Saturday 29 September 2001 23:27, Maik Schreiber wrote: Hi Maik I'm getting this exception when jedit is closing. I think since it coudln't connect it has problems closing, the bad things is that jEdit doesn't save the last settings when this happens. Below is a stack trace of the problem [error] java.lang.NullPointerException [error] at de.iqcomputing.jedit.irc.Net.disconnect(Net.java:81) [error] at de.iqcomputing.jedit.irc.Protocol.disconnect(Protocol.java:408) [error] at de.iqcomputing.jedit.irc.IRCWindow.disconnect(IRCWindow.java:81) [error] at de.iqcomputing.jedit.irc.IRCPlugin.stop(IRCPlugin.java:35) [error] at org.gjt.sp.jedit.jEdit.exit(jEdit.java:1885) [error] at org.gjt.sp.jedit.jEdit.closeView(jEdit.java:2682) [error] at org.gjt.sp.jedit.jEdit.closeView(jEdit.java:1701) [error] at org.gjt.sp.jedit.View$WindowHandler.windowClosing(View.java:1055) [error] at java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:290) [error] at java.awt.Window.processWindowEvent(Window.java:1085) [error] at javax.swing.JFrame.processWindowEvent(JFrame.java:250) [error] at java.awt.Window.processEvent(Window.java:1044) [error] at java.awt.Component.dispatchEventImpl(Component.java:3501) [error] at java.awt.Container.dispatchEventImpl(Container.java:1440) [error] at java.awt.Window.dispatchEventImpl(Window.java:1568) [error] at java.awt.Component.dispatchEvent(Component.java:3363) [error] at java.awt.EventQueue.dispatchEvent(EventQueue.java:448) [error] at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:193) [error] at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:147) [error] at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:141) [error] at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:133) [error] at java.awt.EventDispatchThread.run(EventDispatchThread.java:101) > [Well, it's my birthday today, so I thought I create a gift for you guys > (and girls) out there :-)] > > > * Do you feel lonely when you are programming? > * You have a question but there's no one around to ask? > * Editing some texts and chatting are two mutually exclusive things? > > Well, if you answered any question of the above with YES, it's time for > IRCPlugin! > Chat with your friends or colleagues while doing your stuff. IRCPlugin > is just as easy as it gets! > > The IRC plugin uses a dockable window to display an IRC channel's > contents, so you can decide where it should dock. > No external tools (such as mIRC) are needed. > > Consult the plugin documentation in jEdit's Help menu for more > information. > > > You can find the plugin at http://www.iq-computing.de/IRCPlugin.jar > Just throw the Jar file into your <jEdit-home>/jars directory to install > it. > > Remember to change the settings in "Utilities/Global options/Plugin > options/IRC" to meet your needs. > > > (Licensed under the GPL. Source code is not included yet, but will > follow soon.) |
From: Maik S. <bZ...@iq...> - 2001-09-30 19:51:33
|
>I'm getting this exception when jedit is closing. I think >since it coudln't connect it has problems closing, the >bad things is that jEdit doesn't save the last settings >when this happens. Below is a stack trace of the >problem Thank you very much for this report, Carlos! I guess I was closing the socket to optimistically (ie. it was null :-) This and other minor quirks have been fixed right now and will be incorporated into the 1.2 release. -- </Mickey> |