From: adamp_at@at_ipipan.waw.pl (Adam P.)
Subject: Re: bbdb and mail-aliases not working
Date: Sat, 18 May 2002 13:51:33 +0200 [thread overview]
Message-ID: <wkd6vt4qt6.fsf@at_ipipan.waw.pl> (raw)
In-Reply-To: <86u1p569i5.fsf@foo.bar>
Mike Irwin <mikeirw@pobox.com> writes:
> remi.letot@easynet.be (Remi Letot) writes:
>
>> I'm now trying to use bbdb, and everything seems to work fine, except
>> mail aliases. I made some in my bbdb, but they will not expand when I
>> use them while composing a new message.
>
> By default, bbdb uses M-Tab to expand aliases. This may or may not conflict
> with your window manager if you use one. If it does conflict, you can
> either rebind the keys for your WM, or you can set this in your .gnus:
>
> (define-key message-minibuffer-local-map [(tab)] 'bbdb-complete-name)
You might need to add these two lines to the line above:
(add-hook 'mail-setup-hook 'bbdb-define-all-aliases) ;; Emacs
(add-hook 'message-setup-hook 'bbdb-define-all-aliases) ;; Gnus
Adam
--
Name and address in X-Real...
next parent reply other threads:[~2002-05-18 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bsbdls0t.fsf@easynet.be>
[not found] ` <86u1p569i5.fsf@foo.bar>
2002-05-18 11:51 ` Adam P. [this message]
2002-05-18 14:29 ` Kai Großjohann
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=wkd6vt4qt6.fsf@at_ipipan.waw.pl \
--to=adamp_at@at_ipipan.waw.pl \
/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).