[Konversation-devel] [Bug 129708] konversation needs irssi-style auto completion

Eike Hein sho at eikehein.com
Fri Jun 23 22:37:41 CEST 2006

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From sho eikehein com  2006-06-23 22:37 -------
Peter: Your commit description suggests that the change you made bumps the last completion made to the front of the list for the given completion prefix, while this is about bumping the last active sender on the channel to the front of the list.

Let's say we have three users beginning with the letter "a" in the channel: Aaron, Andrew, Armin.

Prior to your commit, the completion list for "a" would have been strictly alphabetical, i.e. "Aaron, Andrew, Armin".

Going by your commit description, if my last completion was to "Andrew", the list for "a" would now be sorted "Andrew, Aaron, Armin", even when "Armin" was active on the channel recently and "Andrew" has been idle for a while.

If this request is implemented (optional or not), the list for "a" in the above scenario would end up being "Armin, Aaron, Andrew" regardless of my last completion. I.e. this needs to be reopened, or your commit description was false.

Personally, I'm wary of this type of "intelligent" algorithm. My favorite example of this kind of design going wrong are the "Personalized Menus" in recent versions of Microsoft Office, which has application menus only display commonly used items and hides the rest unless a button at the bottom of the menu is clicked. This results in the user ending up unaware of existing functionality, and having a hard time with unpredictably moving around menu items. It's easy to make the same mistake with "intelligent" completion schemes.

If I had to chose between the two outlines above, I'd prefer the one Patrick actually requested. As you note in your commit message, the last completion is always accessible by pressing the Tab key without giving a completion prefix.

More information about the Konversation-devel mailing list