From: Jim Burton <jim@sdf-eu.org>
To: ding@gnus.org
Subject: BBDB and the message buffer
Date: Wed, 11 Feb 2009 18:39:13 +0000 [thread overview]
Message-ID: <87bpt8lsxa.fsf@sdf-eu.org> (raw)
Hi, I suppose this must be an FAQ bit I can't solve it. How do I bind
M-t to bbdb-complete-name in the message buffer? I found this example
online and added to my .gnus:
(add-hook 'gnus-startup-hook 'bbdb-insinuate-gnus)
(setq mail-setup-hook 'bbdb-insinuate-sendmail)
(add-hook 'message-setup-hook 'bbdb-insinuate-message)
(defun bbdb-insinuate-message ()
"Call this function to hook BBDB into the message package."
(define-key message-mode-map "\M-\t" 'bbdb-complete-name))
;;;;;;;;;
But M-t is bound to aspell...help? (In case this makes any difference,
I'm starting a message with 'm').
I would also like point to be after the colon in the first line ("To:
<point>") -- how can I manage this?
Thanks,
Jim
next reply other threads:[~2009-02-11 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 18:39 Jim Burton [this message]
2009-02-11 20:25 ` Reiner Steib
2009-02-11 20:44 ` Jim Burton
2009-02-11 21:30 ` Reiner Steib
2009-02-11 21:54 ` Jim Burton
2009-02-14 14:38 ` Steinar Bang
2009-02-14 22:15 ` Harry Putnam
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=87bpt8lsxa.fsf@sdf-eu.org \
--to=jim@sdf-eu.org \
--cc=ding@gnus.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).