Bug 214338 - Always try to use first nicks instead of cycling through available nicks
Summary: Always try to use first nicks instead of cycling through available nicks
Status: RESOLVED DUPLICATE of bug 107667
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-13 02:39 UTC by Christoph Feck
Modified: 2015-05-17 11:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Feck 2009-11-13 02:39:58 UTC 
Version:            (using Devel)
Installed from:    Compiled sources

I need to have a list of some more alternative nicks, such as "nick", "nick_", "nick__" etc, because my provider sometimes cuts connection multiple times in a short time, and automatic reconnection would fail if all nicks are used (they stay unavailable for 15 minutes, or so).

Very often, however, the cut is only made once a day, so it would be nice if Konversation would always try the first nickname first, instead of cycling.
Comment 1 Eike Hein 2009-11-13 07:13:30 UTC 
Hm, I thought we did this already (I seem to have a memory of writing code to reset the nick queue on a successful connection), but we'll check. Could you tell us the version you're using, though?
Comment 2 Christoph Feck 2009-11-13 14:11:34 UTC 
I am using trunk version, recompiled daily.
Comment 3 Eike Hein 2009-11-13 14:14:14 UTC 
Ok, thanks!
Comment 4 Christoph Feck 2015-05-17 11:15:15 UTC 

*** This bug has been marked as a duplicate of bug 107667 ***