Gnus development mailing list
 help / color / mirror / Atom feed
From: dsg@linus.mitre.org (David S. Goldberg)
Subject: Message, Gnus and bbdb
Date: 10 Mar 1997 11:28:54 -0500	[thread overview]
Message-ID: <m1bk9nf6795.fsf@blackbird.mitre.org> (raw)

I've been using Kai's message-x for quite some time now.  I had made
my own function for doing completion using Peter Galbraith's
e-mh-alias package.  As I am cleaning out the last vestiges of MH in
my Gnus usage, last week I decided to give bbdb a try.  I reset
message-x to use bbdb-complete-name for the to and cc headers.  One
thing I saw in the bbdb info that interested me was the ability to use
a mail-alias property to maintain mailing lists.  Unfortunately I
can't seem to get bbdb-complete-name to recognize the names I put in
these aliases, so while I can do completion/alias expansion on
individuals, my lists are not available to me.  I realize I could just
make separate entries for the lists, but that seems wrong somehow...

On another note, I don't understand how the bbdb auto-creation feature
is supposed to work.  I've added a call to my gnus-select-group-hook
such that a few of my nnml groups have bbdb/news-auto-create-p turned
on.  I can verify that that works (that is, the variable is properly
set to t in those groups, nil in all the others).  However, when I
read new messages in these groups, nothing seems to happen with bbdb.
I can type : or ; and be prompted to create an entry for the current
message.  What am I missing to get the automatic stuff?  Or am I just
misunderstanding what's supposed to happen?

Any advice greatly appreiciated.

--
Dave Goldberg
Post: The Mitre Corporation\MS B305\202 Burlington Rd.\Bedford, MA 01730
Phone: 617-271-3887
Email: dsg@mitre.org


             reply	other threads:[~1997-03-10 16:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-03-10 16:28 David S. Goldberg [this message]
1997-03-10 18:23 ` Steven L Baur
1997-03-10 18:37   ` David S. Goldberg
1997-03-11  2:08 ` David Moore
1997-03-11 16:44   ` David S. Goldberg

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=m1bk9nf6795.fsf@blackbird.mitre.org \
    --to=dsg@linus.mitre.org \
    --cc=dsg@mitre.org \
    /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).