From: Noah Friedman <friedman@splode.com>
Cc: ding@gnus.org, morioka@jaist.ac.jp
Subject: forgive me father, but...tm-vcard.el
Date: Thu, 13 Aug 1998 19:59:42 -0700 (PDT) [thread overview]
Message-ID: <19980813195942.306687.FMU12449@piglet.splode.com> (raw)
In-Reply-To: <ajc@bing.wattle.id.au> , 07 Aug 1998 13:48:57 +1000
>I know vcards are evil and all, but since my Place of Employment is
>going Netscape[1], i'm going to have to deal with vcards more and
>more. So I gave in and got TM to display vcards using Noah Friedman's
>vcard.el library.
I don't think vcards are evil. They make it much easier to parse and store
stuff in a database. If you have to live a MIME world (which is not so
bad, really), vcards beat free-form signatures hands down. (Disclaimer: I
work for Netscape. Assume bias as you wish. :-))
Thanks for the code, too! If you plan to publish your code somewhere on
the web, let me know and I'll add a link from my elisp software pages to
yours.
prev parent reply other threads:[~1998-08-14 2:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-07 3:48 Andrew J Cosgriff
[not found] ` <ajc@bing.wattle.id.au>
1998-08-14 2:59 ` Noah Friedman [this message]
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=19980813195942.306687.FMU12449@piglet.splode.com \
--to=friedman@splode.com \
--cc=ding@gnus.org \
--cc=morioka@jaist.ac.jp \
/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;
as well as URLs for NNTP newsgroup(s).