Re: Merry Xmas!

<div>
<p>Happy new year! <br><br></p>
<div>
<span class="gmail_quote">On 12/31/06, Norman Rasmussen &lt;<a href="mailto:norman@...">norman@...</a>&gt; wrote:</span>
<blockquote class="gmail_quote">and a Happy New Year to everyone...<br><br>--<br>- Norman Rasmussen<br>- Email: <a href="mailto:norman@...">
norman@...</a><br>- Home page: <a href="http://norman.rasmussen.co.za/">http://norman.rasmussen.co.za/</a><br>_______________________________________________<br>psi-devel mailing list<br><a href="mailto:psi-devel@...">
psi-devel@...</a><br><a href="http://lists.affinix.com/listinfo.cgi/psi-devel-affinix.com">http://lists.affinix.com/listinfo.cgi/psi-devel-affinix.com</a><br>
</blockquote>
</div>
<br>
</div>

history truncate

hello.
i am use psi compiled from psi-dev-snapshot-2006-12-23
i noticed, what history older than 1 month are deleted. how can i
increase this limit?

Re: crash on receive next event

On 30 Dec 2006, at 17:35, Hal Rottenberg wrote:
> 12-22nd nightly (Kev have your builds stopped working?)
They didn't stop working so much as the machine was turned off as I  
was away for Christmas, they should be back as of yesterday.

> I noticed middle-click on tray icon no longer receives next event.
> Right-click and choose receive resulted in a crash.
Can anyone else verify this? Is this only on Vista Hal?

/K

--

-- 
Kevin Smith
Psi XMPP Client Project Leader (http://psi-im.org)

Re: crash on receive next event

I experienced this behave under xp by double clicking the event, but
occured not many times.

Ciao Ephraim

Am Dienstag, den 02.01.2007, 08:59 +0000 schrieb Kevin Smith:
> On 30 Dec 2006, at 17:35, Hal Rottenberg wrote:
> > 12-22nd nightly (Kev have your builds stopped working?)
> They didn't stop working so much as the machine was turned off as I  
> was away for Christmas, they should be back as of yesterday.
> 
> > I noticed middle-click on tray icon no longer receives next event.
> > Right-click and choose receive resulted in a crash.
> Can anyone else verify this? Is this only on Vista Hal?
> 
> /K
> 

Re: crash on receive next event

On 1/2/07, Kevin Smith <kevin@...> wrote:
> > I noticed middle-click on tray icon no longer receives next event.
> > Right-click and choose receive resulted in a crash.
> Can anyone else verify this? Is this only on Vista Hal?

So far.  I'll load it up on XP here shortly.

--

-- 
Psi webmaster (http://psi-im.org)
im:hal@...
http://halr9000.com

[PATCH] fox for gcc on 64bit archs

Hi!

Uriy Zhuravlev provided a patch for amd64 systems to fix problems on linux 
with 64bit archs [1]. Problem exist in src/pluginsmanager.cpp file (see patch 
attached). As I found some info here [2], it is a gcc problem - so same 
should go for macosx (AFAIR, xcode-2 is using gcc-4*). I'm not sure about 
windows - I believe same should go for mingw (as it is ported gcc), but I 
don't have an amd64 box to test it with visual.

Anyway - together with amd64 fix, I put into this patch a fix for small typo 
in QString arg.

Hope it will help somebody.

Best regards,
Przemek

[1] https://bugs.gentoo.org/show_bug.cgi?id=131528
[2] http://lists.debian.org/debian-user/2006/04/msg00681.html
-- 
--------------------------------------------------------------------------
Email: troll (at) gentoo.org                 Przemysław Maciąg
Email: pmaciag (at) gmail.com
Reg Linux User#: 303556              "Life is like a box of chocolates."
GPG: 2A84608A [subkeys.pgp.net]    "You never know what you're gonna get."
--------------------------------------------------------------------------

Hi!

Uriy Zhuravlev provided a patch for amd64 systems to fix problems on linux 
with 64bit archs [1]. Problem exist in src/pluginsmanager.cpp file (see patch 
attached). As I found some info here [2], it is a gcc problem - so same 
should go for macosx (AFAIR, xcode-2 is using gcc-4*). I'm not sure about 
windows - I believe same should go for mingw (as it is ported gcc), but I 
don't have an amd64 box to test it with visual.

Anyway - together with amd64 fix, I put into this patch a fix for small typo 
in QString arg.

Hope it will help somebody.

Best regards,
Przemek

[1] https://bugs.gentoo.org/show_bug.cgi?id=131528
[2] http://lists.debian.org/debian-user/2006/04/msg00681.html
--

-- 
--------------------------------------------------------------------------
Email: troll (at) gentoo.org                 Przemysław Maciąg
Email: pmaciag (at) gmail.com
Reg Linux User#: 303556              "Life is like a box of chocolates."
GPG: 2A84608A [subkeys.pgp.net]    "You never know what you're gonna get."
--------------------------------------------------------------------------

Re: [PATCH] fox for gcc on 64bit archs

Przemysław Maciąg wrote:
> +#if __WORDSIZE == 64

The underscores at the beginning of the name seem to be shouting
"unportable!" to me, but maybe I'm wrong ;)

-- 
Maciek
 xmpp:machekku@...

Przemysław Maciąg wrote:
> +#if __WORDSIZE == 64

The underscores at the beginning of the name seem to be shouting
"unportable!" to me, but maybe I'm wrong ;)

--

-- 
Maciek
 xmpp:machekku@...

Re: [PATCH] fox for gcc on 64bit archs

Dnia środa, 3 stycznia 2007 00:12, Maciek Niedzielski napisał:
> Przemysław Maciąg wrote:
> > +#if __WORDSIZE == 64
>
> The underscores at the beginning of the name seem to be shouting
> "unportable!" to me, but maybe I'm wrong ;)

what is more important question: what's the number behind sizeof(*)? is it 4 
or 8? if 4 - then visual will have the same problem as gcc :)

Cheers,
Przemek
-- 
--------------------------------------------------------------------------
Email: troll (at) gentoo.org                 Przemysław Maciąg
Email: pmaciag (at) gmail.com
Reg Linux User#: 303556              "Life is like a box of chocolates."
GPG: 2A84608A [subkeys.pgp.net]    "You never know what you're gonna get."
--------------------------------------------------------------------------

Dnia środa, 3 stycznia 2007 00:12, Maciek Niedzielski napisał:
> Przemysław Maciąg wrote:
> > +#if __WORDSIZE == 64
>
> The underscores at the beginning of the name seem to be shouting
> "unportable!" to me, but maybe I'm wrong ;)

what is more important question: what's the number behind sizeof(*)? is it 4 
or 8? if 4 - then visual will have the same problem as gcc :)

Cheers,
Przemek
--

-- 
--------------------------------------------------------------------------
Email: troll (at) gentoo.org                 Przemysław Maciąg
Email: pmaciag (at) gmail.com
Reg Linux User#: 303556              "Life is like a box of chocolates."
GPG: 2A84608A [subkeys.pgp.net]    "You never know what you're gonna get."
--------------------------------------------------------------------------

Re: [PATCH] fox for gcc on 64bit archs

Przemysław Maciąg wrote:
> Dnia środa, 3 stycznia 2007 00:12, Maciek Niedzielski napisał:
>> Przemysław Maciąg wrote:
>>> +#if __WORDSIZE == 64
>> The underscores at the beginning of the name seem to be shouting
>> "unportable!" to me, but maybe I'm wrong ;)
> what is more important question: what's the number behind sizeof(*)? is it 4 
> or 8? if 4 - then visual will have the same problem as gcc :)
Yes, but if it doesn't know "__WORDSIZE", then it won't work even on
32bit systems, so the fix may break more things than fix.

(as a sidenote, it works in VS2003, but still I find these underscores
rather suspicious)

-- 
Maciek
 xmpp:machekku@...

Przemysław Maciąg wrote:
> Dnia środa, 3 stycznia 2007 00:12, Maciek Niedzielski napisał:
>> Przemysław Maciąg wrote:
>>> +#if __WORDSIZE == 64
>> The underscores at the beginning of the name seem to be shouting
>> "unportable!" to me, but maybe I'm wrong ;)
> what is more important question: what's the number behind sizeof(*)? is it 4 
> or 8? if 4 - then visual will have the same problem as gcc :)
Yes, but if it doesn't know "__WORDSIZE", then it won't work even on
32bit systems, so the fix may break more things than fix.

(as a sidenote, it works in VS2003, but still I find these underscores
rather suspicious)

--

-- 
Maciek
 xmpp:machekku@...

Re: [PATCH] fox for gcc on 64bit archs

Dnia środa, 3 stycznia 2007 00:27, Maciek Niedzielski napisał:
> Yes, but if it doesn't know "__WORDSIZE", then it won't work even on
> 32bit systems, so the fix may break more things than fix.

we can add simple #if defined for linux (and very probably macosx), but I have 
completely no idea, what to do on windows - not my speciality ;)

> (as a sidenote, it works in VS2003, but still I find these underscores
> rather suspicious)

after upgrading to visual 2005 you would need something like this:
#define _CRT_NONSTDC_NO_WARNINGS
in stdafx.h, to compile programs with function like strcpy, without extra 
warnings (but it's an single underscore at the beggining, not double ;), as 
you can see ).

Cheers,
Przemek
-- 
--------------------------------------------------------------------------
Email: troll (at) gentoo.org                 Przemysław Maciąg
Email: pmaciag (at) gmail.com
Reg Linux User#: 303556              "Life is like a box of chocolates."
GPG: 2A84608A [subkeys.pgp.net]    "You never know what you're gonna get."
--------------------------------------------------------------------------

Dnia środa, 3 stycznia 2007 00:27, Maciek Niedzielski napisał:
> Yes, but if it doesn't know "__WORDSIZE", then it won't work even on
> 32bit systems, so the fix may break more things than fix.

we can add simple #if defined for linux (and very probably macosx), but I have 
completely no idea, what to do on windows - not my speciality ;)

> (as a sidenote, it works in VS2003, but still I find these underscores
> rather suspicious)

after upgrading to visual 2005 you would need something like this:
#define _CRT_NONSTDC_NO_WARNINGS
in stdafx.h, to compile programs with function like strcpy, without extra 
warnings (but it's an single underscore at the beggining, not double ;), as 
you can see ).

Cheers,
Przemek
--

-- 
--------------------------------------------------------------------------
Email: troll (at) gentoo.org                 Przemysław Maciąg
Email: pmaciag (at) gmail.com
Reg Linux User#: 303556              "Life is like a box of chocolates."
GPG: 2A84608A [subkeys.pgp.net]    "You never know what you're gonna get."
--------------------------------------------------------------------------