From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: `m', the new minibuffer prompts and bbdb
Date: 03 Jan 1996 10:39:11 +0100 [thread overview]
Message-ID: <vimtwrb4.fsf@bjob.no> (raw)
In-Reply-To: Kai Grossjohann's message of 29 Dec 1995 17:51:18 +0100
Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de> writes:
> I have just installed sgnus-0.26
> and I see that there are new minibuffer prompts in gnus-*-mail
> (whatever is called by `m'). What do I do to bind TAB and M-TAB to
> bbdb-complete-name in this case?
>
> The name of the keymap or the right hook would be enough information,
> of course.
I've just used `read-string', so `minibuffer-local-map' is the keymap
in effect, I think.
--
Lars Magne Ingebrigtsen * larsi@ifi.uio.no
(a red leaf that falls from the purple tree)
next prev parent reply other threads:[~1996-01-03 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-29 16:51 Kai Grossjohann
1996-01-03 9:39 ` Lars Magne Ingebrigtsen [this message]
1996-01-12 15:36 ` Kai Grossjohann
1996-01-15 23:17 ` Lars Magne Ingebrigtsen
1996-01-16 3:59 ` Per Abrahamsen
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=vimtwrb4.fsf@bjob.no \
--to=larsi@ifi.uio.no \
/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).