From mboxrd@z Thu Jan 1 00:00:00 1970 From: wmorgan-sup@masanjin.net (William Morgan) Date: Fri, 23 Nov 2007 10:56:58 -0800 Subject: [sup-talk] Contact Manager and fullname aliasing In-Reply-To: <6205b42d0711220057l79ecc2ect6c4a29dc5efff4ef@mail.gmail.com> References: <6205b42d0711220057l79ecc2ect6c4a29dc5efff4ef@mail.gmail.com> Message-ID: <1195843961-sup-2106@south> Hi Pierre, Excerpts from Pierre Baillet's message of Thu Nov 22 00:57:08 -0800 2007: > I'd like to alter the way the ContactManager work so that it could be > able to save contact which don't have an alias but for which the #name > has been modified: Sounds great. > The problem is that the contact manager is not able to handle > alias-less contacts and hence any modification to a Person during the > run of Sup is never saved for unaliased contacts (I actually patched > my sup to allow fullname modification before understanding that sup > will never save these changes :p). I think the best solution is to alter the contact manager such that it can handle contacts without aliases. I think it currently stores everything as a hash from alias to Person object, so you'll have to add an array instead. On the UI side, we can mimic Mutt-style alias prompts. Press 'l' and it asks you for the person name (pre-filled with the name from the email), and then asks you for the alias, allowing you to hit enter for none. Something like that. > Another idea would be to force all displays to use aliases instead of > real names when displaying emails. This is probably simple to > implement because there is no need to rework on the Contact Manager, > but i still think that "full name" (this full name is used in TO: > headers) and "alias" (this alias is only used internally) should be > different I agree that it's better that the two fields are different. -- William