>> sqimap_msgs_list_copy() does not copy messages, it moves them.

> Yep, you're right.  That's a badly named function, at best.  I see two
> possible solutions.

Agreed.

> Copy sqimap_msgs_list_copy() to sqimap_msgs_list_move() and remove the
> delete command from sqimap_msgs_list_copy().  Update all existing
> references to sqimap_msgs_list_copy to point to the new _move() command.

I think this option is more suitable, it also provides future plugins and
what not two options.  This gives us the chance to add the COPY function
into the filters plugin as well.

> Add a parameter to sqimap_msgs_list_copy(). If set, it deletes the
> messages after copying.

This is viable as a more temporary solution I'd say.

> Jon, could you please give me the Official Word on if I can also add that
> to stable CVS?  The thought of changing the API like this between stable
> releases makes my butt pucker..

Lets get 1.4.2 out the door first... then we'll change it.  I think I'll
start hacking through the bug tracker, and playing catch up on some of
those outstanding requests on the users list.

-- 
Jonathan Angliss
([EMAIL PROTECTED])


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
--
squirrelmail-users mailing list
List Address: [EMAIL PROTECTED]
List Archives:  http://sourceforge.net/mailarchive/forum.php?forum_id=2995
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users

Reply via email to