Bug 129116 - Highlight preferred e-mail address during auto-completion
Summary: Highlight preferred e-mail address during auto-completion
Status: RESOLVED DUPLICATE of bug 131176
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-14 00:44 UTC by Tristan Miller
Modified: 2007-09-14 12:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tristan Miller 2006-06-14 00:44:57 UTC
Version:            (using KDE KDE 3.5.2)
Installed from:    SuSE RPMs

KAddressbook lets you specify multiple e-mail addresses for a contact, and then mark one such address as "preferred".  However, when specifying a recipient in the KMail composer, all addresses for the contact show up during auto-completion.  There's no indication as to which address is the preferred address.  This problem affected me the other day when I sent e-mail to someone at his non-preferred address, and he wrote me back to say that it was lucky he got my mail as he checks that account only once a month.

Please update the auto-completion routine to add some indication as to which address is preferred when a recipient has multiple addresses.  This could be done, for example, by adding the text "(preferred address)" after the address, or by putting the preferred address in bold, or by listing the preferred address first and then indenting all the non-preferred addresses, or some combination of these techniques.
Comment 1 Antonio 2007-01-26 23:37:55 UTC
I second that wish, using KDE 3.5.6.

Whatever I set as default address doesn't matter, because the completion list is always sorted alphabetically. It should be at the top of that one contact's address list though, and highlighted somehow.

Wish #111281 and bug #131176 seem to address the same issue, by the way.
Comment 2 Philip Rodrigues 2007-03-11 23:27:16 UTC

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