Gnus development mailing list
 help / color / mirror / Atom feed
From: Danny Siu <dsiu@mv.us.adobe.com>
Subject: Re: Is Username Expansion possible in GNUS?
Date: 14 Jun 1996 15:36:27 -0700	[thread overview]
Message-ID: <yj9wx1am2s4.fsf@adobe.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 14 Jun 1996 00:32:52 +0000

Lars Magne Ingebrigtsen writes:

  Lars> Danny Siu <dsiu@mv.us.adobe.com> writes:
  >> There is a very nice feature of Pine which can be included in GNUS
  >> message mode .  When composing a message in Pine, just type in the
  >> username, for example, "dsiu", and Pine will expend it to full name and
  >> uid@FQDN, like "Danny Siu <dsiu@adobe.com>".

  Lars> Put something like:

  Lars> alias dsiu "Danny Siu <dsiu@adobe.com>"

  Lars> in your .mailrc file.

Well, I don't think it's something I want to do since there are ~2000 people
at Adobe.  I am using .mailrc file now for aliases of my friends and group
aliases.

Also I am using BBDB which works wonderful!  It automatically learns the
name and email address of people whom I received mail from.

Prehaps I didn't state my question clearly.  For the people at Adobe whom I
have never received any mail from (hence no BBDB record), what I want is to
be able to expend their username (eg: jwz) to full name (first and last
name) so that I know I spell their email address right.

I don't know how Pine does that.  Maybe it looks up somewhere in the net and
give me fullname after I type in the email address.  Does anyone know how
Pine works this wonder?

-- 
                                                                ^..^
 '/..\"                                                        ( oo )  )~
m( oo )m                                                         ,,  ,,
/=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=\
|  Danny Dick-Fung Siu                http://www-leland.stanford.edu/~dsiu |
|  Reference System Group             http://www.csua.berkeley.edu/~dsiu   |
|  Adobe Systems Incorporated       E-Mail:<dsiu@alumni.eecs.berkeley.edu> |
|       "What do you expect from a         <dsiu@leland.stanford.edu>      |
|          Cal. Berkeley grad.?"           <dsiu@adobe.com>                |
\=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=/


  reply	other threads:[~1996-06-14 22:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-13 21:47 Danny Siu
1996-06-14  0:32 ` Lars Magne Ingebrigtsen
1996-06-14 22:36   ` Danny Siu [this message]
1996-06-14 23:02     ` Eric Hendrickson
1996-06-15  1:44       ` Sudish Joseph
1996-06-15 19:06         ` Hallvard B Furuseth
1996-06-15  1:51       ` Lars Magne Ingebrigtsen
1996-06-16 21:27         ` Mark Eichin
1996-06-17  2:33           ` Lars Magne Ingebrigtsen
1996-06-17 18:21             ` Edward J. Sabol
1996-06-18  2:38               ` Sudish Joseph
1996-06-18 16:33                 ` Hallvard B Furuseth
1996-06-18 16:56                   ` Lars Magne Ingebrigtsen
1996-06-18 17:15                     ` Hallvard B Furuseth
1996-06-14 13:08 ` David Worenklein
1996-06-14 15:45 ` Kai Grossjohann
1996-06-17  5:30   ` Mark Breslauer
1996-06-17 14:23     ` BBDB and Gnus 5.2 Jack Vinson
1996-06-17 16:14     ` Is Username Expansion possible in GNUS? Kai Grossjohann
1996-06-18 14:55     ` Hans de Graaff
1996-06-18 15:57       ` Jack Vinson
1996-06-25 17:11         ` Brian Edmonds

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=yj9wx1am2s4.fsf@adobe.com \
    --to=dsiu@mv.us.adobe.com \
    /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).