Summary: | composing mail -- addresses: resource vs. recent addresses duplicates | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Maciej Pilichowski <bluedzins> |
Component: | composer | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | wishlist | CC: | bjoern, luigi.toscano, schaarsc |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Maciej Pilichowski
2007-03-06 16:05:20 UTC
Christian, This is fixed in pim+ right? We should make sure to port the fix into the 3.5 branch. Indeed, that was commit 620313. The commit involves more than the duplicate issue alone. Allen, you think it's OK to send all improvements involved to the 3.5 branch? commit 620313 is for recipientspicker only. I prefer to see my recent addresses no matter if they are in my addressbook or not. I vote for leaving address completion as it is right now. Christian, did I understand you correctly -- you want to see duplicates? yes, I want to know which addresses I have been using. but we could add an option to the "edit recent addresses" dialog, something like "don't store addressbook entries". Would that fit your needs? May be someone might look into a similar issue. see http://bugs.kde.org/show_bug.cgi?id=85539#c4 As almost all of my contacts are stored in the addressbook, this does not happen to me frequently any more or may be it's fixed. Christian, from which source? Ok. I would rather prefer to save screen space and optimize navigation.
> "edit recent addresses" dialog, something like "don't store addressbook
> entries".
99.99% ok. My only concern is with the approach -- better "don't display...", consider deleting address from AB.
Ferdinand, fixed means "does not happen at all". If this happens from time to time it is not fixed then. I just checked (just in case), it happens (duplicates).
Yes, happens in KDE 4.3. Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding. Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2. |