After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 503983 - Adding an address book should add it for autocompletion
Adding an address book should add it for autocompletion
Status: RESOLVED DUPLICATE of bug 373297
Product: evolution
Classification: Applications
Component: Contacts
2.12.x (obsolete)
Other Linux
: Normal enhancement
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-12-17 04:16 UTC by Richard Laager
Modified: 2009-12-17 10:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Richard Laager 2007-12-17 04:16:35 UTC 
I added an address book, with the obvious intention of putting contacts in it. I was surprised that it didn't get added to the list of address books used for autocomplete. I think this should happen by default.
Comment 1 André Klapper 2007-12-17 10:27:29 UTC 
hmm. if we do that, other people will probably complain that it happens automatically.
maybe the best choice is to add a checkbox when adding the addressbook so people can choose this directly when creating it.
Comment 2 Richard Laager 2007-12-17 19:54:44 UTC 
If you have autocomplete enabled and are creating a new address book, why *wouldn't* you want it to be used for autocomplete? That seems like such a corner case that you could tell people to go turn it off and call it good. Adding address books has to be pretty uncommon, but it'd be nice if it Just Worked.
Comment 3 Akhil Laddha 2009-12-17 10:46:35 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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