that's the "we are bored geek losers" spirit of the ML :)
On Mon, 05 Jun 2006 17:04:47 -0400, Thomas Geirhovd <[EMAIL PROTECTED]>
wrote:
> That's part of why I love aMSN :D
>
> On 6/5/06, Philippe Khalaf <[EMAIL PROTECTED]> wrote:
>> Only on amsn-devel would such an email generate such a long
That's part of why I love aMSN :D
On 6/5/06, Philippe Khalaf <[EMAIL PROTECTED]> wrote:
> Only on amsn-devel would such an email generate such a long thread...
>
> Laterz,
> Burger
>
> On Fri, 2 Jun 2006 20:23:19 +0200
> Harry Vennik <[EMAIL PROTECTED]> wrote:
>
> > Op vrijdag 2 juni 2006 20:11, s
Hi,
Well after seeing that long thread about languages, it kinda feels
like there is no solution but to keep the GUI in tcl/tk. We will never
agree on a new language, we already know tcl/tk, and we have a whole
lot of GUI code already written in TCL/TK. The back-end (connection
manager) could be
Only on amsn-devel would such an email generate such a long thread...
Laterz,
Burger
On Fri, 2 Jun 2006 20:23:19 +0200
Harry Vennik <[EMAIL PROTECTED]> wrote:
> Op vrijdag 2 juni 2006 20:11, schreef Youness Alaoui:
> > lol, come on, people don't know what an automated message is ? they relaly
>
While on the topic of the website, I have to say that the website looks a
lot better than the old one.
I do however dislike the current format of the Plugin/Skin page, it is very
hard to scan the list of plugins. If anyone wants to look through them they
have to read them 1 by 1. I think a tabular
> > which means, if we receive the reflector's ACK, we'll go through all
> > switch cases, won't find TSP_PAUSED, so it goes into default, which sets
> > the state as END, closes the socket, and basta... so next time we 'resume'
> > it, we won't be able to send on a closed socket... the readfromsoc
> which means, if we receive the reflector's ACK, we'll go through all
> switch cases, won't find TSP_PAUSED, so it goes into default, which sets
> the state as END, closes the socket, and basta... so next time we 'resume'
> it, we won't be able to send on a closed socket... the readfromsock and
>
readded the pause problem...
don't forget to revert back your changes... and take a look at
ReadFromSock, here :
default
{
status_log "option $state of socket $sock :
[getObjOption $sock state]
not defined.. recei
