Modify

#182 closed defect (fixed)

Problem with duplicate buddies and renaming accounts

Reported by: harmen@… Owned by:
Priority: normal Milestone:
Component: BitlBee Version: 1.0.2
Keywords: Cc:
IRC client+version: Client-independent Operating System: FreeBSD
OS version/distro:

Description

I have a couple of buddies which I have in more then one account. As a matter of clarity I tried to rename them to ~name- whereby - stands for "added in alternate account" and ~ for "this is to see if I'm online myself". Works fine, though as soon as you reconnect to the server it messes it all up. It doesn't save the name properly and I end up with Name-_ instead of ~Name- for example. Bit hazy...

To clarify a bit (I'm horrible with explaining things well):

I started with this:

JpbMSN

JpbMSN_

I had this (after renaming):

JpbMSN

JpbMSN-

And after saving and reconnecting ended up with:

JpbMSN-

JpbMSN-_

Whereby JpbMSN is used on my private msn account and JpbMSN- on my work-account. They're both the same MSN account of JPB though. I didn't test what happens in other situations.

Attachments (0)

Change History (2)

comment:1 Changed at 2006-07-12T10:51:52Z by wilmer

Hi Murf. :-)

This is a known problem, and unfortunately a problem with the current .nicks file format. The XML-format that we'll use in future BitlBee releases fixes this (and other) problem(s). You can get a snapshot from http://code.bitlbee.org/wilmer/storage-xml/ (use bzr, not wget -r!!!) if you feel like beta-testing. ;-)

(Don't worry, it seems to be pretty stable.)

I'll close this bug when I merge the XML stuff into the main development code.

comment:2 Changed at 2006-10-15T09:46:05Z by wilmer

Resolution: fixed
Status: newclosed

This is in the development branch now. Which means I can close this, because it'll eventually be released. :-)

Modify Ticket

Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.