From: deskpot@despammed.com (Vasily Korytov)
Subject: Re: BBDB completion keystroke
Date: Thu, 22 May 2003 00:13:01 +0400 [thread overview]
Message-ID: <873cj8rrci.fsf@unix.home> (raw)
In-Reply-To: <j70el2sjeqc.fsf@dufair.org>
On Wed, 21 May 2003 14:12:43 -0500, Jason Dufair wrote:
> I guess I meant to ask how to make tab be the BBDB completion keystroke
> for the header area of message mode, i.e. the To: Cc: Bcc: fields. I've
> read thru some of the BBDB documentation but don't quite know even how
> to find what I'm looking for. I'm just a Gnus (l)user in this regard.
I guess, you've read the docs too badly. Does the following do what you need?
(setq bbdb-completion-type 'primary-or-name)
(require 'bbdb)
(bbdb-initialize 'gnus 'message)
--
I accept RFC3156 and RFC2440-compatible encrypted mail.
PGP key fingerprint: 123A 7CCE 6E26 6233 0D87 E01A A0F8 3524 FCD8 1841
next parent reply other threads:[~2003-05-21 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <j707k8kxo7m.fsf@dufair.org>
[not found] ` <8ak7ckjjpa.fsf@sm.intel.com>
[not found] ` <j70el2sjeqc.fsf@dufair.org>
2003-05-21 20:13 ` Vasily Korytov [this message]
[not found] ` <8aznlgourc.fsf@sm.intel.com>
2003-05-21 21:40 ` Jason Dufair
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=873cj8rrci.fsf@unix.home \
--to=deskpot@despammed.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).