From: pierre@baillet.name (Pierre Baillet)
Subject: [sup-talk] Contact Manager and fullname aliasing
Date: Thu, 22 Nov 2007 09:57:08 +0100 [thread overview]
Message-ID: <6205b42d0711220057l79ecc2ect6c4a29dc5efff4ef@mail.gmail.com> (raw)
Hi,
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: For some of my contacts, I'd like to be able to change the #name
without adding an alias (such as rename dad at home.com to "Dad Home" and
dad at work.com to "Dad Work") in order to make the Inbox List much easier to
read.
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).
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 might want to have an alias
name "annoyingcolleague" and still have "John Doe" displayed when sending
him an email... Maybe a mix of these two ideas : allow fullname aliasing and
present all "internal" emails list in the following priority order: alias,
aliased fullname, fullname from the real email.
What do you think ?
Cheers,
--
Pierre Baillet <pierre at baillet.name>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/sup-talk/attachments/20071122/5bcffae0/attachment.html
next reply other threads:[~2007-11-22 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 8:57 Pierre Baillet [this message]
2007-11-23 18:56 ` William Morgan
2007-11-24 18:38 ` Pierre Baillet
2007-12-21 18:23 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6205b42d0711220057l79ecc2ect6c4a29dc5efff4ef@mail.gmail.com \
--to=pierre@baillet.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox